I feel that the “message” during bootup keeps giving users concern over nothing important. It’s quite literally like passing by a store on the road and you read a sign that says “We’re open!”
That’s all it is. It’s just a message. “Your filesystem is fine, nothing to do! Anyways, enjoy your computer!”
You can test this yourself by manually invoking fsck (on an unmounted filesystem or in a live USB session) without any parameters. It will most likely immediately exit and skip any such scan because your filesystem is “clean”. That’s why you need to invoke the -f flag to FORCE it to scan your filesystem. (The bootup process does not do that. Nothing is forced.)
fsck may only be run against an unmounted filesystem. Running it against a mounted filesystem is going to cause damage to said filesystem, unless the filesystem is mounted read-only, but even then I still wouldn’t recommend it.
tty3 won’t have been initialized yet at that point of the boot process. The ttys — i.e. the virtual consoles — are initialized by systemd, which isn’t running yet at that point of the boot process. So the output is sent to /dev/console instead, which is the default Linux console — or boot console, if you will — as built into the kernel.
You know what? Correcting me in front of others in public? Fsck yo-, nevermind.
Anyways, I found a solution. Just remove the dust cover when you think the login screen or desktop is ready. No need to change any settings or defaults. It is highly effective at resolving most bootup concerns.
Well, it would attempt to send the boot-up messages to tty3, but that’s no guarantee that they will arrive there, given that the fsck is being run before tty3 is initialized. And in that case, my might then just as easily point them at /dev/null… where no one hears you scream…
It could be, because those messages are there for a reason. If you redirect all output of the boot process to /dev/null and something goes wrong, you’d never know about it.
I have no way of knowing what you need and what you don’t need, because it all depends on your hardware and how you’ve installed the system. For instance, I myself don’t have Bluetooth, so I’ve disabled that, and I’m also not using lvm2, so I’ve disabled that too. But you in turn may need those things. We don’t know that.
What I will say is that 5.286 seconds is definitely not a bad score, so I don’t see what could possibly still make a difference.
Ctrl+Alt+F3. The shortcut for returning to your GUI environment differs per GUI. In the event of KDE Plasma, it would be Alt+F1, but if you’re running XFCE, then it’ll be Alt+F7. I’m not sure anymore what it is for GNOME these days — Alt+F4 maybe?
Either way, if you want to see those messages, then why redirect them in the first place?