On Thu, 16 Jan 2014 18:14:48 -0700 Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > systemd debug is rather verbose. First remove 'rhgb quiet' from the > linux line, Never liked a graphical both have been removed for many releases. //* Daft, I like looking at the text going up. */ 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, I put single in after "ro" cleared the rest of the line. > then you can add rd.break to boot parameters This replaces single I guess. 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 Unfortunately I hit hard reboot. and no rsyslog active to fall back on. > > 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 Appreciate that. ___ Regards, Frank www.frankly3d.com -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
