Boot failed: Not a bootable disk

Latest response

Hi,

Today I ran a failover test. Kill one of the hypervisors (power off via Remote access, not the best way I know).
All VMs was running fine prior to the failover.
3 of 5 was successfully restarted on another hypervisor.

But 2 of the VMs can't boot with the following in console: "Boot failed: Not a bootable disk".
All the VMs are using the same SAN.
The VMs has a bootable disk in the "Disks" tab and status is OK.
The VMs has two disks, one which isn't bootable (app data).

I guess I will have to open a support case. But has anyone seen this before?

pa
Log in to join the conversation

Responses

DR Active Contributor 307 points
21 May 2013 8:54 AM

Hi,

Try to deactivate and then activate the appdata-disk and see if the vm boots.

/Brian

pa Expert 917 points
21 May 2013 8:58 AM

Brian,

That worked. Thanks.

pa Expert 917 points
21 May 2013 9:01 AM

This is how I got it to work again:

1. Deactivate the non-bootable disk.
2. Poweron the VM.
3. Shutdown from OS (tried to activate the deactivated disk, but that failed).
4. Activate the non-bootable disk with VM powered off

DR Active Contributor 307 points
21 May 2013 9:12 AM

Cool, glad that helped.

When we had the issue, which still occurs from time to time, only step 1 and 4 is necessary to resolve it.

pa Expert 917 points
21 May 2013 9:45 AM

Not for me though.
The VM has to be powered down for activating the disk again, else I get:
"Failed to plug the disk <disk name> on VM <vm name>"

pa Expert 917 points
21 May 2013 9:51 AM

Did you open a support case about it?

DR Active Contributor 307 points
21 May 2013 10:22 AM

Hi,

Yes, the vm needs to be down when you deactive/activate the disk(s), but I don't think its necessary to boot inbetween.

And I never got around to opening a support case...

/Brian

Sadique Puthen's picture Red Hat Guru 4649 points
21 May 2013 4:12 PM

There is a bug already filed for this. Please open a case even if you have resolved this as more the customers report this issue (which increases the bug's priority) the faster we could release a fix.

pa Expert 917 points
22 May 2013 7:16 AM

Already done.

pa Expert 917 points
22 May 2013 8:19 AM

It happend again and I tried what you said.
So, these steps solves the issue,

1. Poweroff the VM
2. Deactivate the non-bootable disk(s)
3. Activate the non-bootable disk(s)
4. Power on the VM

Thanks for the help Brian.

pa Expert 917 points
10 June 2013 6:10 AM

FYI: The related BZ for this:

https://bugzilla.redhat.com/show_bug.cgi?id=967268
pa Expert 917 points
16 July 2013 1:46 PM

FYI: The bug has been closed.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.