On Wed, 22 May 2024 00:51:22 +0100 Luca Boccassi <bl...@debian.org> wrote:
Control: reassign -1 dracut 060+5-1
On Tue, 21 May 2024 21:47:37 +0200 Evgeni Golov <evg...@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
It seems like the issue is that systemd 256 now makes /usr read-only in the
initrd environment, but dracut depends on writing to /usr.
One workaround is to set ProtectSystem=no in the initrd, so that /usr is
writable again. I got my system (also LVM on LUKS) booting with a dracut
module to write system.conf:
blee@r8 /usr/lib/dracut/modules.d/99local $ cat module-setup.sh
#!/bin/bash
# called by dracut
install() {
printf "[Manager]\nProtectSystem=no\n" >>
"${initdir}/etc/systemd/system.conf"
}
