Hi, all --
I am building a Leap 15.2 system and had some filesystem mount issues that caused the system to stick at "enter root password or press Ctrl-D to continue" asking for help. I did get that one (user missing from the passwd file but specified as an NTFS volume content owner) figured out, but it wasn't because I could figure out how to see the errors that went by before the screen cleared and the message & password prompt popped up. I tried looking in /var/log/messages and running dmesg and poking at anything else that I could imagine, but I never did see that mount error.
When I'm in a recovery/maintenance single-user shell after a boot failure, how do I see the boot messages to read back and see what blew up?
TIA & HAND
:-D
On 15/03/2021 02.40, David T-G wrote:
Hi, all --
I am building a Leap 15.2 system and had some filesystem mount issues that caused the system to stick at "enter root password or press Ctrl-D to continue" asking for help. I did get that one (user missing from the passwd file but specified as an NTFS volume content owner) figured out, but it wasn't because I could figure out how to see the errors that went by before the screen cleared and the message & password prompt popped up. I tried looking in /var/log/messages and running dmesg and poking at anything else that I could imagine, but I never did see that mount error.
When I'm in a recovery/maintenance single-user shell after a boot failure, how do I see the boot messages to read back and see what blew up?
Try "journalctl".
Also:
systemctl --failed
to see what failed.
Carlos, et al --
...and then Carlos E. R. said... % % On 15/03/2021 02.40, David T-G wrote: % > ... % > % >When I'm in a recovery/maintenance single-user shell after a boot failure, % >how do I see the boot messages to read back and see what blew up? % % Try "journalctl".
Ahhhhhhh ... OK. Now to remember that ... but it's a good pointer :-)
% % Also: % % systemctl --failed % % to see what failed.
Indeed. Thanks!
HAND
:-D
On 15/03/2021 11.07, David T-G wrote:
Carlos, et al --
...and then Carlos E. R. said... % % On 15/03/2021 02.40, David T-G wrote: % > ... % > % >When I'm in a recovery/maintenance single-user shell after a boot failure, % >how do I see the boot messages to read back and see what blew up? % % Try "journalctl".
Ahhhhhhh ... OK. Now to remember that ... but it's a good pointer :-)
Yes, this is a command you must remember.
% % Also: % % systemctl --failed % % to see what failed.
Indeed. Thanks!
That one I had to look it up ;-)
-
Carlos E. R. -
David T-G