Good evening,
I've been trying to configure a Full Disk Encryption (FDE) device for a week
and i'm currently stuck in a problem I'm not able to solve (already fixed lots
of problems during this week).
The device is a UEFI device and I'm currently able to boot into the initrd (so
all the crypt setup is good).
The thing is that i've configured the encrypted disk as a BTRFS filesystem with
--checksum xxhash (xxhash64 as btrfs decided), --metadata single, -n 32k (so
nodesize of 32KiB). I give you this info in case it helps with helping out.
When booting into the initrd I get this error that says that it's unable to
open the filesystem because no xxhash64 hash is available.
From this message I understand that probably the initrd is lacking the xxhash64
module in order to read the btrfs filesystem.
So how do I specify to the operative-system config the initrd-module so it gets
built and loaded? I know there is the operative-system keyname/field
initrd-modules that I can supply with an improper list with modules to load.
But which is the correct name for the xxhash64 module? From internet I got that
there's a xxhash-generic module for the linux kernel. Would that work
("xxhash-generic")?
Apart from that, is it posible to chroot into the guix system without having to
do the whole "guix system init ..." stuff?
I've tried what the "System troubleshooting tips" of the guix ref manual says
but since i've never fully booted into the system I lack a user (root or
whatever).
With that bare minimums when I try to chroot into the system, i'm unable to
start the guix-daemon for building and I also lack some channels I require for
my system.
Well if the only possibility is going with the live install it's okay. I'll
just need to configure the btrfs volumes again. At this point i think I have
the steps burned in my brain hahahhaha. And the config.scm is totally
recoverable from the store, so no problem with that.
Thank you in advance.
Best regards,
--
Marius.
