Home  >  Article  >  Operation and Maintenance  >  Why do you need to annotate the mount items when creating a custom image using ECS?

Why do you need to annotate the mount items when creating a custom image using ECS?

坏嘻嘻
坏嘻嘻Original
2018-09-29 16:27:332634browse

The content of this article is about why ECS needs to annotate mount items when creating a custom image creation server. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Why ECS needs to comment on the mount item when creating a custom image server

When using a custom image to create an ECS instance, the following reasons may cause the disk to fail to mount:

Create The instance does not have a data disk

The data disk is a new disk and has not been partitioned and formatted

The created custom image does not remove the disk mounting entry in /etc/fstab

You can see the following picture indicating that there is currently no partition:

Why do you need to annotate the mount items when creating a custom image using ECS?

And you can see that in the ECS instance created by the custom image, the disk mount is not removed from /etc/fstab Entry:

Why do you need to annotate the mount items when creating a custom image using ECS?

When the instance starts, the disk will be mounted according to the settings in the fstab file, but the mounting fails because there is no partition:

Why do you need to annotate the mount items when creating a custom image using ECS?

There is no need to comment on the disk mounting situation. Generally, the data disk can only be selected when creating the server, and the data disk is generated from a partitioned and formatted data disk snapshot.

Why do you need to annotate the mount items when creating a custom image using ECS?

The above is the detailed content of Why do you need to annotate the mount items when creating a custom image using ECS?. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn