xenial image fails to mount rootfs

Bug #1718415 reported by Markos Chandras
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
diskimage-builder
Fix Released
Undecided
Unassigned

Bug Description

Hi,

We are building a Xenial image using DIB_RELEASE=xenial and the following command

disk-image-create --no-tmpfs -o deployment_image.qcow2 -t qcow2 -p "vlan,vim,less,bridge-utils,language-pack-en,iputils-ping,rsyslog,curl,iptables,lvm2" ubuntu-minimal vm enable-serial-console simple-init devuser growroot openssh-server

This however results in the following error when booting the image

[ 2.279933] VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0,0): error -6
[ 2.294251] Please append a correct "root=" boot option; here are the available partitions:
[ 2.308070] 0800 1791552 sda driver: sd
[ 2.316631] 0801 1789504 sda1 15cbceb6-01
[ 2.325394] 0b00 1048575 sr0 driver: sr
[ 2.333875] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.337844] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-96-generic #119-Ubuntu
[ 2.337844] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
[ 2.337844] 0000000000000086 8d281f2c43cdce82 ffff88013ab87de8 ffffffff813fabd3
[ 2.337844] ffffffff81ca6028 ffff88013ab87e80 ffff88013ab87e70 ffffffff8118d967
[ 2.337844] 6230002000000010 ffff88013ab87e80 ffff88013ab87e18 8d281f2c43cdce82
[ 2.337844] Call Trace:
[ 2.337844] [<ffffffff813fabd3>] dump_stack+0x63/0x90
[ 2.337844] [<ffffffff8118d967>] panic+0xd3/0x215
[ 2.337844] [<ffffffff81f5f576>] mount_block_root+0x201/0x294
[ 2.337844] [<ffffffff81f5f66e>] mount_root+0x65/0x68
[ 2.337844] [<ffffffff81f5f7ab>] prepare_namespace+0x13a/0x172
[ 2.337844] [<ffffffff81f5f21b>] kernel_init_freeable+0x1e9/0x212
[ 2.337844] [<ffffffff81836ad0>] ? rest_init+0x80/0x80
[ 2.337844] [<ffffffff81836ade>] kernel_init+0xe/0xe0
[ 2.337844] [<ffffffff8184360f>] ret_from_fork+0x3f/0x70
[ 2.337844] [<ffffffff81836ad0>] ? rest_init+0x80/0x80

I have attached the entire log for the build

I also noticed that the final image misses an initrd file in /boot which may be the reason for the failure.

Revision history for this message
Markos Chandras (hwoarang) wrote :
Revision history for this message
Markos Chandras (hwoarang) wrote :

This line is also interested in the log

Installing GRUB2...
Installing for i386-pc platform.
Installation finished. No error reported.
/tmp/in_target.d/finalise.d/50-bootloader: line 160: type: grub2-mkconfig: not found
Generating grub configuration file ...

Revision history for this message
Markos Chandras (hwoarang) wrote :

Hmm that's actually from another log

Revision history for this message
Andreas Florath (ansreas) wrote :

I was able to reproduce this bug with DIB from master branch.

Changed in diskimage-builder:
status: New → Confirmed
Revision history for this message
YuZhang (ivysdu) wrote :

I also encountered this issue today, and I tried to generate the initrd to /boot, but still could not fix this issue.

Revision history for this message
Ian Wienand (iwienand) wrote :

I believe this is fixed with https://review.openstack.org/#/c/505857/

however, master still has issues with networkx. please try again with the 2.9.0 release when it is made

Changed in diskimage-builder:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.