Help Center> Elastic Cloud Server> FAQs> OS Management> OS Faults> What Should I Do If the Forcibly Stopped Linux ECS Fails to Start Due to File System Damage?
View PDF

What Should I Do If the Forcibly Stopped Linux ECS Fails to Start Due to File System Damage?

Symptom

After a Linux ECS is forcibly stopped, there is a low probability that the file system is damaged. As a result, the ECS fails to be restarted.

Figure 1 Failure to start an ECS

Possible Causes

As shown in Figure 1, the ECS cannot be started because the file system is damaged. Forcibly stopping or restarting an ECS is highly risky because this operation may cause inconsistent metadata of the file system, leading to the file system damage.

Solution

Use the disk repair tool (fsck) delivered with the Linux OS to rectify the fault.

The following uses Figure 1 as an example, in which the affected disk partition is /dev/xvdb1.

  1. Enter user root password as prompted.
  2. Run the following command to check whether the affected disk partition has been mounted:

    mount | grep xvdb1

    • If yes, go to step 3.
    • If no, go to 4.
  3. Run the following command to unmount the affected disk partition:

    umount /dev/xvdb1

  4. Run the following command to rectify the fault for the file system of the affected disk partition:

    fsck -y /dev/xvdb1

  5. Run the following command to restart the ECS to make the configuration take effect:

    reboot

    If the fault persists, contact customer service for technical support.

Parent topic: OS Faults