4 ms·
> If that happens again I'd try opening a virtual terminal, login as root and check logs. If the system has unmounted all the drives, there won't be any logs.
by Twirrim 5y ago
> If that happens again I'd try opening a virtual terminal, login as root and check logs.
If the system has unmounted all the drives, there won't be any logs. This happens often enough with systemd / journald to be a big source of annoyance.
The only option you get is to tell systemd to boot in debug mode but that fundamentally alters the timing and behaviour of so much that it often stops the weird behaviour from ever happening (similar fun can be had with `dracut` where enabling debug tends to stop any race condition from ever happening)
- AshamedCaptain 5y agoNote systemd does dump its own log to the kernel ring buffer until journald starts (the last message I see on the kernel ring buffer is Started Journal Service). It's no help though when (as in my case) journald starts but then has /var unmounted below its feet. I can write a script that keeps /var busy though, preventing it from being unmounted.
- tremon 5y ago> I can write a script There's some delicious irony in having to write a shell script to combat the init system that was designed to replace all the shell scripts.