systemd boot-up another daft question

[Chris Murphy]

On Jan 16, 2014, at 3:50 PM, Frank Murphy <frankly3d at gmail.com> wrote:

> On Thu, 16 Jan 2014 15:47:54 -0500
> Matthew Miller <mattdm at fedoraproject.org> wrote:
> 
>> Sorry, coming to this late, but did you try booting with 
>> 
>> systemd.log_level=debug
>> 
> 
> No, 
> 
> Would that have helped at the time read what was on the screen?


systemd debug is rather verbose. First remove 'rhgb quiet' from the linux line, found in the grub menu. Highlight the entry you want to boot, hit e to edit, and then scroll down to find the linux line. This won't pause. If you're having a problem seeing the error message, and  it happens early enough that /sysroot hasn't yet mounted rw, then you can add rd.break to boot parameters and that will drop you to a dracut shell where you can look at the journal for failures, something like:

journalctl -xb | grep -i fail

Or just journalctl -b and scroll through until you find the problem. The journal is started right away, but isn't persistent until /sysroot is mounted rw, so this is a way to get access to early messages and troubleshooting if you can't ssh in or read the journal once you get a login prompt.


Chris Murphy