On Sun, Jun 5, 2022 at 2:28 PM Barry Scott <barry(a)barrys-emacs.org&gt; wrote: Need logs. And it might help to have the exact same binaries available in A vs B config, i.e. LUKS LVM ext4 vs LUKS Btrfs, but both are Fedora 36. I don't know that much about tang or clevis, but my understanding is the central aspect is `clevis luks unlock` and once the LUKS volume is unlocked, then libblkid should see the btrfs volume on it, and then possible to mount it. While the LUKS volume is locked, the Btrfs volume in effect is invisible (all ciphertext) so the fact it's btrfs is obscured and can't be a factor until the LUKS volume is unlocked. So I'm thinking unlock problems are unrelated to the fs selection, and it's some other factor (package versions, network latency, race condition). -- Chris Murphy

On 6/10/22 11:29, Barry Scott wrote: I'd start by looking at "journalctl -b0" You might be able to find clevis information in there. Another interesting item might be to run "ls -l /boot/initramfs-$(uname -r).img > initramfs-$(hostname)" and to diff the two resulting files.

I have been slowly reproducing the issue and checking logs. I found an error from clevis - no network! The initramfs does not contain any code to bring up the network. On the system that works I use systemd-networkd and that is in the initramfs. But on the system that does not work its was using NetworkManager and the initramfs has not network modules init. I changed the system to use systemd-networkd and stopped using NetworkManager. But dracut does not add systemd-networkd to the initramfs. I spent some time trying to figure out why by adding echo statements to the dracut code, but I'm no closer to understanding why systemd-networkd is not added. What I did do is: $ dracut -f --add systemd-networkd and that makes clevis unlocking work. I'll add a dracut conf file to force this on. I think this is worth raising as a bugzilla and will do that. Barry