vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/ecs/umn/en-us_topic_0087622835.html
Huijuan, Wang 21515be61b ecs umn 20240823 
Reviewed-by: Pristromskaia, Margarita <margarita.pristromskaia@t-systems.com>
Co-authored-by: Huijuan, Wang <wanghuijuan738@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-committed-by: Huijuan, Wang <wanghuijuan738@noreply.gitea.eco.tsi-dev.otc-service.com>
2024-10-28 16:14:07 +00:00

4.5 KiB
Raw Blame History

How Can I Rectify the Fault That May Occur on a Linux ECS with an NVMe SSD Disk Attached?

Symptom

When a Linux ECS with an NVMe SSD disk attached becomes faulty, you must contact the administrator to remotely rebuild the ECS again.

If automatic NVMe SSD disk attachment upon ECS startup is enabled in /etc/fstab on the faulty ECS, the system disk recovers after the ECS is created. However, the attached NVMe SSD disk does not have a file system, and automatic NVMe SSD disk attachment upon ECS startup fails to take effect. As a result, the ECS enters the emergency mode, as shown in Figure 1.

Figure 1 Emergency mode

To ensure that the new ECS is functional, you must manually delete the attachment information in /etc/fstab.

If the NVMe SSD disk is faulty, data on it will be lost. The operations provided in this section are only used to restore automatic NVMe SSD disk attachment to an ECS, but not restoring the data on the disk.

Solution

  1. Log in to the ECS.
  2. Enter the password of user root to log in to the ECS.
    Figure 2 Logging in to the ECS
  3. Run the following command to edit the /etc/fstab file:

    vi /etc/fstab

  4. Delete the attaching information of the NVMe SSD disk and save the file.
    Figure 3 Deleting the automatic attaching information
  5. Run the following command to restart the ECS:

    reboot

  6. Verify that the ECS recovers and can be logged in.
    Figure 4 Logging in to the ECS