What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?
Symptom
An ECS created from a private image booting to UEFI cannot start.
Possible Causes
The image is configured for UEFI boot, but the uefi attribute was not added to the image.
Solution
- Delete the ECS that failed to start.
- Call the API to update the image attributes and change the value of hw_firmware_type to uefi.
API URI: PATCH /v2/cloudimages/{image_id}
For details about how to call the API, see Updating Image Information.
- Use the updated image to create an ECS.
ECS Creation FAQs
- Can I Change the Image of a Purchased ECS?
- Can I Change the Specifications Defined by a Private Image When I Use the Image to Create an ECS?
- Can I Specify the System Disk Capacity When I Create an ECS Using an Image?
- What Do I Do If a Partition Is Not Found During the Startup of an ECS Created from an Imported Private Image?
- What Do I Do If the Disks of a CentOS ECS Created from an Image Cannot Be Found?
- What Do I Do If I Enabled Automatic Configuration During Image Registration for an ECS Created from a Windows Image and Now It Won't Start?
- What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore