Scenario

This document takes cloud disks with a capacity less than 2TB as an example to provide guidance on disk initialization. For more information, see Initialization Scenarios.

Prerequisites

You have mounted a cloud disk to your CVM.

Notes

• To protect important data, please see Usage FAQs before operating on your cloud disks.
• Formatting a data disk will erase all data. Make sure that the disk does not contain data, or important data has been backed up.
• To avoid exceptions, make sure before formatting that the CVM has stopped external services.

Directions

Initializing cloud disks (Windows)

This document uses the Windows Server 2008 operating system as an example. The formatting operation varies by operating system. Below is for reference only.

1. Log in to the Windows Cloud Virtual Machine.
2. In the CVM desktop, click Start.
3. Right click Computer in the start menu and select Manage.
4. In the left navigation tree, select Storage>Disk Management to enter the Disk Management page.

If the newly added disk is in offline status (as shown in the figure above), execute Step 5 before Step 6 to perform initialization. Otherwise, you can directly execute Step 6.

5. Disks are listed on the right-side pane. Right click disk 1 area, and select Online to bring it online. The status of disk 1 changes from Offline to Not Initialized.

6. Right click disk 1 area, and select Initialize Disk in the menu.
7. In the Initialize Disk dialog box, the disk you need to initialize is displayed. Select MBR or GPT and click OK.

If the disk partition format is changed after the disk is put into use, the original data on the disk will be erased. Please select an appropriate partition format based on actual needs.

8. Right click the unallocated space of the disk, and select New Simple Volume.
9. In the pop-up New Simple Volume Wizard dialog box, follow instructions on the interface and click Next.
10. Specify the volume size as needed, which is the maximum value by default. Click Next.
11. Assign a drive letter, and click Next.
12. Select Format this volume with the following settings, configure parameters as needed, format the partition, and click Next to complete the partition creation.
13. Click Complete to complete the wizard. Wait for the system to complete the initialization operation. When the volume status becomes Healthy, disk initialization is successful.
    After successfully completing the initialization, enter the Computer interface to view the new disk.

Initializing cloud disks (Linux)

Select the initialization method according to your actual use scenario:

• If the entire disk is presented as one independent partition (i.e., no logical disks such as vdb1 and vdb2), we strongly recommend that you not use partition, and directly create the file system on bare devices.
• If the entire disk is presented as multiple logical partitions (i.e., there are multiple logical disks), you need to perform the partition operation first, and then create the file system on a partition.

Creating file systems on bare devices

1. Log in to the Linux Cloud Virtual Machine.
2. Execute the following command as the root user to view the disk name.

   fdisk -l

   If information similar to what is shown below is returned, the current CVM has two disks, where “/dev/vda” is the system disk and “/dev/vdb” is the newly added data disk.
   
3. Execute the following command to create a file system on the “/dev/vdb” bare device.

   mkfs -t <File system format> /dev/vdb

   The partition size supported by different file systems varies. Select an appropriate file system as needed. The following example takes EXT4 as the file system:

   mkfs -t ext4 /dev/vdb

   The formatting takes a while. Please pay attention to the system’s running status and do not exit.

4. Execute the following command to create a new mount point.

   mkdir <Mount point>

   Take creating a new mount point /data as an example:

   mkdir /data

5. Execute the following command to mount the newly created partition to the newly created mount point.

   mount /dev/vdb <Mount point>

   Take the newly created mount point /data as an example:

   mount /dev/vdb /data

6. Execute the following command to view the mount result.

   df -TH

   If you do not need to configure automatic disk mounting at startup, skip the following steps.

7. Confirm the mount method and obtain the corresponding information.
   Based on business needs, you can use an elastic cloud disk’s soft link, file system’s UUID (universally unique identifier), or device name to automatically mount a disk. The descriptions and information acquisition methods are as follows:

   Mount method	Pros and cons	Information acquisition method
   Use the soft link of the elastic cloud disk(recommended)	Pros:The soft link of an elastic cloud disk is fixed and unique. It does not change with operations such as mounting, unmounting, and formatting partitions. Cons:Only an elastic cloud disk can use the soft link, which operates transparently for the partition formatting operation.	Execute the following command to view the soft link of the elastic cloud disk. ls -l /dev/disk/by-id
   Use the UUID of the file system	Automatic mounting configuration may fail due to changes in a file system’s UUID. For example, reformatting a file system will change its UUID.	Execute the following command to view the UUID of the file system. blkid /dev/vdb
   Use device name	Automatic mounting configuration may fail due to changes in device name. For example, if an elastic cloud disk on the CVM is unmounted and then remounted, the device name may change when the operating system recognizes the file system again.	Execute the following command to view the device name. fdisk -l

8. Run the following command to back up the /etc/fstab file to the /home directory, for example:

   cp -r /etc/fstab /home

9. Execute the following command to use VI editor to open the /etc/fstab file.

   vi /etc/fstab

10. Press i to enter the edit mode.
11. Move the cursor to the end of the file, press Enter, and add the following content.

    <Device information> <Mount point> <File system format> <File system installation option> <File system dump frequency> <File system check sequence at launch>

    • (Recommended) Take automatic mounting using the soft link of an elastic cloud disk as an example. Add the following to the previous example:

      /dev/disk/by-id/virtio-disk-drkhklpe /data ext4 defaults 0 0

    • Take automatic mounting using the UUID of the disk partition as an example. Add the following to the previous example:

      UUID=d489ca1c-5057-4536-81cb-ceb2847f9954 /data  ext4 defaults     0   0

    • Take automatic mounting using the device name as an example. Add the following to the previous example:

      /dev/vdb /data   ext4 defaults     0   0

12. Press Esc, enter :wq, and press Enter.
    Save the configuration and exit the editor.
13. Execute the following command to check whether the /etc/fstab file has been written successfully.

    mount -a 

    If the command runs successfully, the file has been written. The newly created file system will automatically mount when the operating system is launched.

Creating a file system on a partition

This example uses the parted partition tool in the CentOS 7.5 operating system to configure data disk /dev/vdc as the primary partition. GPT is used as the default partition format, EXT4 format as the file system, /data/newpart2 as the mount point, and automatic mounting at startup is configured. The formatting operation varies by operating system. Below is for reference only.

1. Log in to the Linux Cloud Virtual Machine.
2. Execute the following command as the root user to view the disk name.

   fdisk -l

   If information similar to what is shown below is returned, the current CVM has two disks, where “/dev/vda” is the system disk and “/dev/vdb” is the newly added data disk.
   
3. Execute the following command to enter the fdisk partition tool and execute the partitioning operation on the newly added data disk.

   fdisk <Newly added data disk>

   Take the newly mounted data disk /dev/vdb as an example:

   fdisk /dev/vdb

   The returned information is similar to what is shown below:
   
4. Enter n and press Enter to start creating the new partition.
   The returned information is similar to what is shown below:
   
   This indicates that the disk has two partition types:
   • p indicates the primary partition.
   • e indicates the extended partition.
5. Take creating a primary partition as an example. Enter p and press Enter to start creating a new primary partition.
   The returned information is similar to what is shown below:
   
   Partition number indicates the number of the primary partition. You can choose from 1-4.
6. Take selecting partition number 1 as an example. Enter the primary partition number 1 and press Enter.
   The returned information is similar to what is shown below:
   
   First sector indicates the start sector. You can choose from 2048 - 20971519. The default value is 2048.
7. Take selecting default start sector number 2048 as an example. Press Enter.
   The returned information is similar to what is shown below:
   
   Last sector indicates the end sector. You can choose from 2048 - 20971519. The default value is 20971519.
8. Take selecting the default end sector number 20971519 as an example. Press Enter.
   The returned information is similar to what is shown below:
   
   This indicates that partitioning is completed. A new partition has been created on the 60GB data disk.
9. Enter p and press Enter to view the information of the newly created partition.
   The returned information is similar to what is shown below:
   
   This indicates the detailed information of the newly created partition /dev/vdb1.

If the partitioning operation above has an error, enter q to exit the fdisk tool and the prior partition result will not be retained.

10. Enter w and press Enter to write the partition result into the partition table.
    If the returned information is similar to what is shown below, the partition has been created.
    
11. Execute the following command to sync the partition table to the operating system.

    partprobe

12. Execute the following command to configure the file system of the newly created partition to that required by the system.

    mkfs -t <File system format> /dev/vdb1

    The partition size supported by different file systems varies. Select an appropriate file system as needed. The following example takes EXT4 as the file system:

    mkfs -t ext4 /dev/vdb1

    The returned information is similar to what is shown below:
    
    The formatting takes a while. Please pay attention to the system’s running status and do not exit.
13. Execute the following command to create a new mount point.

    mkdir <Mount point>

    Take creating a new mount point /data/newpart as an example:

    mkdir /data/newpart

14. Execute the following command to mount the newly created partition to the newly created mount point.

    mount /dev/vdb1 <Mount point>

    Take the newly created mounting target /data/newpart as an example:

    mount /dev/vdb1 /data/newpart

15. Execute the following command to view the mount result.

    df -TH

    The returned information is similar to what is shown below:
    
    This indicates that the newly created partition /dev/vdb1 has been mounted to /data/newpart.

If you do not need to configure automatic disk mounting at startup, skip the following steps.

16. Confirm the mount method and obtain the corresponding information.
    Based on business needs, you can use an elastic cloud disk’s soft link, file system’s UUID (universally unique identifier), or device name to automatically mount a disk. The descriptions and information acquisition methods are as follows:

    Mount method	Pros and cons	Information acquisition method
    Use the soft link of the elastic cloud disk(recommended)	Pros:The soft link of an elastic cloud disk is fixed and unique. It does not change with operations such as mounting, unmounting, and formatting partitions. Cons:Only an elastic cloud disk can use the soft link, which operates transparently for the partition formatting operation.	Execute the following command to view the soft link of the elastic cloud disk. ls -l /dev/disk/by-id
    Use the UUID of the file system	Automatic mounting configuration may fail due to changes in a file system’s UUID. For example, reformatting a file system will change its UUID.	Execute the following command to view the UUID of the file system. blkid /dev/vdc1
    Use device name	Automatic mounting configuration may fail due to changes in device name. For example, if an elastic cloud disk on the CVM is unmounted and then remounted, the device name may change when the operating system recognizes the file system again.	Execute the following command to view the device name. fdisk -l

17. Run the following command to back up the /etc/fstab file to the /home directory, for example:

    cp -r /etc/fstab /home

18. Execute the following command to use VI editor to open the /etc/fstab file.

    vi /etc/fstab

19. Press i to enter the edit mode.
20. Move the cursor to the end of the file, press Enter, and add the following content.

    <Device information> <Mount point> <File system format> <File system installation option> <File system dump frequency> <File system check sequence at launch>

    • (Recommended) Take automatic mounting using the soft link of an elastic cloud disk as an example. Add the following to the previous example:

      /dev/disk/by-id/virtio-disk-drkhklpe-part1 /data/newpart   ext4 defaults     0   2

    • Take automatic mounting using the UUID of the disk partition as an example. Add the following to the previous example:

      UUID=d489ca1c-5057-4536-81cb-ceb2847f9954 /data/newpart   ext4 defaults     0   2

    • Take automatic mounting using the device name as an example. Add the following to the previous example:

      /dev/vdb1 /data/newpart   ext4 defaults     0   2

21. Press Esc, enter :wq, and press Enter.
    Save the configuration and exit the editor.
22. Execute the following command to check whether the /etc/fstab file has been written successfully.

    mount -a 

    If the command runs successfully, the file has been written. The newly created file system will automatically mount when the operating system is launched.

Related Operations

Initializing cloud disks (larger than or equal to 2TB).