4 ms·
Deactivate graphical boot screens (often just by pressing Esc), increase the log level[0] and try to read the logs somehow. Maybe you can still log in as root.
by corty 5y ago
Deactivate graphical boot screens (often just by pressing Esc), increase the log level[0] and try to read the logs somehow. Maybe you can still log in as root. If you cannot log in as root even, but networking works, configure rsyslog to send your logs to another host and read them there.
[0] https://freedesktop.org/wiki/Software/systemd/Debugging/ https://freedesktop.org/wiki/Software/systemd/Debugging/
- jraph 5y agoif you can't login as root, you can try to put bash as init (with init=/bin/bash in the kernel boot command line) to inspect the system. Might be difficult on some systems (with SELinux?)
- megous 5y agoif you have access to kernel command line to add init= you can also disable selinux there.
- corty 5y agoI'd rather recommend booting a liveCD. grml, knoppix, whatever floats your boat. An init=/bin/bash shell needs quite a bit of knowledge to get working (mount rw, get rid of selinux, mount the real rootfs), is possibly just busybox and generally a pain. Even more so if you need the net to copy something over. It isn't impossible, and OK in a pinch, but why make it hard on yourself?
- isodude 5y agoYou can actually specify systemd.unit=rescue.target nowadays. https://ostechnix.com/how-to-boot-into-rescue-mode-or-emergency-mode-in-ubuntu-18-04/ https://ostechnix.com/how-to-boot-into-rescue-mode-or-emerge...
- megous 5y agoYou forgot mounting /proc and /sys :) Anyway, it's the quickest way to recover if all you need is to edit some config file or run passwd.