I just installed Fedora 38 and have been noticing that it takes a longer than usual to get to the login screen (around 2 minutes).
Why is this and how to I speed it up?
I’m running this on an older laptop with ok specs I think but I’ve tried other Operating Systems that I think were more demanding and they were faster to finish the boot up.
FWIW, it looks similar to this report. They appear to be saying that the larger number of activated devices is expected and the times are not cumulative since the services are started in parallel. Still, 30 seconds seems excessive. My (slow) PC shows that service taking 10 seconds.
Thank you for linking that report. Upon further reading, I think this might be related to my bios trying a bunch of different drives (boot order?) instead of the main ssd ?
Though, I do have it set up for the drive that fedora 38 is on to boot first…
Then it might be the way I installed fedora (see pic below);
The partitioning looks fine to me. I don’t believe that would cause things to run slowly even if it were incorrect. That is something that either works or it does not.
There are (many) other possibilities. Since you appear to have an ATA disk drive, maybe this one?
Nevermind, I read the wrong line from your last post. I see you said it is an SSD. In that case, maybe it is this “discard storm” problem that has been mentioned recently?
The script appears to be calling snap list --all to list all the installed snaps and feeding that list to a filter (awk ‘/disabled/{print $1, $3}’) then those filtered results to a loop (while read snapname revision). The loop then removes whatever snaps were supplied to it one-by-one with snap remove “$snapname” --revision=“$revision”. The script, as you’ve copied it here, appears to be a bit corrupted. There should be a semicolon (;) before done.
That is 3 separate commands which is why in your post above they were given to you on 3 lines. sudo set -eu snap refresh LANG=C snap list --all | awk ‘/disabled/{print $1, $3}’ | while read snapname revision; do sudo snap remove “$snapname” --revision=“$revision” ;done
systemd-analyze blame doesn’t tell much on its own. It shows startup times of units, but most of them should be running in parallel. The manual explains this in more detail.
You can generate a graph that shows the actual order and timing of units. Do a cold boot first (completely shut down, then boot the computer), then run this command:
systemd-analyze plot | tee plot.svg | fpaste
This will save the plot to a file plot.svg (which you can open in your image viewer or browser) and also upload it to the Fedora pastebin. Reply with the URL given.
The ~30s for initrd phase seems abnormal, I usually see it around 3s to 15s (and that includes other reports of slow boots). In particular the dracut-initqueue.service stands out to me.
Can you upload the journal as well? Hopefully there’s a clue in there.
journalctl -b | fpaste
Is the SSD shown in your earlier screenshot the only disk on this computer?
Any USB devices connected at boot other than mouse/keyboard? Could you try disconnecting them and see if it affects the boot time?