Why Does a Forcibly-Stopped Linux ECS Fail to Be Restarted?

Symptom

When you try to restart a forcibly-stopped Linux ECS, the ECS failed to be restarted, as shown in Figure 1.

Figure 1 Restart failure

Possible Causes

As shown in Figure 1, the ECS cannot be restarted because the file system was 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 the password of user root 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 step 4.
3. Run the following command to unmount the affected disk partition:

   umount /dev/xvdb1

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

   fsck -y /dev/xvdb1

5. Run the following command to restart the ECS:

   reboot

   

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