Hello all. I’m running Fedora 39 (beta) and so far satisfied. However, the system starts rather slowly. Maybe you can help me ?
Startup finished in 9.893s (firmware) + 5.534s (loader) + 3.971s (kernel) + 9.424s (initrd) + 28.710s (userspace) = 57.534s
graphical.target reached after 28.687s in userspace.
systemd-analyze critical-chain
The time when unit became active or started is printed after the “@” character.
The time the unit took to start is printed after the “+” character.
graphical.target ad28.687s
└─logid.service ad28.687s
└─multi-user.target ad28.671s
└─plymouth-quit-wait.service ad8.147s +20.504s
└─systemd-user-sessions.service ad8.106s +22ms
└─remote-fs.target ad8.090s
└─remote-fs-pre.target ad8.090s
└─nfs-client.target ad8.090s
└─gssproxy.service ad8.063s +26ms
└─network.target ad8.037s
└─wpa_supplicant.service ad8.029s +7ms
└─basic.target ad5.915s
└─dbus-broker.service ad5.831s +71ms
└─dbus.socket ad5.793s
└─sysinit.target ad5.768s
└─systemd-resolved.service ad4.311s +1.340s
└─systemd-tmpfiles-setup.service ad3.300s +709ms
└─import-state.service ad3.100s +155ms
└─local-fs.target ad3.079s
└─run-user-1000-doc.mount ad13.034s
└─run-user-1000.mount ad8.289s
└─local-fs-pre.target ad2.130s
└─systemd-tmpfiles-setup-dev.service ad1.999s +103ms
└─systemd-tmpfiles-setup-dev-early.service ad1.677s +304ms
└─kmod-static-nodes.service ad1.282s +140ms
└─systemd-journald.socket
└─system.slice
└─-.slice
ad=@ 
https://img.adminforge.de/gallery#4H5LBZWD/9qhm0ZUi.svg
I think you can use the <> pre formatted text to allow the original output to be posted without edit8ng iut the @.
OK, i try
What are the specs of your computer? In particular, what kind of disk do you have?
Does it actually take 57 seconds from pressing the power button to the login screen?
Are you using automatic login?
You can edit your exsting post to replace the text with the orginal format that has @ symbols and use proper formatting.
The slow start could be a symptom of a failing storage device. At my work, before SSD’s were common, most users were issued name-brand laptops that would become sluggish at end-of-warranty plus a few days, due to drives making multiple read attempts on some blocks. IT bought new disks by the carton to replace the hard disks. Fortunately prompt replacement meant very little data were lost, but the cost in lost time to users and IT staff was significant.
You can use the Gnome DIsks utility to check the status of your storage device(s).