On Wed, May 22, 2024 at 05:58:50PM +0200, Evgeni Golov wrote:
> On Tue, May 21, 2024 at 10:10:02PM -0700, Benjamin Lee wrote:
> > > 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
>
> I am rather sure it's not the libraries, as I have dracut -8.
> >
> > 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"
> > }
>
> Thanks! That worked, even if it looks like a gross hack. :)
>
> In the meantime, I have found [1] over at Fedora, which I am going to
> try next (as it is supposed to fix the same thing, but cleaner).
It does fix the issue!
I've opened an MR against the dracut package [2] and uploaded built
packages at [3] if anyone wants to try :)
Thanks for hinting me in the right direction!
Evgeni
[2] https://salsa.debian.org/debian/dracut/-/merge_requests/36
[3] https://people.debian.org/~evgeni/dracut-systemd-ro-usr/
