Slow boot Fedora 39

Hello, I am experiencing a slow boot speed on my laptop running Fedora. I have provided the specifications of my laptop, the version of Fedora, the boot time, and the running services at the time of boot.

[behrooz@fedora ~]$ systemd-analyze
Startup finished in 2.350s (firmware) + 3.457s (loader) + 1.814s (kernel) + 4.597s (initrd) + 11.923s (userspace) = 24.143s 
graphical.target reached after 11.887s in userspace.
[behrooz@fedora ~]$ systemd-analyze blame
5.842s sys-module-fuse.device
5.812s dev-ttyS4.device
5.812s sys-devices-platform-serial8250-tty-ttyS4.device
5.800s sys-devices-platform-serial8250-tty-ttyS19.device
5.800s dev-ttyS19.device
5.793s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1.device
5.793s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1.0.device
5.793s dev-sda.device
5.793s dev-disk-by\x2ddiskseq-1.device
5.793s sys-devices-pci0000:00-0000:00:17.0-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
5.793s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_90LCPY35T.device
5.793s dev-disk-by\x2did-wwn\x2d0x5000039a4270b76a.device
5.784s dev-ttyS23.device
5.784s sys-devices-platform-serial8250-tty-ttyS23.device
5.769s dev-ttyS25.device
5.769s sys-devices-platform-serial8250-tty-ttyS25.device
5.769s dev-ttyS22.device
5.769s sys-devices-platform-serial8250-tty-ttyS22.device
5.746s sys-devices-platform-serial8250-tty-ttyS3.device
5.746s dev-ttyS3.device
5.746s dev-ttyS6.device
5.746s sys-devices-platform-serial8250-tty-ttyS6.device
5.745s sys-devices-platform-serial8250-tty-ttyS18.device
5.745s dev-ttyS18.device
5.735s dev-ttyS7.device
5.735s sys-devices-platform-serial8250-tty-ttyS7.device
5.735s sys-devices-platform-serial8250-tty-ttyS8.device
5.735s dev-ttyS8.device
5.730s dev-ttyS10.device
5.730s sys-devices-platform-serial8250-tty-ttyS10.device
5.730s dev-ttyS15.device
5.730s sys-devices-platform-serial8250-tty-ttyS15.device
5.728s dev-ttyS17.device
5.728s sys-devices-platform-serial8250-tty-ttyS17.device
5.719s dev-ttyS31.device
5.719s sys-devices-platform-serial8250-tty-ttyS31.device
5.718s dev-ttyS29.device
5.718s sys-devices-platform-serial8250-tty-ttyS29.device
5.716s sys-devices-platform-serial8250-tty-ttyS2.device
5.716s dev-ttyS2.device
5.716s dev-ttyS1.device
5.716s sys-devices-platform-serial8250-tty-ttyS1.device
5.715s dev-ttyS0.device
5.715s sys-devices-platform-serial8250-tty-ttyS0.device
5.715s dev-ttyS12.device
5.715s sys-devices-platform-serial8250-tty-ttyS12.device
5.715s sys-devices-platform-serial8250-tty-ttyS27.device
5.715s dev-ttyS27.device
5.711s dev-ttyS24.device
5.711s sys-devices-platform-serial8250-tty-ttyS24.device
5.708s sys-devices-platform-serial8250-tty-ttyS9.device
5.708s dev-ttyS9.device
5.708s dev-ttyS11.device
5.708s sys-devices-platform-serial8250-tty-ttyS11.device
5.703s sys-devices-platform-serial8250-tty-ttyS26.device
5.703s dev-ttyS26.device
5.699s dev-ttyS28.device
5.699s sys-devices-platform-serial8250-tty-ttyS28.device
5.696s sys-devices-platform-serial8250-tty-ttyS20.device
5.696s dev-ttyS20.device
5.696s dev-ttyS30.device
5.696s sys-devices-platform-serial8250-tty-ttyS30.device
5.693s sys-devices-platform-serial8250-tty-ttyS21.device
5.693s dev-ttyS21.device
5.688s dev-ttyS5.device
5.687s sys-devices-platform-serial8250-tty-ttyS5.device
5.681s sys-devices-platform-serial8250-tty-ttyS13.device
5.681s dev-ttyS13.device
5.680s dev-ttyS14.device
5.680s sys-devices-platform-serial8250-tty-ttyS14.device
5.668s sys-devices-platform-serial8250-tty-ttyS16.device
5.668s dev-ttyS16.device
5.626s dev-disk-by\x2dlabel-Archive.device
5.626s dev-disk-by\x2duuid-08648A12648A0324.device
5.626s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_90LCPY35T\x2dpart1.device
5.626s dev-disk-by\x2ddiskseq-1\x2dpart1.device
5.626s dev-disk-by\x2did-wwn\x2d0x5000039a4270b76a\x2dpart1.device
5.626s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1.0\x2dpart1.device
5.626s dev-sda1.device
5.626s sys-devices-pci0000:00-0000:00:17.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
5.626s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1\x2dpart1.device
5.626s dev-disk-by\x2dpartuuid-d9fa2484\x2d01.device
5.614s sys-module-configfs.device
5.590s dev-sda2.device
5.590s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1.0\x2dpart2.device
5.590s dev-disk-by\x2did-wwn\x2d0x5000039a4270b76a\x2dpart2.device
5.590s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_90LCPY35T\x2dpart2.device
5.590s dev-disk-by\x2dpartuuid-d9fa2484\x2d02.device
5.590s dev-disk-by\x2dlabel-Linux\x5cx20Backup.device
5.590s dev-disk-by\x2duuid-bf7aca7f\x2dc941\x2d4590\x2d8cf1\x2daa83ae6523e8.device
5.590s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1\x2dpart2.device
5.590s dev-disk-by\x2ddiskseq-1\x2dpart2.device
5.590s sys-devices-pci0000:00-0000:00:17.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
5.512s sys-devices-pci0000:00-0000:00:17.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device
5.512s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_90LCPY35T\x2dpart3.device
5.512s dev-disk-by\x2duuid-396a60cf\x2d8e8b\x2d40d9\x2dba1d\x2d77bcd8dd74e7.device
5.512s dev-disk-by\x2ddiskseq-1\x2dpart3.device
5.512s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1.0\x2dpart3.device
5.512s dev-sda3.device
5.512s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1\x2dpart3.device
5.512s dev-disk-by\x2dpartuuid-d9fa2484\x2d03.device
5.512s dev-disk-by\x2did-wwn\x2d0x5000039a4270b76a\x2dpart3.device
5.404s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T\x2dpart1.device
5.404s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T_1\x2dpart1.device
5.404s dev-disk-by\x2did-nvme\x2deui.0025385a01b05282\x2dpart1.device
5.404s dev-disk-by\x2dpartuuid-2133a0ef\x2d3fed\x2d4866\x2d92b7\x2da0ab67deb82f.device
5.404s dev-nvme0n1p1.device
5.404s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
5.404s sys-devices-pci0000:00-0000:00:1d.4-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
5.404s dev-disk-by\x2duuid-7316\x2dEF51.device
5.404s dev-disk-by\x2ddiskseq-2\x2dpart1.device
5.404s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart1.device
5.398s dev-disk-by\x2ddiskseq-2\x2dpart3.device
5.398s dev-disk-by\x2duuid-9f4c4835\x2d7273\x2d4c9c\x2d969b\x2d244c367e72eb.device
5.398s dev-disk-by\x2dlabel-fedora_localhost\x2dlive.device
5.398s dev-nvme0n1p3.device
5.398s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart3.device
5.398s sys-devices-pci0000:00-0000:00:1d.4-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
5.398s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T\x2dpart3.device
5.398s dev-disk-by\x2did-nvme\x2deui.0025385a01b05282\x2dpart3.device
5.398s dev-disk-by\x2dpartuuid-e5e005a2\x2d2e54\x2d481e\x2dbbca\x2dcbe099778d41.device
5.398s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T_1\x2dpart3.device
5.296s dev-disk-by\x2did-nvme\x2deui.0025385a01b05282\x2dpart2.device
5.296s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1\x2dpart2.device
5.296s dev-disk-by\x2dpartuuid-ce1db8d0\x2dba6b\x2d4e62\x2da622\x2d70f067db2498.device
5.296s sys-devices-pci0000:00-0000:00:1d.4-0000:06:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
5.296s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T\x2dpart2.device
5.296s dev-nvme0n1p2.device
5.296s dev-disk-by\x2ddiskseq-2\x2dpart2.device
5.296s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T_1\x2dpart2.device
5.296s dev-disk-by\x2duuid-06773389\x2dc37d\x2d4f3c\x2d91d1\x2d062909c0d278.device
5.283s dev-disk-by\x2dpath-pci\x2d0000:06:00.0\x2dnvme\x2d1.device
5.283s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T_1.device
5.283s dev-disk-by\x2did-nvme\x2deui.0025385a01b05282.device
5.283s dev-nvme0n1.device
5.283s dev-disk-by\x2ddiskseq-2.device
5.283s sys-devices-pci0000:00-0000:00:1d.4-0000:06:00.0-nvme-nvme0-nvme0n1.device
5.283s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_500GB_S4EVNX0NA21122T.device
3.950s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
3.591s plymouth-quit-wait.service
2.609s dracut-initqueue.service
2.297s NetworkManager-wait-online.service
1.390s initrd-switch-root.service
1.248s NetworkManager.service
 866ms fwupd.service
 719ms systemd-journal-flush.service
 699ms firewalld.service
 658ms smartd.service
 484ms user@1000.service
 415ms udisks2.service
 362ms upower.service
 341ms systemd-tmpfiles-setup-dev.service
 331ms systemd-resolved.service
 311ms systemd-tmpfiles-setup.service
 311ms systemd-udev-trigger.service
 293ms systemd-oomd.service
 265ms accounts-daemon.service
 256ms polkit.service
 230ms abrtd.service
 196ms chronyd.service
 183ms systemd-journald.service
 176ms systemd-tmpfiles-setup-dev-early.service
 171ms systemd-sysctl.service
 168ms systemd-logind.service
 166ms dev-zram0.swap
 163ms systemd-vconsole-setup.service
 152ms systemd-userdbd.service
 150ms auditd.service
 143ms systemd-network-generator.service
 138ms import-state.service
 138ms systemd-binfmt.service
 138ms systemd-modules-load.service
 136ms lvm2-monitor.service
 136ms bluetooth.service
 136ms ModemManager.service
 133ms plymouth-switch-root.service
 131ms systemd-random-seed.service
 127ms rtkit-daemon.service
 126ms systemd-remount-fs.service
 125ms var-lib-nfs-rpc_pipefs.mount
 118ms dev-hugepages.mount
 117ms initrd-cleanup.service
 116ms systemd-zram-setup@zram0.service
 116ms kmod-static-nodes.service
 115ms dev-mqueue.mount
 112ms systemd-rfkill.service
 112ms sys-kernel-debug.mount
 110ms systemd-fsck@dev-disk-by\x2duuid-7316\x2dEF51.service
 109ms sys-kernel-tracing.mount
 103ms avahi-daemon.service
 102ms systemd-udevd.service
 101ms dracut-cmdline.service
  96ms sssd-kcm.service
  92ms switcheroo-control.service
  72ms dracut-pre-pivot.service
  70ms systemd-tmpfiles-clean.service
  68ms proc-sys-fs-binfmt_misc.mount
  63ms virtqemud.service
  61ms systemd-fsck@dev-disk-by\x2duuid-06773389\x2dc37d\x2d4f3c\x2d91d1\x2d062909c0d278.service
  61ms dracut-shutdown.service
  60ms boot.mount
  59ms systemd-machined.service
  56ms systemd-sysusers.service
  54ms thermald.service
  53ms systemd-backlight@backlight:intel_backlight.service
  43ms boot-efi.mount
  42ms dracut-pre-udev.service
  42ms flatpak-system-helper.service
  41ms plymouth-read-write.service
  41ms systemd-fsck-root.service
  38ms sys-fs-fuse-connections.mount
  36ms user-runtime-dir@1000.service
  32ms initrd-udevadm-cleanup-db.service
  31ms dbus-broker.service
  28ms systemd-update-utmp.service
  27ms uresourced.service
  24ms nordvpnd.socket
  24ms plymouth-start.service
  21ms initrd-parse-etc.service
  20ms gdm.service
  19ms systemd-user-sessions.service
  18ms gssproxy.service
  15ms modprobe@loop.service
  15ms modprobe@configfs.service
  15ms rpc-statd-notify.service
  14ms cups.service
  14ms systemd-update-utmp-runlevel.service
  14ms home.mount
  13ms colord.service
  12ms modprobe@dm_mod.service
  12ms wpa_supplicant.service
   8ms tmp.mount
   8ms modprobe@fuse.service
   6ms modprobe@drm.service
[behrooz@fedora ~]$ screenfetch
                                      OS: Fedora 
                                      Uptime: 20m
                                      Packages: 2137
 ,------------:MMMd--------    ---:   Resolution: 1536x864
                                      WM Theme: Adwaita
 :-    ------/hMMMy------------:      GTK Theme: Adwaita [GTK2/3]
        :-------------------::        Disk: 255G / 930G (28%)
        :-------------------::        CPU: Intel Core i3-1005G1 @ 4x 1.201GHz [41.0°C]
    /-----------omMMMNNNMMD  ---:     behrooz@fedora
 :-    ------/hMMMy------------:      Shell: bash 5.2.21
    /-----------omMMMNNNMMD  ---:     DE: GNOME 45.2
 :----    oNMMMMMMMMMNho     .----:   Font: Cantarell 11
  :-----------:MMMdP-------    ---\   GPU: Mesa Intel(R) UHD Graphics (ICL GT1)
 :------:://:-------------::          WM: Mutter
 :-    ------/hMMMy------------:      RAM: 3752MiB / 7735MiB
                                      Kernel: x86_64 Linux 6.6.8-200.fc39.x86_64
   :-----------sMMMMNMNMP.    ---:    Icon Theme: Adwaita
 :-   --------/MMMd-------------;    
[behrooz@fedora ~]$ 

With such a 1.2GHz CPU I would think that 11.9s to graphical .target is reasonable.
Why do you think its slow?

Have a look at systemd-analyze critical-chain to see what services are on the critical path.
That will show what the delays are step to step.

There is nothing in the screenfetch output that would be of concern except possibly the first line with the username and hostname.

It appears you did a lot of cut & paste editing so that portion of your data is difficult to decipher. (it is terribly out of order from what is normally seen). Mine shows this after removing the very first line.

$ screenfetch
        :-------------------::        OS: Fedora 
      :-----------/shhOHbmp---:\      Kernel: x86_64 Linux 6.6.9-200.fc39.x86_64
    /-----------omMMMNNNMMD  ---:     Uptime: 1d 19h 47m
   :-----------sMMMMNMNMP.    ---:    Packages: 3785
  :-----------:MMMdP-------    ---\   Shell: bash 5.2.21
 ,------------:MMMd--------    ---:   Resolution: 3840x2160
 :------------:MMMd-------    .---:   DE: GNOME 45.2
 :----    oNMMMMMMMMMNho     .----:   WM: Mutter
 :--     .+shhhMMMmhhy++   .------/   WM Theme: Adwaita
 :-    -------:MMMd--------------:    GTK Theme: Adwaita [GTK2/3]
 :-   --------/MMMd-------------;     Icon Theme: Adwaita
 :-    ------/hMMMy------------:      Font: Cantarell 11
 :-- :dMNdhhdNMMNo------------;       Disk: 5.2T / 6.4T (87%)
 :---:sdNMMMMNds:------------:        CPU: AMD Ryzen 7 5700X 8-Core @ 16x 3.4GHz
 :------:://:-------------::          GPU: NVIDIA GeForce RTX 3050
 :---------------------://            RAM: 5971MiB / 32016MiB

I don’t really understand your concern with only 24 seconds total boot time. Mine is about 40 seconds total with more than 15 seconds spent in the firmware stage where the bios is recognizing all the attached hardware. You have a much older and slower CPU, less RAM, and slower GPU as well, with much smaller disk space.

$ systemd-analyze
Startup finished in 15.693s (firmware) + 6.458s (loader) + 3.486s (kernel) + 2.734s (initrd) + 12.169s (userspace) = 40.541s 
graphical.target reached after 12.122s in userspace.
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 @12.068s
└─multi-user.target @12.068s
  └─plymouth-quit-wait.service @7.930s +4.128s
    └─systemd-user-sessions.service @7.880s +24ms
      └─remote-fs.target @7.872s
        └─remote-fs-pre.target @6.063s
          └─nfs-client.target @6.063s
            └─gssproxy.service @6.042s +19ms
              └─network.target @6.023s
                └─wpa_supplicant.service @6.008s +13ms
                  └─basic.target @3.672s
                    └─dbus-broker.service @3.646s +20ms
                      └─dbus.socket @3.631s
                        └─sysinit.target @3.627s
                          └─systemd-resolved.service @3.327s +298ms
                            └─systemd-tmpfiles-setup.service @3.066s +222ms
                              └─import-state.service @2.972s +82ms
                                └─local-fs.target @2.964s
                                  └─boot-efi.mount @2.670s +293ms
                                    └─boot.mount @2.536s +112ms
                                      └─systemd-fsck@dev-disk-by\x2duuid-06773389\x2dc37d\x2d4f3c\x2d91d1\x2d062909c0d278.service @2.428s +67ms
                                        └─dev-disk-by\x2duuid-06773389\x2dc37d\x2d4f3c\x2d91d1\x2d062909c0d278.device @584542y 2w 2d 20h 1min 46.646s +5.297s

Unfortunately for me, mine is far worse than yours. . .

scott@fedora:~$ systemd-analyze
Startup finished in 3.113s (firmware) + 2.154s (loader) + 1.154s (kernel) + 13.699s (initrd) + 29.583s (userspace) = 49.704s 
graphical.target reached after 29.554s in userspace.

:disappointed_relieved:

I wish my boot time was 24.143s, I am experiencing almost 15 minute boot time:
systemd-analyze
Startup finished in 1min 9.976s (firmware) + 2.692s (loader) + 1.654s (kernel) + 3min 23.506s (initrd) + 10min 13.216s (userspace) = 14min 51.046s
looks like my problem is with lvm2-monitor
systemd-analyze blame
10min 2.222s lvm2-monitor.service

Found the problem, had an unformatted SD card in the system so removed it and now boot time just under a minute.