Bug#1071592: fails to enable LVM on crypt during boot, rendering the system unbootable

[Luca Boccassi]

Control: reassign -1 dracut 060+5-1

On Tue, 21 May 2024 21:47:37 +0200 Evgeni Golov <evgeni at debian.org>
wrote:
> Package: systemd
> Version: 256~rc2-3
> Severity: important
> 
> Ohai,
> 
> I am filing this against systemd, as that's the package that triggers
> the issue when upgraded, but it very well might be in dracut, so
please
> re-assign as you see fit.
> Also filing this "only" as important, as it's breaking a non-default
> setup and I did not verify this on any other system.
> 
> My laptop is running sid with / on LVM on crypt. I am using dracut
for
> initrd generation.
> 
> With the upgrade to systemd 256 (from 255.5) it fails to boot:
> 1. asks for my passphrase
> 2. systemd-cryptsetup@<cryptdevice>.service starts
> 3. dev-mapper-<vg>-<lv>.device runs forever, never reaching
completion
> 
> I can get it to boot by:
> 1. rd.break=pre-mount in the bootloader to interrupt dracut
> 2. lvm lvchange -ae <vg>/<lv> in the dracut shell
> 
> I am aware of #1071278 but I do have dracut 060+5-8 which is supposed
to
> have all the required fixes.
> 
> Downgrading systemd to 255.5-1 and regenerating the initrd fixes the
> boot process.

It's probably the same issue with missing libraries, but I do not use
either dracut nor LVM so I cannot help, reassigning to dracut so that
you might get some help with debugging and finding out what the actual
issue is

-- 
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-systemd-maintainers/attachments/20240522/226ad877/attachment.sig>