Bug#848945: grub-common: Empty rpool leaves ZFS systems unbootable

2022-05-20 Thread Stefan Bühler
Hi, this bug is really annoying... How about using this simple line instead? LINUX_ROOT_DEVICE="ZFS=$(findmnt --direction backward --first-only --noheadings -o SOURCE /)" "--direction backward" should find the "active mount" first (in case there are multiple mounts on "/"). cheers, Stefan

Bug#848945: grub-common: Empty rpool leaves ZFS systems unbootable

2021-03-09 Thread наб
Control: found -1 2.04-16 GRUB still runs /usr/sbin/grub-probe --device /dev/vdb1 /dev/vda3 /dev/vdd1 /dev/vde1 --target=fs_label for me which writes (started writing recently? possibly something to do with pool upgrade) /usr/sbin/grub-probe: error: unknown filesystem. to the stderr and leave

Bug#848945: grub-common: Empty rpool leaves ZFS systems unbootable

2017-02-07 Thread Chris Zubrzycki
Good patch, except my root dataset has a - in it’s name, it’s called debian-2 and each major upgrade gets a new version… Please change the grep line to use grep -P -v '\s-‘ zfsbootfs=`zpool get bootfs | sed '2,100!d' | grep -P -v ‘\s-' | awk {'print $3'} 2>/dev/null || true` Nothing in that

Bug#848945: grub-common: Empty rpool leaves ZFS systems unbootable

2016-12-20 Thread John Goerzen
Package: grub-common Version: 2.02~beta2-22+deb8u1 Severity: important This problem likely stems from the use of grub-probe in grub-mkconfig. For a zpool, grub-probe may very well display several lines of information. Unfortunately, an analysis of strace shows all this goes into GRUB_DEVICE and