This is a quick heads-up for folks who use grub, have their root filesystem on ZFS and boot from
it with an initramfs (i.e. not directly from grub), and have fully upgraded their pool to 2.2.2.
In that configuration, grub-mkconfig (grub-probe, actually) fails to recognize the pool, and it
generates a bad kernel command-line. For example, if you normally have:
root=ZFS=POOL/root/gentoo
in your kernel command-line, after updating to 2.2.2 and upgrading your pool, grub-mkconfig will
instead set the following, without warning:
root=ZFS=/root/gentoo
That is, the pool name is missing. This is due to grub-probe not recognizing the pool due to the
com.klarasystems:vdev_zaps_v2 feature, among others.
So, please double-check the output of grub-mkconfig and fix the root= entry.
(I've been trying to paper over the issue with a quick patch to grub, but unsuccessfully so far;
apparently the feature above isn't the only one causing issues.)
-- Remy
it with an initramfs (i.e. not directly from grub), and have fully upgraded their pool to 2.2.2.
In that configuration, grub-mkconfig (grub-probe, actually) fails to recognize the pool, and it
generates a bad kernel command-line. For example, if you normally have:
root=ZFS=POOL/root/gentoo
in your kernel command-line, after updating to 2.2.2 and upgrading your pool, grub-mkconfig will
instead set the following, without warning:
root=ZFS=/root/gentoo
That is, the pool name is missing. This is due to grub-probe not recognizing the pool due to the
com.klarasystems:vdev_zaps_v2 feature, among others.
So, please double-check the output of grub-mkconfig and fix the root= entry.
(I've been trying to paper over the issue with a quick patch to grub, but unsuccessfully so far;
apparently the feature above isn't the only one causing issues.)
-- Remy