← Production Guide · VM lifecycle
PG-32 · Boot from volume fails?¶

Operational lesson. The fault names the volume. Read its status and Cinder's message before you retry.
The memo as text¶
Situation. Local-disk instances build fine. Those whose root disk is a Cinder volume are refused, go to ERROR, or boot nothing.
First checks (read-only):
- Status and fault of the instance:
openstack server show <id> -c status -c fault - The volume of the build:
openstack volume show <volume> -c status -c bootable - Cinder's own explanation:
openstack --os-volume-api-version 3.3 volume message list - Are the volume services up?:
openstack volume service list
Think before acting:
- ⛔ Avoid. Retrying blindly. Each retry from an image creates another volume, which counts in the quota and fills the backend.
- 🛑 Destructive. Deleting the failed instance also deletes its volume when "Delete On Termination" is true.
Go deeper¶
This memo is a memory aid. The procedure, with every command, its risk warning and its limits, is in the runbook:
- Instance fails to boot from volume. ERROR at build, or ACTIVE with no bootable disk ·
lab-verifiedon 2026.1 · highest risk in the page: destructive - Volume stuck in creating, or in error right after create ·
lab-verifiedon 2026.1 · highest risk in the page: destructive
Where this holds. Written from the Nova and Cinder 2026.1 sources; its five causes were partly reproduced on an all-in-one lab with Cinder LVM over iSCSI. The three minutes are Nova's default wait (block_device_allocate_retries). Cinder 2026.1 refuses a qcow2 image declared raw: the volume goes to error, it is not written as it is. Fixing an image property and rebooting does not help: the instance keeps the properties copied at build time. Fault wording varies with the client and microversion. Ironic and encrypted volumes are not covered.
LinkedIn kit¶
- Image:
dist/pg-32-boot-from-volume-fails.png(1080 × 1350) - Post title: Boot from volume fails: Nova reports it, Cinder explains it
Instances with a local disk build fine. The ones that boot from a volume do not.
What happens tells you where to look:
→ refused at once, no instance: the request itself. Volume smaller than the image's min_disk, a volume that is not bootable, no boot index 0.
→ ERROR, the volume in "error" or still "creating": Cinder. It failed, or the volume was not ready when Nova stopped waiting, after about three minutes by default.
→ ERROR with "Exceeded maximum number of retries", the volume "available": the compute. It could not connect to the volume, and neither could the others.
→ ACTIVE, but nothing boots: what the volume holds. A blank volume marked bootable, or an image that needs a firmware or disk bus the instance did not get.
For a volume in error, Cinder usually says why in one line: openstack volume message list.
What not to do: retry in a loop. Each retry from an image creates another volume, which counts in the quota.
Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/scheduling/instance-fails-to-boot-from-volume.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production
#OpenStack #Nova #Cinder #Storage #CloudOperations #OzarLand
Source: boot-from-volume-fails.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.