Now, I think is worth mentioning that:
Adding 'x-initrd.attach' to the device holding root at /etc/crypttab,
does in fact solve systemd-cryptsetup@vda5_crypt.service failing. But,
on reboots and shutdowns I still get 'Failed to finalize DM devices,
ignoring'. I wonder if it can be ignored. Using dracut doesn't change
this behavior.
And on my other machine, I get at boot: "cryptsetup: WARNING:
vda5_crypt: ignoring unknown option 'x-initrd.attach.". Even though the
option does work as expected, this I suppose because I'm using
initramfs-tools/busybox this time? I still haven't tried with dracut
since the warning seems a false positive.
El 28/9/22 a las 17:38, ng escribió:
Well, I added that to my crypttab, and everything is fine again on my
side :)
what happens next is up to you, thank you for your help
El 26/9/22 a las 13:16, Michael Biebl escribió:
Am 20.09.22 um 06:47 schrieb ng:
https://github.com/systemd/systemd/issues/24758
Done, I hope I did it right.
Thanks for forwarding this issue upstream.
It turns out, that adding "x-initrd.attach" to /etc/crypttab for the
device holding the root fs does fix the issue.
This is nicely documented in systemd's man crypttab. Unfortunately we
don't install this man page atm due to [1] which appears to go nowhere.
I guess we should do two things:
a/ dpkg-divert the cryptsetup provided man page and install the man
page which we currently remove [2]
b/ clone this bug report and reassign it to d-i/partman so the debian
installer adds the x-initrd.attach option when creating the luks+lvm
setup.
Thoughts?
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981405
[2]
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/rules#L219
