Ask Your Question

Error messages at boot and at shutdown

asked 2016-11-30 17:15:14 -0500

rjltrevisan gravatar image

updated 2016-12-02 10:19:06 -0500


I've just freshly installed Fedora 25 on a ASUS laptop that previously was running Ubuntu. Then I updated it. When I boot I can notice very quicly some error messages in text. It looks like something related to the kernel. And when I shutdown I also get some quick error messages. I can identify something about some modules.

Now is there a log I could access to read properly these error messages? And what could they be what could be the solution?


I formated the pc and reinstalled everything, updated and I get almost the same errors. This time when the pc is shutting down, a long line repeats itself nonstop until the pc reboots. At boot now I can see that it tells me to check systemctl for some modules...

edit retag flag offensive close merge delete


I think that Fedora still provides /var/log/boot.log which gives you a record of what happened during the most recent boot, and it's world-readable. Try using grep FAILED /var/log/boot.log in a terminal and it will tell you what steps in the boot process aren't working. Or, if the errors are too early for that, sudo dmesg | grep -i fail may help.

sideburns gravatar imagesideburns ( 2016-11-30 20:57:05 -0500 )edit

With the command sudo dmesg | grep -i fail i get:

[ 1.716169] audit: type=1130 audit(1480587336.242:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

rjltrevisan gravatar imagerjltrevisan ( 2016-12-01 04:30:55 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2016-11-30 21:09:50 -0500

florian gravatar image

Often, these messages are just warnings or maybe error messages from the kernel. So, dmesg would be the right tool to examine those.

Then, there is journalctl, a component that displays a massive journal of systemd. There you have all kind of system log. For example, run sudo journalctl -b -1 to get all message of the second-to-last boot. And so on.

The internet has plenty of information on both dmesg and journalctl

edit flag offensive delete link more


For usage examples of journalctl, this one may be helpful:

florian gravatar imageflorian ( 2016-11-30 21:12:45 -0500 )edit

After the command on the same line add a pipe to grep as | grep failure

Your list willbe manageable. For the failures reported. Run. sudo system disable "item that failed"

lsatenstein gravatar imagelsatenstein ( 2016-12-03 17:22:05 -0500 )edit

Question Tools

1 follower


Asked: 2016-11-30 17:15:14 -0500

Seen: 3,227 times

Last updated: Dec 02 '16