[Bug 1923865] Re: Bootable buildd xenial images go to initramfs on boot
Gauthier Jolly
1923865 at bugs.launchpad.net
Thu Apr 22 07:58:02 UTC 2021
Hi,
Checking the cmdline, the root filesystem is not set:
/boot/vmlinuz-4.4.0-21-generic root= ro quiet splash $vt_handoff
If I change it to "root=PARTUUID=fb561bdb-b68a-44ae-a884-a5fd70f80cf7"
it's booting.
I see also two other errors during boot:
[ 0.075065] core perfctr but no constraints; unknown hardware!
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/vda1
fsck exited with status code 8
The fsk issue is also present in the bionic images I tried but not the
perfctr one.
I just think something went/was wrong when grub was updated during
build.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1923865
Title:
Bootable buildd xenial images go to initramfs on boot
Status in cloud-images:
Confirmed
Status in livecd-rootfs package in Ubuntu:
New
Bug description:
This image:
http://cloud-
images.ubuntu.com/daily/server/buildd/daily/xenial/current/xenial-
server-cloudimg-amd64-disk.img
Fails to boot, with either UEFI or MBR:
```
error: can't find command `hwmatch'.
error: no such device: root.
```
Then it goes straight into initramfs.
Every once in a while there's more context written:
```
mount: can't find /root in /etc/fstab
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesstem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
...
No init found. Try passing init= bootarg.
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1923865/+subscriptions
More information about the foundations-bugs
mailing list