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

[Luca Boccassi]

On Mon, 27 May 2024 22:44:21 +0100 Luca Boccassi <bluca at debian.org>
wrote:
> On Fri, 30 Sep 2022 23:34:46 -0300 ng <ledufff at hotmail.com> wrote:
> > 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 at 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.
> 
> I'll upload a D-I fix that adds x-initrd.attach to crypttab by
default
> shortly. Yes you can ignore the "unknown option" message, as the
> Debian-specific initramfs-tools scripts do not know about it, but
> that's fine, it's for the shutdown path anyway. And the finalize
> messages can also be ignored.

Hi cryptsetup maintainers,

Please consider applying the same change in the initramfs-tools
cryptsetup scripts, so that x-initrd.attach is recognized (and no
warning is printed), and so that it is added if missing. Thanks.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20240527/c21a227e/attachment.sig>