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
Capture boot verbose to text file?
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Capture boot verbose to text file?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Capture boot verbose to text file?
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
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
Re: Capture boot verbose to text file?
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.
All the issues were in regards to apparmor as it doesn't like a double stacked file system so it spat out errors.