Arch Linux

avi9526

Member

Registered: 2015-05-15

Posts: 126

System randomly not booted

My system randomly not booted, last message in journalctl is
"Reached target Local Encrypted Volumes."
until 20 sec passed and i have pressed Ctrl+Alt+Del and it rebooted

direct comparison with prev. boot

journalctl -o cat -b -1 | grep -B10000000 'Reached target Block Device Preparation for /dev/mapper/hdd.' | sort > 1
journalctl -o cat -b -2 | grep -B10000000 'Reached target Block Device Preparation for /dev/mapper/hdd.' | sort > 2

the line

Reached target Block Device Preparation for /dev/mapper/hdd.

is common message after which there is only

Reached target Local Encrypted Volumes.
Reached target System Initialization.

for proper boot

or

Reached target Local Encrypted Volumes.
Received SIGINT.

for stuck boot and Ctrl+Alt+Del

So

diff 1 2 > 12

gives only few lines that are not some numbers (memory, time, etc) changed

…
> Finished Tell Plymouth To Write Out Runtime Data.
…

this system booted properly around 6 times after last major change that was update + extra kernel command line arguments "console=ttyS0,115200 console=ttyUSB0,115200 console=tty0" that broke plymouth

For a moment I thought that it was fstrim.timer that triggered freeze-like state, but it was not planed for next few days.

Does anyone has any clues where to dig it?

jonno2002

Member

Registered: 2016-11-21

Posts: 887

Re: System randomly not booted

systemctl cat sysinit.target
# /usr/lib/systemd/system/sysinit.target
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=System Initialization
Documentation=man:systemd.special(7)

Wants=local-fs.target swap.target
After=local-fs.target swap.target
Conflicts=emergency.service emergency.target
Before=emergency.service emergency.target

wait longer for the timeout period and see what happens, 20secs isnt long enough

try removing/commenting out all unnecessary entries from your fstab and see if it boots