I think I worked this out. You are able to execute an update-grub even if your pools are not correctly imported into zfs.
I noticed the list looked like this: $> zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool 1.84T 141G 1.71T - - 1% 7% 1.00x ONLINE - After an import of the bpool. $> sudo zpool import bpool. Now looks like $> zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT bpool 1.88G 285M 1.60G - - 0% 14% 1.00x ONLINE - rpool 1.84T 141G 1.71T - - 1% 7% 1.00x ONLINE - And the grub scripts once again starts behaving. A full reinstall of the latest *47 kernel now correctly updates the boot selection list and lets me boot into the correct kernel. I still see this as a bug in the grub scripts. If the bpool is not correctly imported the scripts should either try to do this or - maybe even better - simply exit with a descriptive error. Also when the grub-probe executable gets an error - see to it it prints out exactly where (on which device) the failing probe was running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084584 Title: GRUB / ZFS - unable to detect new kernels installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2084584/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
