Extremely slow boot (over 3 minutes)
Solution:Jump to solution
just need to shut down and unplug the usb, if it is something that is also powered, cut the power for it too (for me the issue was my powered usb hub)
41 Replies
i've had issues with plymouth and boot times before so maybe I need to disable it?
https://drive.google.com/file/d/1XFdJ5mjZj1sQPiFNubzzWWH_Zo6qdiHE/view?usp=drive_link
here is a plot of the boot processes according to
systemd-analyze plot > plot.svg
seems like its taking a really long time to mount my disks for some reason
Just realized the way I shared it in Google drive you can't really see the SVG without downloading it and then opening it in a browser š
Need to find a better way to share an SVG...
but basicly its taking 2 plus minutes on disks for some reason even though there healthy nvme drives (just ran SMART)
also
achtually the top hold up seems to be the built in TPM but don't see how that could be I don't have any disk encryption :ThonkFedora:
no idea about this, i am not affected and i have like 11 drives in my system
are any mechanical?
I have one but its seems the ones its getting stuck on are nvme
3 ssds, rest mechanical, some in raid 1
if your system is installed on a mechanical drive though then slow boot times on any atomic system is to be expected, ostree is not friendly with mechanical drives
no its installed on to a nvme
WD_BLACK_SN770_1TB
oh i think im looking at it wrong
the
time on the left of each item is how much time passed since loading UEFI
so when it says
that means
it got stuck on
dracut-initqueue.service
for about one minute since running systemd-rfkill.serviceit being stuck on dracut though might be related to rebuilding initramfs maybe?
so it looks like where its stuck the longest is on dracut
yeah
do you have initramfs regeneration enabled
its only needed for vfio here i think
then it takes an additonal 6 sec to mount all my drives which i guess is fine
rpm-ostree statusnot sure how do I check
if that mentions
Initramfs: regenerate then its enabledi do have virt manger...
yup
do you do vfio/gpu passthrough?
it says regenerate
no
rpm-ostree initramfs --disable
then see if that helpsthough i think i did set it up when I ran the ujust...
but I don't use it
yeah it sets it up if you enable vfio drivers
ujust setup-virtualization vfio-off first then
just in case
then run rpm-ostree initramfs --disablehmm nope still getting stuck on dracut it seems
i have no idea then why its struggling there
try see if there is anything in
systemctl status dracut-initqueue
other than that i got nothing atmhmm this seems to be why
what that means though i have no idea š
hmm
this is a long shot but can you try shutting off, unplug all usbs then boot up again
maybe it hangs on some usb device since it times out on udev rules
i think it may be usb devices. I see alot of usb errors in my dmesg.
chatgpt said to check that lol
i had that happen with a usb hub long ago where the usb hub was in a weird state which slowed down the boot and this reminded me of that
do what i said then
full shut down
unplug every usb
boot then plug everything back again
easier than trying 1 by 1
and if it happens again you know what it is then (has not happened for over half a year for me though)
yeah
fwiw
this is what I see in my dmesg
yep
thats the same error i have when it happened
Solution
just need to shut down and unplug the usb, if it is something that is also powered, cut the power for it too (for me the issue was my powered usb hub)
so if you have anything similar its worth unplugging them from the pc and power then boot up again
Holy it was that. Literally booted in seconds now
i do have a powered usb hub so could be that...
anyway that imporved boot times by a lot
though it seems I can further shave off about 20 sec by disabling cec
don't think I need it as I don't have the hardware for it anyway (i don't think the 6700xt has HDMI cec)
Hmmm plugging back in the USB devices causes a slow boot again after rebooting
Do I need to keep it unplugged for it to boot?
Maybe one of my USB devices is going bad....
no gpu has cec support, requires usb hardware with cec
unplug the power for the usb hub
it might need a power reset
anyways im off, try to remove power from the usb hub, if it happens again maybe unplug the usb hub from power when you go to bed so the caps in it drain, i believe thats what i did and havent had the issue since.
Well left everything unplugged (PC and hub) for about an hour no luck so I guess my hub is going faulty now
2nd USB hub I had die on me this year :goodgrief:
was the hub unplugged from power entierly
yup i have everyting on a ups and i unpluged the ups and turned it off so it wouldn't run on battery
and then I also unpluged the power cable of the hub (anyway its a real small battery would of only lasted about 10 minutes)
maybe i should stop buying cheap no name usb hubs on amazon :clueless:
caps depending on their size can keep a charge for up to a month
the ones in a usb hub maybe overnight
try unplug the power and usb for it before going to bed, if that doesnt work then it might be the hub itself (or one of the things plugged into the hub)
yeah ill try again before going to bed but I tried draining any power from the hub by connecting a phone
and turning each port on and off
that from my understanding should of killed any remainning power
its just the last resort before deciding the hub is being iffy
anyways i am off to try sleep now
night thanks for the advice though! I would of still been stuck on troubleshooting my disks lol
wow leaving it overnight def did the trick
still loasing about 20 seconds because of
systemd-rfkill.service
yep caps needed to drain, glad it works though
about 1-1.2 min boot is normal though
mine boots in 1.2 mins
yeah not worth chasing the extra potentinal 20 seconds. if i really wanted to I could maybe get it down to about 40s by using EFISTUB instead of refind but I will lose dualboot support