I created a bunch of GPT partition schemes with the EF02 boot loader partition (sdX1), a 32G partition (sdX2), and then a 1.4TB partition (sdX3) in the remaining space.
If I "zpool create -R /mnt -o ashift=12 r raidz2 /dev/sd[abcdefghijk]2", grub-probe is happy to report that /mnt/r is indeed of type zfs. If, however, I then also "zpool create -R /mnt -o ashift=12 z raidz2 /dev/sd[abcdefghijk]3", then grub-probe bails out with "unknown filesystem" and if I run with "-vv" it complains of a fletcher4 checksum failure. Running "zpool destroy z" makes everything happy again, running "zpool create ... z ..." makes things sad again.
I don't know if this is a grub-probe-specific bug or, more generally, a grub bug, as I have only now discovered it and have not been able to boot the system because of it.
ETA: Nope, not just grub-probe; having created the second zpool on these disks, grub can't boot and believes that "(hd0,gpt2)/" is an unknown filesystem. "(hd0,gpt3)/" on the other hand, still works.
I created a bunch of GPT partition schemes with the EF02 boot loader partition (sdX1), a 32G partition (sdX2), and then a 1.4TB partition (sdX3) in the remaining space.
If I "zpool create -R /mnt -o ashift=12 r raidz2 /dev/sd[abcdefghijk]2", grub-probe is happy to report that /mnt/r is indeed of type zfs. If, however, I then also "zpool create -R /mnt -o ashift=12 z raidz2 /dev/sd[abcdefghijk]3", then grub-probe bails out with "unknown filesystem" and if I run with "-vv" it complains of a fletcher4 checksum failure. Running "zpool destroy z" makes everything happy again, running "zpool create ... z ..." makes things sad again.
I don't know if this is a grub-probe-specific bug or, more generally, a grub bug, as I have only now discovered it and have not been able to boot the system because of it.
ETA: Nope, not just grub-probe; having created the second zpool on these disks, grub can't boot and believes that "(hd0,gpt2)/" is an unknown filesystem. "(hd0,gpt3)/" on the other hand, still works.