Citrix Hypervisor Cannot Boot VM - Inaccessible_boot_device
Article ID: CTX245905
Updated On:
Description
After booting the VM an "Inaccessible Boot Device" error appears. The error may also appear as "The boot selection failed because a required device is inaccessible".
This may be a critical VM that needs to be restored fast.
Resolution
Troubleshooting Steps
- Make sure that the VM has a disk attached. Select the VM and go to the Storage tab in XenCenter. An upgrade or some other activity may unintentionally alter the metadata and loose the link between the VM and its disk.
- If the VM has multiple disks, try only attaching the boot disk. After it recognizes the boot disk you can attach the other disk.
- Try creating a new VM and attaching the existing disk. This will rule out if ti is an issue with the VM metadata. If it does not start, it could be a problem with the disk.
- If the problem started after an upgrade, take one host out of the pool and downgrade it to the previous version. Copy the VM to that host and start it. This can be useful to get it back up while the problem is troubleshooted by Citrix Support.
- Check / repair boot environment variables. If it is a Windows VM:
Insert the OS installation disk
Select Next > Repair your computer
Select Next > Command Prompt
Change directory (cd) to X:\sources\recovery, then type StartRep.exe to launch a repair utility which corrects boot environment values. This step may require more than one attempt.
If previous step fails, open the command prompt and type bcdedit. This will display the values for Windows Boot Manager.
Review the values for Device. Is it set to unknown, as shown below? If so, proceed.
At the command prompt, type the following commands (c: is the default system partition. If you original partition was another drive letter, this value can be set to that drive letter):
bcdedit /set {DEFAULT.EN_US} device partition=c:
bcdedit /set {DEFAULT.EN_US} osdevice partition=c:
bcdedit /set {BOOTMGR.EN_US} device partition=c:
Reboot the system after rebooting the OS disk.
- A final option is to rebuild the problem VM.
- Make sure that the VM has a disk attached. Select the VM and go to the Storage tab in XenCenter. An upgrade or some other activity may unintentionally alter the metadata and loose the link between the VM and its disk.
- If the VM has multiple disks, try only attaching the boot disk. After it recognizes the boot disk you can attach the other disk.
- Try creating a new VM and attaching the existing disk. This will rule out if ti is an issue with the VM metadata. If it does not start, it could be a problem with the disk.
- If the problem started after an upgrade, take one host out of the pool and downgrade it to the previous version. Copy the VM to that host and start it. This can be useful to get it back up while the problem is troubleshooted by Citrix Support.
- Check / repair boot environment variables. If it is a Windows VM:
Insert the OS installation disk
Select Next > Repair your computer
Select Next > Command Prompt
Change directory (cd) to X:\sources\recovery, then type StartRep.exe to launch a repair utility which corrects boot environment values. This step may require more than one attempt.
If previous step fails, open the command prompt and type bcdedit. This will display the values for Windows Boot Manager.
Review the values for Device. Is it set to unknown, as shown below? If so, proceed.
At the command prompt, type the following commands (c: is the default system partition. If you original partition was another drive letter, this value can be set to that drive letter):
bcdedit /set {DEFAULT.EN_US} device partition=c:
bcdedit /set {DEFAULT.EN_US} osdevice partition=c:
bcdedit /set {BOOTMGR.EN_US} device partition=c:
Reboot the system after rebooting the OS disk.
- A final option is to rebuild the problem VM.
Problem Cause
Different possible causes.
Was this article helpful?
Yes
No
Powered by
