• Cause:

    Attaching a volume to a VM instance is a dynamic operation, while the /etc/fstab configuration file for the VM instance is static. After attaching the volume to the VM instance, you modify the fstab file of the VM instance, encapsulate the VM instance as an image online, and use this image to create another new VM instances. The fstab file does not contain the corresponding mount information so that the created VM instances are hung and cannot be started,

  • Solution:
    • After the Linux VM instance attaches the volume, we recommend that you do not modify the /etc/fstab file.
    • Recommended method:
      • Go to /etc/rc.d/rc.local, and run mount to mount the volume:
        # chmod +x /etc/rc.d/rc.local
# mount -U <the file system UUID> <the target mount path>
        Note: We recommend that you use the file system UUID of the volume to mount the VM instance rather than use the drive letter similar to /dev/vdb.