---
name: virtual-servers-vsi_troubleshooting_virtualserver_readonly
title: Why is my virtual server read-only?
description: The virtual server is in read-only status.
last-updated: 2024-07-24
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/virtual-servers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why is my virtual server read-only?
{: #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}

1. From your device list, click the **name of the server** > **Actions menu** > **Rescue kernel**.
1. When your server restarts in rescue mode, log in to the server by using SSH with the root user credentials.
1. Run a file system check by using the following command:
   `fsck -y -C /dev/xvda1`
1. Run the same command if you have more files systems such as `/dev/xvda2_, _/dev/xvda3`, and other files.

For more help, contact [support](https://cloud.ibm.com/docs/get-support?topic=get-support-get-supportfaq&format=markdown#contactsupport) or open a support case.

Running a file system check might cause data loss, so make sure that your data is backed up.
{: note}