On 08/06/18 18:48, Xen wrote: > John Lane schreef op 08-06-2018 15:10: > >> I'm trying unsuccessfully to create a ZFS zpool that I can read in Grub. > > Haven't done it myself yet but it seemed there were plenty of tutorials. > > One thing to note is that on Solaris, you could not boot from a pool > that has > a separate cache, but that might not even apply to Grub. > > The only thing I've remembered, is that you do have to use filesystem > volumes, > and not any zvols - but grub should have a parameter syntax to select > the filesystem volume. > > Also do zpools themselves not have a boot parameter? > > bootfs=pool/dataset > > Identifies the default bootable dataset for the root pool. > This property is expected to > be set mainly by the installation and upgrade programs. > > I'm sorry I cannot offer anything more, but your problems are also > rather unspecific.
Thanks for your reply. All that I am trying to do at this stage is create a zpool that I can read in Grub. I am not (yet) trying to boot anything - just prove that the boot files on the zpool can be accessed from Grub. I have created a filesystem volume but I cannot read it. I've tried various features enabled and disabled without success. When I do "ls (hd1,1)/ROOT/archlinux@/boot' I get errors for each file about the compression algorithm not being supported. Enabling or disabling lz4_compress does not help. I have used the zfsinfo module to confirm that Grub does know it's a zfs pool. The detail is on the linked post [1] but I can repeat it here if it helps. [1] https://unix.stackexchange.com/questions/447960 Thanks. > > Regards. > > _______________________________________________ > Help-grub mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/help-grub > _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
