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 $(nproc))
mkfs.ext2 -q ${zRAM__DEV}
.
.
.
mount --type auto ${zRAM__DEV} /new_root/
.
.
.
rsync \
--archive \
--acls \
--exclude boot \
--exclude dev \
--exclude mnt \
--exclude proc \
--exclude run \
--exclude sys \
--exclude tmp \
--exclude lost+found \
--verbose \
--xattrs \
--hard-links \
\
/real_root/ \
/new_root/ \
.
.
.
umount /real_root/
When I remove quiet from the boot parameters and activate the hook the only
addition to the Freezing message is:
*:: running cleanup hook [udev]*
*Welcome to Arch Linux!*
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.
On Mon, 24 Apr 2023 at 11:41, Lennart Poettering <lenn...@poettering.net>
wrote:
> 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.
> > [ 439.264894] systemd[1]: Freezing execution.
> >
> > What does this message mean and what new systemd 253 requirements do I
> > need to satisfy for the load to RAM to work as it did before?
>
> I am not sure "what running Linux from RAM" is precisely supposed to
> mean, but I am pretty sure the above message has little to do with
> amount of memory required. Enable debug output if output is too terse.
>
>
> https://freedesktop.org/wiki/Software/systemd/Debugging/#diagnosingbootproblems
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
