I had time to revisit this. I think the user property thing is the way
to go. The installer would just mark the entire pool as a pool that is
considered bootable.
kyle@optional:~$ zfs get zsys:bootable rpool
NAME PROPERTY VALUE SOURCE
rpool zsys:bootable - -
I ran into this issue too after setting up dual boot with FreeBSD on my
system. An unattended upgrade wiped out my grub menu since it mistook
the "etc" dataset in the FreeBSD zfs pool as a signal that it contained
an Ubuntu install.
The hack described by Benjamin worked for me, although it
This bug affects me too, but the 'quick fix' suggested doesn't work
either for some reason.
I tried lots of ways to work around this by modifying the 10_linux_zfs
file, but they all failed. I don't have the coding skills apparently!
I could do with a fix for this as I'm relying on it to rebuild
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850003
Title:
