Help Center > > FAQs> OS Management> OS Faults> Why Does a Forcibly Stopped Linux ECS Fail to Start Due to File System Damage?

Why Does a Forcibly Stopped Linux ECS Fail to Start Due to File System Damage?

Updated at: Sep 02, 2021 GMT+08:00

Symptom

After you forcibly stop a Linux ECS and try to start the ECS, the ECS cannot be started.

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 in 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 procedure considers the affected disk partition as /dev/xvdb1, which is the partition shown in Figure 1.

  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 so that the configuration takes effect:

    reboot

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

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel