Detaching an EVS Disk from a FlexusX Instance

Scenarios

• If the file system on your system disk is damaged and your FlexusX instance cannot be started, you can detach the system disk and attach it to another FlexusX instance as a data disk. After the file system is fixed, you can re-attach the disk to the original FlexusX instance as the system disk.
• If you want to move a data disk from one FlexusX instance to another in the same region and AZ, you can detach the data disk and then attach it to that FlexusX instance.
• If you no longer need an EVS disk, you can detach and delete it.

Billing

A detached EVS disk will not be automatically deleted, and it will still be billed. To avoid unintended charges, you can delete or unsubscribe from the disk if it is no longer needed.

Constraints

• A system disk can only be detached offline. It means that you can detach the system disk only when its FlexusX instance is in the Stopped state.
• After the system disk is detached from a FlexusX instance, the following operations cannot be performed: starting the instance, remote login, resetting the password, changing instance specifications, changing the OS, reinstalling the OS, creating images, creating backups, adding disks, and changing the security group.

Prerequisites

• Before detaching an EVS disk from a running Linux FlexusX instance, you must log in to the instance and run the umount command to cancel the association between the disk and the file system. In addition, ensure that no program is reading data from or writing data to the disk. Otherwise, the disk will fail to detach.

Procedure

1. Log in to the FlexusX console, click in the upper left corner, and select a region and project.
2. Click the name of the target FlexusX instance from which you want to detach a disk.

   The details page of this instance is displayed.

3. Click the Disks tab. Locate the target disk and click Detach.