Thanks Adrian that seems to be it. I hacked my hook (Wow! What a phrase.) to create /tmp on the zram device and the boot completes.
However, I now briefly see several "Failed to start MD array monitor" messages. So far that doesn't seem to affect anything. On Sun., Apr. 30, 2023, 11:37 a.m. Adrian Vovk, <adrianv...@gmail.com> wrote: > Without the debug logs this is just a blind guess, but could it possibly > be this issue: https://github.com/systemd/systemd/issues/27436? > > Best, > Adrian > > On Sat, Apr 29, 2023, 19:20 Caeri Tech <caerit...@gmail.com> wrote: > >> So my next question is under what circumstances does systemd issue this >> message? >> >> On Tue., Apr. 25, 2023, 9:18 a.m. Caeri Tech, <caerit...@gmail.com> >> wrote: >> >>> Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it >>> works as before. >>> >>> Is there perhaps a dependency that I'm now required to include in the >>> initramfs config? >>> >>> On Tue., Apr. 25, 2023, 4:54 a.m. Lennart Poettering, < >>> lenn...@poettering.net> wrote: >>> >>>> On Di, 25.04.23 01:43, Caeri Tech (caerit...@gmail.com) wrote: >>>> >>>> > *:: running cleanup hook [udev]* >>>> >>>> This ouput doesn't look as if systemd was actually involved? >>>> >>>> > But it still freezes execution. >>>> > >>>> > The rescue and emergency shells do not start if I activate the hook >>>> and >>>> > again it freezes. The shells do start, however, when the hook is >>>> not >>>> > activated. >>>> >>>> Anyway, without debug logs as suggested in my earlier mail this is >>>> really hard to debug. Enable debug logging. >>>> >>>> Lennart >>>> >>>> -- >>>> Lennart Poettering, Berlin >>>> >>>
