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.
So my next question is under what circumstances does systemd issue this
message?
On Tue., Apr. 25, 2023, 9:18 a.m. Caeri Tech, 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
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
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
To *run Linux from RAM *I have a hook that copies the contents of the root
device to a zram device. Here is a snip from the hook:
mkdir /real_root/
mount ${root} /real_root/
modprobe zram
zRAM__DEV=$(zramctl -f -fs $(free -m | awk '/Mem/ {print
int($2*2)"M"}') -a lzo -t
On Fr, 21.04.23 18:36, Caeri Tech (caerit...@gmail.com) wrote:
> I've been running Linux from RAM for a couple years without issue.
> However, since the upgrade from 252 to 253 the load to RAM fails and the
> computer hangs with the message below:
>
> [!!] Failed to start up manager.
> [
