image won't boot after upgrading to yakkety's 4.8 kernel because efi
Bug #1626158 reported by
Tycho Andersen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Tim Gardner | ||
Xenial |
New
|
Critical
|
Unassigned |
Bug Description
If I use a relatively recent yakkety daily with uvt-kvm,
com.ubuntu.
and upgrade the kernel to the latest kernel (which happens to be 4.8), my VM won't boot any more. kern.log has:
http://
and systemd complains that,
[FAILED] Failed to mount /boot/efi
See 'systemctl status boot-efi.mount' for details.
and dumps me to a recovery console. Of course, I don't have EFI since I'm booting this thing on KVM. The problem here (I think) is that /boot/efi is in /etc/fstab, and systemd fails to boot when anything in /etc/fstab doesn't work.
If I comment /boot/efi out of /etc/fstab, it boots just fine.
Changed in cloud-images: | |
status: | Confirmed → Incomplete |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in cloud-images: | |
status: | Incomplete → Fix Released |
To post a comment you must log in.
requested by smoser,
yakkety:~ cat /proc/partitions
major minor #blocks name
254 0 31457280 vda cloudimg- rootfs" UUID="072136f3- 5666-4381- 83bd-8d7175059b e3" TYPE="ext4" PARTUUID= "651ee987- 3881-4315- 91bd-7b4fa084d7 1a" "035f3d9d- e9a5-47ef- 9d4a-22911a283a 10" 09-21-08- 57-02-00" LABEL="cidata" TYPE="iso9660"
254 1 31343599 vda1
254 14 4096 vda14
254 15 108544 vda15
254 16 366 vdb
yakkety:~ blkid
/dev/vda1: LABEL="
/dev/vda15: LABEL="UEFI" UUID="5EC7-12FA" TYPE="vfat" PARTUUID=
/dev/vdb: UUID="2016-