How to expand the system disk capacity without changing the operating system image

The content of this article is about how to expand the system disk capacity without changing the operating system image. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Expanding the system disk

As your business develops, if you need to expand the system disk capacity, you can do so through the Replace System Disk function. This article only describes how to expand the system disk capacity without changing the operating system image.

Note

While expanding the system disk, you can also change the operating system. For specific operations, see Replacing the Operating System.

Notes

Replacing the system disk is a high-risk operation, so please be sure to read the following precautions carefully before replacing the system disk .

Risks

Replacing the system disk has the following risks:

Replacing the system disk requires stopping the instance, thus interrupting your business.

After the replacement is completed, you need to redeploy the business operating environment in the new system disk, which may cause long-term interruption to your business.

Replacing the system disk means reassigning a system disk to your instance. The cloud disk ID will change, so snapshots created based on the old system disk cannot be used to roll back the new system disk.

Note

After replacing the system disk, the snapshots you created manually will not be affected, and you can still use these snapshots to create custom images. If you set an automatic snapshot policy for the old system disk and set the automatic snapshot to be released with the cloud disk, the automatic snapshot policy will no longer apply to the new system disk, and the automatic snapshots of the old system disk will be automatically deleted.

Restrictions and instructions

When replacing the system disk, you need to pay attention to the following information:

After replacing the system disk, your instance will be assigned a For the new system disk, the system disk ID will be updated and the original system disk will be released.

You cannot change the cloud disk type of the system disk.

The system disk after expansion has a minimum capacity of the capacity before expansion and a maximum capacity of 500 GiB. The system disk capacity cannot be reduced.

Windows 2003 does not support system disk expansion.

If your annual or monthly subscription instance has been renewed and downgraded, you cannot modify the system disk capacity before entering the next billing cycle.

The IP address and MAC address of the instance remain unchanged.

Before expanding the system disk, it is recommended that you create a snapshot for the system disk. When creating a snapshot, pay attention to the following restrictions:

Avoid creating snapshots during your business peak period to avoid affecting your business. A 40 GiB snapshot takes about 40 minutes to create the first time. So please allow enough time. Moreover, creating snapshots may reduce block storage I/O performance (generally within 10%), causing temporary slowdowns.

When creating a snapshot for the system disk, please ensure that the system disk has enough space. It is recommended to reserve 1 GiB of space. Otherwise, the system may not start normally after the system disk is expanded and replaced.

To ensure that there are enough snapshot quotas to complete the automatic snapshot policy of the new system disk, you can delete unnecessary old system disk snapshots. For detailed operations, see Deleting Snapshots and Automatic Snapshot Policies.

Operation steps

#If you want to expand the system disk while retaining the contents of the original system disk, you must follow the steps below to replace the system disk:

Log in to the ECS management console.

In the left navigation bar, click Instances.

Select a region.

Find the instance that needs to expand the system disk, click the instance ID, and enter the instance details page.

Follow the following steps to create a snapshot of the system disk:

In the left navigation bar, click this instance disk.

Find the system disk and click Create Snapshot in the Operation column.

Note

For detailed operational restrictions or precautions on creating a snapshot, see Creating a Snapshot.

Follow the following steps to create a custom image using a system disk snapshot:

In the left navigation bar, click this instance snapshot to view the creation progress and status of the snapshot. When the progress is 100% and the status is Successful, in the Action column, click Create Custom Image.

Note

For detailed operational restrictions or precautions on creating a custom image, see Creating a Custom Image Using Snapshots.

When replacing the system disk, the image obtained through this method will appear in the drop-down list of Custom Image.

Return to the instance list page, in the left navigation bar, select Snapshots and Mirrors > Mirror to view the creation progress and status of the custom mirror.

When the custom image creation progress is 100% and the status is displayed as Available, click Instance in the left navigation bar.

Find the instance that requires operation, and in the Operation column, select More > Stop.

illustrate

If it is a pay-as-you-go VPC type instance and the no-charge-for-pay-as-you-go instance shutdown feature has been turned on, in the Reminder pop-up box, click OK. In the Stop Instance dialog box, select Keep the instance after stopping and continue to charge. If you use the no-charge mode, you may not be able to successfully start the instance after replacing the system disk.

When the status of the instance shows Stopped, in the Action column, select More > Replace the system disk.

In the pop-up dialog box, after carefully reading the precautions for replacing the system disk, click OK to replace the system disk.

On the Change System Disk page,

Image type: Select the custom image you just created from Custom Image.

System disk: Modify the system disk capacity according to business needs, and the maximum capacity can be expanded to 500 GiB. The minimum capacity that can be set during expansion is related to the current capacity of the system disk and the mirror, as shown in the following table.

Description

The cloud disk type of the system disk cannot be modified.

Security settings:

If it is a Windows system, you can only use password authentication.

If your instance is an I/O optimized instance and is a Linux system, you can choose to use password authentication or SSH key pair authentication. You can set a login password or bind an SSH key pair.

Confirm Configuration fee: includes the price of the image and the price of the system disk. Please see the cloud product pricing page for details.

After confirming that everything is correct, click OK to change.

You can monitor the system status through the console. It will take about 10 minutes to complete the operating system replacement. Once completed, the instance starts automatically.

Follow-up operations

After replacing the system disk, you may need to do the following operations:

If the Linux system, and, The instance has mounted the data disk and set up automatic mounting at startup: After replacing the system disk, the file system mounting information in the original system disk is lost. You must write the new partition information in the /etc/fstab file of the new system disk, and Mount the file system, but there is no need to format and partition the data disk. The operation steps are as follows. For specific operation commands, see Formatting and Mounting the Data Disk in Linux:

(Recommended) Back up /etc/fstab.

Write new partition information to /etc/fstab.

View the new partition information in /etc/fstab.

Mount the file system.

Check the current cloud disk space and usage: Run the command df -h.

After the mounting operation is completed, you can start using the new file system without restarting the instance.

Set an automatic snapshot policy for the disk. The automatic snapshot policy is bound to the cloud disk ID. After replacing the system disk with a new one, the automatic snapshot policy applied to the old cloud disk will automatically become invalid. You need to set an automatic snapshot policy for the new system disk.

The above is the detailed content of How to expand the system disk capacity without changing the operating system image. For more information, please follow other related articles on the PHP Chinese website!