FWIW: /usr/sbin/grub-probe is also posixly incorrect, e.g.: # export POSIXLY_CORRECT=1 # /usr/sbin/grub-probe --device /dev/sda2 --target=partmap /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check your device.map.
# unset POSIXLY_CORRECT # /usr/sbin/grub-probe --device /dev/sda2 --target=partmap gpt So e.g. if one has POSIXLY_CORRECT set, but not GRUB_TERMINAL (the default in /etc/default/grub), /etc/grub.d/00_header assumes gfxterm and therefore indirectly calls /usr/share/grub/grub-mkconfig_lib:prepare_grub_to_access_device() - which in turn fails, because it calls /usr/sbin/grub-probe w/o unsetting POSIXLY_CORRECT before. Since this aborts grub.cfg generation, a disaster recovery is needed on the next reboot if there is not already an old grub.cfg which is able to boot a kernel ... If one sets GRUB_TERMINAL=console , mkconfig_lib:prepare_grub_to_access_device() doesn't get invoked and update-grub and in turn grub-mkconfig -o /boot/grub/grub.cfg generates a valid/usable config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897785 Title: 10_linux_zfs: empty bootmenu if POSIXLY_CORRECT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1897785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
