Capture boot verbose to text file?

Chat about Linux in general
Post Reply
User avatar
Lucap
Level 5
Level 5
Posts: 897
Joined: Tue May 24, 2016 1:40 am

Capture boot verbose to text file?

Post by Lucap » Wed Jan 17, 2018 1:49 am

Fsprotect errors are not showing up in Dmesg , Does anyone remember the old command that you could add to grub just after quiet-splash to dump all the boot verbose to text file?

It was something like 2@>text.txt

User avatar
xenopeek
Level 24
Level 24
Posts: 22192
Joined: Wed Jul 06, 2011 3:58 am
Location: The Netherlands

Re: Capture boot verbose to text file?

Post by xenopeek » Wed Jan 17, 2018 12:18 pm

dmesg shows messages from the kernel ring buffer. Once the buffer is filled with messages, the oldest messages start getting overwritten. dmesg is only useful to look at things as they occur, not longer after the fact. I don't know the GRUB feature you're asking about.

Are you using Linux Mint 17.x? In that case you could take a picture with your smartphone or camera of the message? (or a video if the message scrolls by too fast)

For Linux Mint 18 and newer the boot messages are actually kept by the kernel and stored in your system journal once system is booted. So you can just retrieve them with journalctl. Use the command journalctl -k to show the kernel messages from your current boot. That includes all the boot messages (and any kernel messages from after your system booted). If you want to store this to file you do: journalctl -k > logfile.txt
Image

User avatar
Lucap
Level 5
Level 5
Posts: 897
Joined: Tue May 24, 2016 1:40 am

Re: Capture boot verbose to text file?

Post by Lucap » Thu Jan 18, 2018 1:42 am

Cheers for that but it's now solved , thanks :)

All the issues were in regards to apparmor as it doesn't like a double stacked file system so it spat out errors.

Post Reply

Return to “Chat about Linux”