Boot process needs too much time, how do I get more information about this?

How can I make the boot messages visible during the boot process?
Deleting the boot parameter “quite” does nothing, I only see a black screen with the Manjaro logo for about 1 minute until the KDE login appears. This takes much too long, I suspect one or more processes hang during booting.

Is there a way to trace the boot process (perhaps via dmesg or jourmalctl), including the required times?

Remove plymouth and/or splash and quiet from boot options.


That would be the plymouth boot splash.


These are common

systemd-analyze
systemd-analyze blame
systemd-analyze critical-chain
systemd-analyze plot > bootplot.svg

See pretty much all the thing at the archwiki page;

https://wiki.archlinux.org/title/Improving_performance/Boot_process

2 Likes

There is no “quite” boot parameter. That would be “quiet”. They are called kernel parameters.

Also, did you run update-grub as root after changing kernel parameters?

2 Likes

@cscs: Thanks for the detailed answer, I’ll take a closer look at this.

@ben75: “quite” was a typo. For the first times of booting I’ve deleted the parameter directly in grub menu.

Edit: After deleting “splash” and “quiet” I found the error immediately. It was the swap partition with an invalid UUID in fstab. So the timeout of 1:30 had to be waited for.

You can actually edit comments here instead of creating a new comment starting with the word EDIT. Do you see the pencil icon below your comments?

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.