You are not logged in.
Dear all,
I finally managed to install Archilinux in a Virtualbox Virtual Machine.
Everything seems fine and the OS boots correctly, but when the system is loading I can see that one of the checks performed at boot
returns a FAILED message. The problem is that it is so fast I can't read it.
I also notice a Yellow message but, again I can't read what it is about.
I know it might sound a silly question, but is there a way to se a log of these checks?
Thanks a lot in advance for the help!
Cheers,
Luca
TLDR: all the solutions proposed below are valid (and well worth reading the links for learning purpose). If you just want the list of the failed actions, you can get it with the command
sudo journalctl -b | grep -i failed
Last edited by lucacerone (2014-01-25 11:18:39)
Offline
Temporarily disable clearing these messages, automatic logging in etc. Extend you scrollback buffer if needed and use Shift+PgUp to view these messages.
Offline
Also, look at the output of dmesg and of journalctl
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Hi karol and ewaller, thanks for the help
Though I have no idea of how I can do the stuff in karol's reply
Offline
Offline
Though I have no idea of how I can do the stuff in karol's reply
You can start by reading https://wiki.archlinux.org/index.php/Scrollback_buffer
However, heed Karol's warning by reading https://wiki.archlinux.org/index.php/Di … t_Messages
Good luck!
edit: Oh, darn. Karol beat me to it lol
Last edited by frank604 (2014-01-19 00:44:36)
Offline
Thanks guys
Offline
If it worked, please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
Offline
Thanks a lot everybody. In the end I chose to simply use journalctrl -b | grep -i failed > boot.fails.log to inspect these errors more posts arriving to fix the issues.
Offline
I think it's important to run this command as root or with sudo.
Offline
Ah I didn't know because I did all of this as root (I still haven't setup sudo on my laptop.. I am using Arch to improve my Linux skills, but haven't had too much time to play with it )
Thanks for the clarification!
Offline
Thanks a lot everybody. In the end I chose to simply use journalctrl -b | grep -i failed > boot.fails.log to inspect these errors more posts arriving to fix the issues.
The command should be 'journalctl', like you say in your first post, there's no 'r' :-)
$ journalctl -b | wc -l
13
$ sudo journalctl -b | wc -l
433
As you can see, with sudo you get much more info, although grepping may sometimes return the same results, with or without sudo.
Offline