Ask Your Question
0

Boot failed. Could not read the boot disk

asked 2013-05-09 09:23:28 -0500

khoivu gravatar image

updated 2013-05-21 13:57:18 -0500

smaffulli gravatar image

I successfully launched an instance. However, I could not ping or ssh into that running instance. By viewing the instance's console log, I found out that

Booting from hard disk
Boot failed. not a bootable disk
Booting from ROM
DHCP (net0: fa:16:3e:3e: 23:aa:bd)
No more network drivers
Booting from floppy
Boot failed. Could not read from the boot disk.
No boot table device

Openstack dashboard shows that the instance is running without any errors (status is Active). What is wrong about the image? why it is running but its log is saying it is not bootable?

Nova logs show:

# cat /var/log/nova/compute.log
2013-05-09 10:58:23.063 WARNING nova.virt.disk.api [req-fb03d308-6390-4b0a-bb68-02a1fe896a7b e8ed005baf2d4999a7680899e0a27450 654ae45fb88241de9a80e228fa47edf8] Ignoring error injecting data into image (No operating system found in /var/lib/nova/instances/fe3c1bd4-4e48-4ae6-8efd-ae03b103028b/disk)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-05-09 14:56:13 -0500

khoivu gravatar image

The cirros qcow2 images I downloaded from https://launchpad.net/cirros/+download seems corrupted and do not work. But the fedora 16 qcow2 images I downloaded from http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack-sda.qcow2 (this page)works

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-05-09 09:23:28 -0500

Seen: 2,981 times

Last updated: May 21 '13