| copyright |
|
||
|---|---|---|---|
| lastupdated | 2024-07-24 | ||
| keywords | troubleshoot virtual server, virtual servers troubleshooting, tips, error, problem, insufficient capacity | ||
| subcollection | virtual-servers | ||
| content-type | troubleshoot |
{{site.data.keyword.attribute-definition-list}}
{: #vsi-troubleshoot-vs-why-vs-read-only} {: troubleshoot} {: support}
The virtual server is in read-only status. {: tsSymptoms}
A virtual server might receive a read-only issue because of unplanned networking incidents or outages. {: tsCauses}
To bring back your server from a read-only status, you need to restart the server to rescue kernel, and you need to run a file system check on all your file systems. {: tsResolve}
- From your device list, click the name of the server > Actions menu > Rescue kernel.
- When your server restarts in rescue mode, log in to the server by using SSH with the root user credentials.
- Run a file system check by using the following command:
fsck -y -C /dev/xvda1 - Run the same command if you have more files systems such as
/dev/xvda2_, _/dev/xvda3, and other files.
For more help, contact support or open a support case.
Running a file system check might cause data loss, so make sure that your data is backed up. {: note}