[SOLVED] Chromebook stuck in systemd

[stronnag]

I rebooted my Chromebook today, and systemd is stuck in
systemd-journald : Failed to forward syslog message: Connect refused.

This is after a load of updates today. I had installed Arch to the internal device using the methods posted here some time ago.

Any clues on how to recover greatly appreciated.

[WarheadsSE]

Immediately, make a USB or SD card, so you can boot that and diagnose the issue more thoroughly. This should be doable from any linux system.

Secondly, it might be a good idea to check the ro/rw/debug options being passed to the kernel, and adjust accordingly.

[stronnag]

Thanks for the debug clue; it was the well publicised systemd abuse of kernel debug that caused the hang. For me, the hard part was evincing the correct u-boot commands to boot the SD backup. The older threads such as http://archlinuxarm.org/forum/viewtopic.php?f=27&t=4016&start=80 are a real treasure.

-jh

[WarheadsSE]

If you have both a local installation and a USB/SD installation, ctrl-u will boot to the external, and ctrl-d will boot to the internal

[WarheadsSE]

This thread is a little more direct: viewtopic.php?f=47&t=6971