In short: I want to boot Void off of a zfs dataset (using legacy mounts, but that’s irrelevant here), and i can, without problems, build zfs and dependencies on the host/installation system, but it fails in the chroot to the new system. (I can boot the kernel from GRUB, but it doesn’t get past the kernel messages because it has no root)
I have, by now, only one zfs dataset for Void (mostly because this is just a test run, the actual install will have multiple datasets), which is
On the install system (which has zfs built successfully), i mount that dataset using
mount -t zfs data/void /mnt, which works just fine.
I then run
for dir in dev proc run sys; do mount --rbind /$dir /mnt/$dir; done to mount the needed directories, followed by a
chroot /mnt /bin/bash.
Inside the chroot, i installed zfs using
xbps-install -S zfs. I didn’t notice it failed for some time, because it literally says “FAILED” and nothing else. That’s why i know the kernel boots properly - i have tried to boot it multiple times and it worked, except for the missing zfs support of course.
No matter what i try (mostly editing dracut config files), i can’t get it to build inside the chroot. I have tried multiple kernel versions as well.
What could be the issue? How can i see why exactly it fails, and not just FAILED?
Thanks in advance