What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?
Symptom
An ECS created from a private image using the UEFI boot mode cannot start.
Possible Causes
The image OS uses the UEFI boot mode, but the uefi attribute is 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 Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?
- Can I Specify the System Disk Size When I Create an ECS Using an Image?
- What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?
- What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?
- What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Configuration During Image Registration?
- What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?
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