UB
Universal Blueā€¢2w ago
zany130

Extremely slow boot (over 3 minutes)

Any ideas for imroving boot times? 
systemd-analyze
Startup finished in 9.079s (firmware) + 31.540s (loader) + 4.249s (kernel) + 2min 5.425s (initrd) + 32.153s (userspace) = 3min 22.449s 
graphical.target reached after 32.090s in userspace.
systemd-analyze
Startup finished in 9.079s (firmware) + 31.540s (loader) + 4.249s (kernel) + 2min 5.425s (initrd) + 32.153s (userspace) = 3min 22.449s 
graphical.target reached after 32.090s in userspace.
https://paste.centos.org/view/346501c8
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)
Jump to solution
41 Replies
zany130
zany130ā€¢2w ago
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...
zany130
zany130ā€¢2w ago
zany130
zany130ā€¢2w ago
but basicly its taking 2 plus minutes on disks for some reason even though there healthy nvme drives (just ran SMART) 
Startup finished in 9.118s (firmware) + 31.744s (loader) + 4.250s (kernel) + 2min 5.440s (initrd) + 33.361s (userspace) = 3min 23.914s 
graphical.target reached after 25.068s in userspace.

2min 6.709s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
2min 6.709s dev-tpm0.device
2min 6.638s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J\x2dpart2.device
2min 6.638s dev-disk-by\x2duuid-D6FCB12FFCB10AAF.device
2min 6.638s dev-nvme1n1p2.device
2min 6.638s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
2min 6.638s dev-disk-by\x2ddiskseq-3\x2dpart2.device
2min 6.638s dev-disk-by\x2did-nvme\x2deui.002538d91148b62e\x2dpart2.device
2min 6.638s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J_1\x2dpart2.device
2min 6.638s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
2min 6.638s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart2.device
2min 6.638s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.2-0000:03:04.0-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
2min 6.633s sys-module-fuse.device
2min 6.600s dev-ttyS1.device
2min 6.600s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
2min 6.577s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart4.device
2min 6.577s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J\x2dpart4.device
2min 6.577s dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
2min 6.577s dev-nvme1n1p4.device
2min 6.577s dev-disk-by\x2did-nvme\x2deui.002538d91148b62e\x2dpart4.device
2min 6.577s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J_1\x2dpart4.device
2min 6.577s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.2-0000:03:04.0-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p4.device
2min 6.577s dev-disk-by\x2dlabel-GAMES.device
2min 6.577s dev-disk-by\x2ddiskseq-3\x2dpart4.device
2min 6.577s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
Startup finished in 9.118s (firmware) + 31.744s (loader) + 4.250s (kernel) + 2min 5.440s (initrd) + 33.361s (userspace) = 3min 23.914s 
graphical.target reached after 25.068s in userspace.

2min 6.709s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
2min 6.709s dev-tpm0.device
2min 6.638s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J\x2dpart2.device
2min 6.638s dev-disk-by\x2duuid-D6FCB12FFCB10AAF.device
2min 6.638s dev-nvme1n1p2.device
2min 6.638s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
2min 6.638s dev-disk-by\x2ddiskseq-3\x2dpart2.device
2min 6.638s dev-disk-by\x2did-nvme\x2deui.002538d91148b62e\x2dpart2.device
2min 6.638s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J_1\x2dpart2.device
2min 6.638s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
2min 6.638s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart2.device
2min 6.638s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.2-0000:03:04.0-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
2min 6.633s sys-module-fuse.device
2min 6.600s dev-ttyS1.device
2min 6.600s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
2min 6.577s dev-disk-by\x2dpath-pci\x2d0000:0c:00.0\x2dnvme\x2d1\x2dpart4.device
2min 6.577s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J\x2dpart4.device
2min 6.577s dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
2min 6.577s dev-nvme1n1p4.device
2min 6.577s dev-disk-by\x2did-nvme\x2deui.002538d91148b62e\x2dpart4.device
2min 6.577s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S64ANJ0R930800J_1\x2dpart4.device
2min 6.577s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.2-0000:03:04.0-0000:0c:00.0-nvme-nvme1-nvme1n1-nvme1n1p4.device
2min 6.577s dev-disk-by\x2dlabel-GAMES.device
2min 6.577s dev-disk-by\x2ddiskseq-3\x2dpart4.device
2min 6.577s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
also 
  2min 78ms dracut-initqueue.service
    29.700s systemd-rfkill.service
    20.587s cec-onboot.service
  2min 78ms dracut-initqueue.service
    29.700s systemd-rfkill.service
    20.587s cec-onboot.service
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:
HikariKnight
HikariKnightā€¢2w ago
no idea about this, i am not affected and i have like 11 drives in my system 
Startup finished in 36.492s (firmware) + 10.559s (loader) + 5.193s (kernel) + 9.644s (initrd) + 17.259s (userspace) = 1min 19.149s 
graphical.target reached after 17.223s in userspace.
Startup finished in 36.492s (firmware) + 10.559s (loader) + 5.193s (kernel) + 9.644s (initrd) + 17.259s (userspace) = 1min 19.149s 
graphical.target reached after 17.223s in userspace.
zany130
zany130ā€¢2w ago
are any mechanical? I have one but its seems the ones its getting stuck on are nvme
HikariKnight
HikariKnightā€¢2w ago
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
zany130
zany130ā€¢2w ago
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 
2min 6.436s dev-disk-by\x2did-ata\x2dST4000VN006\x2d3CW104_ZW625J75.device
2min 6.436s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda.device
2min 6.436s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d6.0.device
2min 6.436s dev-sda.device
2min 6.436s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d6.device
2min 6.436s dev-disk-by\x2did-wwn\x2d0x5000c500e85f53cb.device
2min 6.436s dev-disk-by\x2ddiskseq-1.device
  2min 78ms dracut-initqueue.service
    29.700s systemd-rfkill.service
2min 6.436s dev-disk-by\x2did-ata\x2dST4000VN006\x2d3CW104_ZW625J75.device
2min 6.436s sys-devices-pci0000:00-0000:00:01.3-0000:02:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda.device
2min 6.436s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d6.0.device
2min 6.436s dev-sda.device
2min 6.436s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d6.device
2min 6.436s dev-disk-by\x2did-wwn\x2d0x5000c500e85f53cb.device
2min 6.436s dev-disk-by\x2ddiskseq-1.device
  2min 78ms dracut-initqueue.service
    29.700s systemd-rfkill.service
that means it got stuck on dracut-initqueue.service for about one minute since running systemd-rfkill.service
HikariKnight
HikariKnightā€¢2w ago
it being stuck on dracut though might be related to rebuilding initramfs maybe?
zany130
zany130ā€¢2w ago
so it looks like where its stuck the longest is on dracut yeah
HikariKnight
HikariKnightā€¢2w ago
do you have initramfs regeneration enabled its only needed for vfio here i think
zany130
zany130ā€¢2w ago
then it takes an additonal 6 sec to mount all my drives which i guess is fine
HikariKnight
HikariKnightā€¢2w ago
rpm-ostree status
zany130
zany130ā€¢2w ago
not sure how do I check
HikariKnight
HikariKnightā€¢2w ago
if that mentions Initramfs: regenerate then its enabled
zany130
zany130ā€¢2w ago
i do have virt manger... 
rpm-ostree status                                                                                                                                                                                                                                      ā”€ā•Æ
State: idle
Deployments:
ā— ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:b8fe1ed400759df5655cc93dd1af61c4a3ca62a4377269e6b2bae4f6094666f7
                  Version: 40.20240907.0 (2024-09-08T20:18:29Z)
          LayeredPackages: applet-window-buttons coolercontrol edk2-ovmf kvantum liquidctl qemu sunshine virt-manager
            LocalPackages: lact-0.5.5-0.x86_64 rEFInd_GUI-1.4.2-1.fc39.x86_64
                Initramfs: regenerate

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:3b2db0c90cbce46515defce9eab4a1cc34f306d2ad7ffe715e077f770f187385
                  Version: 40.20240901.1 (2024-09-02T21:14:31Z)
          LayeredPackages: applet-window-buttons coolercontrol edk2-ovmf kvantum liquidctl qemu sunshine virt-manager
            LocalPackages: lact-0.5.5-0.x86_64 rEFInd_GUI-1.4.2-1.fc39.x86_64
                Initramfs: regenerate
rpm-ostree status                                                                                                                                                                                                                                      ā”€ā•Æ
State: idle
Deployments:
ā— ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:b8fe1ed400759df5655cc93dd1af61c4a3ca62a4377269e6b2bae4f6094666f7
                  Version: 40.20240907.0 (2024-09-08T20:18:29Z)
          LayeredPackages: applet-window-buttons coolercontrol edk2-ovmf kvantum liquidctl qemu sunshine virt-manager
            LocalPackages: lact-0.5.5-0.x86_64 rEFInd_GUI-1.4.2-1.fc39.x86_64
                Initramfs: regenerate

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:3b2db0c90cbce46515defce9eab4a1cc34f306d2ad7ffe715e077f770f187385
                  Version: 40.20240901.1 (2024-09-02T21:14:31Z)
          LayeredPackages: applet-window-buttons coolercontrol edk2-ovmf kvantum liquidctl qemu sunshine virt-manager
            LocalPackages: lact-0.5.5-0.x86_64 rEFInd_GUI-1.4.2-1.fc39.x86_64
                Initramfs: regenerate
yup
Want results from more Discord servers?
Add your server