On further testing, this issue is limited to server, as desktop is producing the correct boot order. This serves to greatly limit the affected scope of users.
** Description changed: when attempting to do-release upgrade zfs encrypted, grub-install fails like follows: --- Setting up grub-efi-amd64 (2.12-5ubuntu5.1) ... Replacing config file /etc/default/grub with new version Installing grub to /boot/efi. Installing for x86_64-efi platform. grub-install: error: /boot/efi doesn't look like an EFI partition Configuring grub-efi-amd64 -------------------------- GRUB failed to install to the following devices: /dev/vda1 (side note: correct device) Do you want to continue anyway? If you do, your computer may not start up properly. --- grub-install -v --force /dev/vda1 adds the following info --- grub-install: info: executing modprobe efivars 2>/dev/null grub-install: info: Looking for /sys/firmware/efi ... grub-install: info: ...found. Installing for x86_64-efi platform. grub-install: info: cannot open `/boot/grub/device.map': No such file or directory. grub-install: error: cannot find EFI directory. --- Seen on both noble->oracular and oracular->plucky. I have only tested zfs encrypted installs so far but I speculate that zfs unencrypted has the same fate. + + --- + + Workaround: modify /etc/fstab, add "x-systemd.after=zfs-mount.service" + to the /boot/efi entry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107408 Title: do-release-upgrade on zfs encrypted, "/boot/efi doesn't look like an EFI partition" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2107408/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
