After enabling CONFIG_EFI_STUB=y both of my machines will not boot from filesystem UUID. The rootfs on both machines is a btrfs subvolume on an nvme partition. On boot, the kernel panics that it can't find the rootfs: kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)
If I either specify by device path (/dev/nvme0n1p2 and /dev/nvme0n1p3 for the two machines) or by PARTUUID, it can find it and boot. I haven't investigated why the kernel can't find the filesystems by fs UUID, but they are not available after the EFI handover. To workaround it, I have set these options in /etc/default/grub: GRUB_DISABLE_LINUX_UUID=true GRUB_DISABLE_LINUX_PARTUUID=false This forces grub to pass the PARTUUID instead of the fs UUID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
