Updated on 2022-08-16 GMT+08:00

Changing the OS

Scenarios

Changing an ECS OS will change the system disk attached to the ECS. After the changing, the system disk ID of the ECS will be changed, and the original system disk will be deleted.

If the OS running on an ECS cannot meet service requirements, change the ECS OS.

The public cloud supports changing between image types (public images, private images, and shared images) and between OSs. You can change your OS by changing your ECS image.

Constraints

  • The EVS disk quota must be greater than 0.
  • Windows and Linux cannot be changed to each other.
  • Switching between the ECSs in BIOS boot mode and in UEFI boot mode is not allowed.

Notes

  • After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
  • Back up data before changing the OS.
  • Changing the OS does not affect data in data disks.
  • After the OS is changed, your service running environment must be deployed in the new OS again.
  • After the OS is changed, the ECS will be automatically started.
  • After the OS is changed, the system disk type of the ECS cannot be changed.
  • After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
  • After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
  • It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
  • Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.

Prerequisites

  • The target ECS is stopped.
  • The target ECS has a system disk attached.
  • Necessary data has been backed up. (Changing the OS clears the data in all partitions of the system disk, including the system partition.)
  • If the original ECS uses password authentication while the new ECS uses key pair authentication, ensure that a key pair is available.
  • If a private image is required for changing the ECS OS, create the desired private image by following the instructions provided in Image Management Service User Guide.
    • If the image of an ECS is required, make sure that a private image has been created using the ECS.
    • If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
    • If a private image from another region is required, make sure that the image has been copied.
    • If a private image from another user account is required, make sure that the image has been shared with you.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select your region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. Locate the row containing the target ECS. Click More in the Operation column and select Manage Image/Disk > Change OS.

    Only stopped ECSs support OS changing. If the ECS is not stopped, stop it before proceeding with changing.

  5. Modify related ECS parameters, such as Image Type and Image, based on service requirements.
  6. Configure the login mode.

    If the target ECS uses key pair authentication, you can replace the original key pair.

  7. Click OK.
  8. On the Change ECS OS page, confirm the specifications, and click Submit Application.

    After the application is submitted, the ECS status changes to Changing OS. The OS changing has been completed when Changing OS disappears.

    A temporary ECS is created during the OS changing process. After the process is complete, this ECS will be automatically deleted.

Follow-up Procedure

  • If the OSs before and after the OS change are both Linux, and automatic partition mounting upon system startup has been enabled for the data disk, the data disk partition mounting information will be lost after the OS is changed. In such a case, you need to update the /etc/fstab configuration.
    1. Write the new partition information into /etc/fstab.

      It is a good practice to back up the /etc/fstab file before writing data into it.

      To enable automatic partition mounting upon system startup, see Initializing a Linux Data Disk (fdisk).

    2. Mount the partition so that you can use the data disk.

      mount Disk partition Device name

    3. Check the mount result.

      df -TH

  • If the OS change is unsuccessful, perform steps 3 to 8 again to retry changing the OS again.
  • If the second OS change attempt is unsuccessful, contact customer service for manual recovery at the backend.