This topic describes how to isolate damaged local disks in the ECS console. When a damaged local disk is isolated, the corresponding ECS instance still resides on the same physical machine. The procedure described in this topic is applicable only to resolving system events about damaged local disks on ECS instances.

Procedure

  1. Log on to the ECS console.
  2. In the left-side navigation pane, click Events.
  3. On the Pending Events page, click the Local Disk Damaged tab.
  4. Find the target instance, and click Repair in the Actions column.
  5. In the Configurations Modification step, modify the configuration file of the instance. Then, click Next.
    Configurations modificationIf the Configurations Modification step is displayed for some Linux instances, complete the following operations. In this topic, the damaged disk named /dev/vdd is used as an example.
    1. Connect to the ECS instance. For more information, see Overview.
    2. Optional:Isolate the read and write operations of the local disk at the application layer.
    3. For Linux instances, add the nofail parameter to the /etc/fstab configuration file of the ECS instance for the local disk.
      /dev/vdd /mnt/vdd ext4 defaults,barrier=0,nofail 0 0
      Parameter Description
      /dev/vdd The device name of the local disk, which is the value of the Device parameter returned by DescribeInstanceHistoryEvents.
      /mnt/vdd The mount point of the local disk, which can be queried using the mount | grep "/dev/vdd" command.
      ext4 The file system type of the instance, which can be queried using the blkid /dev/vdd1 command.
      barrier=0 The mount option to disable barriers in the file system.
      nofail Indicates that the booting sequence of the ECS instance will not be interrupted even if the local disk specified in the file system does not exist.
    4. Detach the local disk.
      umount /dev/vdd
      Note If you do not detach the local disk, the device name of the local disk will be modified after the local disk is isolated and repaired. In this case, applications may read from or write to another disk.
  6. In the Damaged Disk Isolation step, click OK.
    Refresh the page if the next step is not displayed.
  7. Optional:In the Instance Restart step, click Restart.
    If the Instance Restart step is displayed, you must click Restart to restart the instance.
    Note After the instance is restarted, the isolated damaged local disk is temporarily converted to a 1 MiB dummy hard disk to facilitate subsequent operations. At the application layer, you must continuously isolate the read/write operations on the damaged local disk and configure the nofail parameter in the /etc/fstab file.
  8. After the instance is restarted, click OK in the New Disk Inserting step.
    Wait for Alibaba Cloud to replace the damaged local disk on the physical machine that hosts the instance. Maintenance is typically completed within five weekdays. After maintenance is completed, you will receive a event that requires you to restore the disk.
  9. After you receive the event, click Restore in the Disk Restoration step.
    Refresh the page if the next step is not displayed.
  10. Optional:In the Instance Restart step, click Restart.
    If the Instance Restart step is displayed, you must click Restart to restart the instance.
  11. After the instance is restarted, click Complete in the Complete step.

Result

Within a few minutes after the damaged disk is replaced, the local disk damaged event disappears.

What to do next

After the damaged disk is isolated, check the status of the instance and local disk. The replaced local disk is restored to its original capacity, and you can reformat data disks. For more information, see Format a data disk for a Windows ECS instance or Format a data disk for a Linux instance.