[Bug 1834095] Re: update-grub fails on zfs with root and boot datasets
Didier Roche
didrocks at ubuntu.com
Tue Jun 25 16:02:51 UTC 2019
Thanks for the results!
Can you run "zfs get all bpool/BOOT/ubuntu" please?
I'm a little bit puzzled about this line:
bpool/BOOT/ubuntu 121M 246M 120M legacy
legacy means you have a manual mountpoint set on this dataset. How do you mount it? Can you paste your /etc/fstab (I guess you put it there?)
I wonder if <pool>/BOOT/ was hardcoded in some way and it had a way to
detect dataset was mounted.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834095
Title:
update-grub fails on zfs with root and boot datasets
Status in grub2 package in Ubuntu:
Incomplete
Bug description:
This issue was encountered on a virtual machine installation of Ubuntu
19.10 running zfs. After reloading several times from backup and
placing the original version of grub2 on hold it was verified that
upgrading to the newer version of grub caused update-grub to
improperly detect the two zfs datasets, bpool (boot pool) and rpool
(root pool).
To recap:
1) lsb_release -rd
Description: Ubuntu Eoan Ermine (development branch)
Release: 19.10
2) apt-cache policy grub-pc
grub-pc:
Installed: 2.02+dfsg1-12ubuntu2
Candidate: 2.02+dfsg1-12ubuntu3 (version with issue in this report)
Version table:
2.02+dfsg1-12ubuntu3 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
*** 2.02+dfsg1-12ubuntu2 100
100 /var/lib/dpkg/status
3) What I expected to happen: update-grub runs without error
4) What happened instead: update-grub did not run correctly, resulting in unbootable system (only entries for memtest86+ in grub menu).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1834095/+subscriptions
More information about the foundations-bugs
mailing list