Bug#1017542: systemd-cryptsetup at vda5_crypt.service: Control process exited, code=exited, status=1/FAILURE

[Michael Biebl]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220926/fce6626d/attachment.sig>