Extremely Slow Boot with Fresh Install

Ask Fedora
1

Hello,

Just switch from Windows to Fedora. I am concerned with my Boot Time, it is around 1 minute 16 seconds. My guess is that it is something to do with my second SSD drive. I have added it to fstab to have it mount automatically. This drive is just for Steam and Games. Here is some logs:

systemd-analyze blame
26.183s upower.service
4.918s sys-module-fuse.device
4.822s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
4.822s dev-tpmrm0.device
4.821s dev-ttyS0.device
4.821s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
4.820s dev-ttyS1.device
4.820s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
4.819s dev-ttyS2.device
4.819s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
4.819s dev-ttyS3.device
4.819s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
4.805s sys-module-configfs.device
4.796s dev-nvme1n1p2.device
4.796s dev-disk-by\x2did-nvme\x2deui.0025384741a20eb6\x2dpart2.device
4.796s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-6c5b2c7b\x2da3df\x2d4e3b\x2d84fe\x2dc74e6867f949.device
4.796s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-dcb67589\x2d8742\x2d4bfa\x2da9ef\x2ddfa88f21b8f1.device
4.796s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
4.796s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B\x2dpart2.device
4.796s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
4.796s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
4.796s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B_1\x2dpart2.device
4.796s dev-disk-by\x2dpartuuid-dcb67589\x2d8742\x2d4bfa\x2da9ef\x2ddfa88f21b8f1.device
4.796s dev-disk-by\x2ddiskseq-1\x2dpart2.device
4.796s dev-disk-by\x2duuid-6c5b2c7b\x2da3df\x2d4e3b\x2d84fe\x2dc74e6867f949.device
4.794s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1\x2dpart1.device
4.794s dev-nvme0n1p1.device
4.794s sys-devices-pci0000:00-0000:00:02.2-0000:0e:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
4.794s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
4.794s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-Games.device
4.794s dev-disk-by\x2dpartuuid-5627845f\x2da3c2\x2d43de\x2d87ee\x2d9b9ce30eee1c.device
4.794s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-aa8d25ba\x2d1c8b\x2d41af\x2dab25\x2dc875cc8dc9c0.device
4.794s dev-disk-by\x2duuid-aa8d25ba\x2d1c8b\x2d41af\x2dab25\x2dc875cc8dc9c0.device
4.794s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X914549Y_1\x2dpart1.device
4.794s dev-disk-by\x2ddiskseq-2\x2dpart1.device
4.794s dev-disk-by\x2dlabel-Games.device
4.794s dev-disk-by\x2did-nvme\x2deui.0025384941a0d177\x2dpart1.device
4.794s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-5627845f\x2da3c2\x2d43de\x2d87ee\x2d9b9ce30eee1c.device
4.794s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X914549Y\x2dpart1.device
4.792s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
4.792s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
4.792s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
4.792s dev-disk-by\x2ddiskseq-1\x2dpart1.device
4.792s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-1F7E\x2dED29.device
4.792s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B_1\x2dpart1.device
4.792s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-7add089e\x2de011\x2d4441\x2d9291\x2d185ada89054c.device
4.792s dev-disk-by\x2dpartuuid-7add089e\x2de011\x2d4441\x2d9291\x2d185ada89054c.device
4.792s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
4.792s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B\x2dpart1.device
4.792s dev-nvme1n1p1.device
4.792s dev-disk-by\x2duuid-1F7E\x2dED29.device
4.792s dev-disk-by\x2did-nvme\x2deui.0025384741a20eb6\x2dpart1.device
4.792s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
4.790s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-System.device
4.790s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
4.790s dev-disk-by\x2did-nvme\x2deui.0025384741a20eb6\x2dpart3.device
4.790s dev-disk-by\x2dpartuuid-06c0f16a\x2dfa48\x2d4cc6\x2d9add\x2d7fca88b3017d.device
4.790s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
4.790s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-06c0f16a\x2dfa48\x2d4cc6\x2d9add\x2d7fca88b3017d.device
4.790s dev-disk-by\x2dlabel-System.device
4.790s dev-nvme1n1p3.device
4.790s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-e74b8309\x2db4dd\x2d4da0\x2d8106\x2d83300c01387a.device
4.790s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p3.device
4.790s dev-disk-by\x2duuid-e74b8309\x2db4dd\x2d4da0\x2d8106\x2d83300c01387a.device
4.790s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B_1\x2dpart3.device
4.790s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B\x2dpart3.device
4.790s dev-disk-by\x2ddiskseq-1\x2dpart3.device
4.779s dev-disk-by\x2ddiskseq-2.device
4.779s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X914549Y.device
4.779s dev-disk-by\x2dpath-pci\x2d0000:0e:00.0\x2dnvme\x2d1.device
4.779s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X914549Y_1.device
4.779s dev-nvme0n1.device
4.779s sys-devices-pci0000:00-0000:00:02.2-0000:0e:00.0-nvme-nvme0-nvme0n1.device
4.779s dev-disk-by\x2did-nvme\x2deui.0025384941a0d177.device
4.774s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B.device
4.774s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
4.774s dev-nvme1n1.device
4.774s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_2TB_S7KHNU0X741182B_1.device
4.774s dev-disk-by\x2did-nvme\x2deui.0025384741a20eb6.device
4.774s dev-disk-by\x2ddiskseq-1.device
4.774s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme1-nvme1n1.device
2.685s NetworkManager-wait-online.service
480ms initrd-switch-root.service
235ms tuned.service
186ms firewalld.service
143ms systemd-udev-trigger.service
126ms abrtd.service
119ms user@1000.service
117ms systemd-journal-flush.service
99ms systemd-tmpfiles-setup.service
96ms tuned-ppd.service
92ms systemd-tmpfiles-setup-dev-early.service
76ms lvm2-monitor.service
76ms media-Games.mount
72ms var-lib-nfs-rpc_pipefs.mount
71ms udisks2.service
62ms ModemManager.service
60ms systemd-random-seed.service
58ms dev-zram0.swap
55ms systemd-udevd.service
53ms NetworkManager.service
53ms accounts-daemon.service
52ms polkit.service
51ms systemd-tmpfiles-clean.service
50ms systemd-journald.service
49ms bluetooth.service
43ms systemd-logind.service
42ms avahi-daemon.service
41ms chronyd.service
41ms systemd-vconsole-setup.service
39ms systemd-tmpfiles-setup-dev.service
39ms systemd-resolved.service
38ms systemd-sysctl.service
36ms systemd-userdbd.service
36ms dracut-pre-udev.service
34ms systemd-hostnamed.service
33ms dbus-broker.service
32ms rsyslog.service
31ms plymouth-switch-root.service
30ms boot-efi.mount
30ms dev-hugepages.mount
30ms boot.mount
29ms dev-mqueue.mount
29ms sys-kernel-debug.mount
28ms systemd-zram-setup@zram0.service
28ms systemd-fsck-root.service
26ms user-runtime-dir@1000.service
26ms systemd-oomd.service
25ms plymouth-read-write.service
24ms plymouth-quit-wait.service
24ms dracut-cmdline.service
24ms plymouth-quit.service
22ms systemd-fsck@dev-disk-by\x2duuid-6c5b2c7b\x2da3df\x2d4e3b\x2d84fe\x2dc74e6867f949.service
21ms gssproxy.service
21ms switcheroo-control.service
21ms smartd.service
20ms modprobe@configfs.service
20ms systemd-rfkill.service
19ms systemd-fsck@dev-disk-by\x2duuid-1F7E\x2dED29.service
19ms modprobe@fuse.service
19ms systemd-update-utmp-runlevel.service
19ms home.mount
19ms auditd.service
18ms rpc-statd-notify.service
17ms modprobe@dm_mod.service
17ms modprobe@efi_pstore.service
17ms systemd-user-sessions.service
17ms modprobe@loop.service
16ms uresourced.service
15ms plymouth-start.service
15ms cups.service
14ms systemd-homed.service
13ms dracut-shutdown.service
13ms audit-rules.service
13ms rtkit-daemon.service
13ms dracut-pre-pivot.service
12ms sys-kernel-tracing.mount
11ms kmod-static-nodes.service
10ms initrd-cleanup.service
10ms modprobe@drm.service
10ms initrd-parse-etc.service
9ms systemd-udev-load-credentials.service
7ms initrd-udevadm-cleanup-db.service
7ms systemd-modules-load.service
6ms systemd-remount-fs.service
5ms systemd-update-utmp.service
5ms systemd-sysusers.service
3ms sys-fs-fuse-connections.mount
2ms tmp.mount
64us systemd-homed-activate.service
3

This is my fstab file:

#
# /etc/fstab
# Created by anaconda on Mon Apr 28 23:43:19 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=e74b8309-b4dd-4da0-8106-83300c01387a /                       btrfs   subvol=root,compress=zstd:1 0 0
UUID=6c5b2c7b-a3df-4e3b-84fe-c74e6867f949 /boot                   ext4    defaults        1 2
UUID=1F7E-ED29          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=e74b8309-b4dd-4da0-8106-83300c01387a /home                   btrfs   subvol=home,compress=zstd:1 0 0

# Programs (dev/nvme1n1)
UUID=aa8d25ba-1c8b-41af-ab25-c875cc8dc9c0       /media/Games    ext4    defaults        0       0
4

Fyi please use preformatted text for code and logs.
It is the </> button, I fixed your fstab post for you.

Can you post the output of systemd-analyze critical-chain please?

5 
sudo systemctl status upower.service
6

Ok, cleaned up my post, sorry about that.

Here is 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 @28.005s
└─upower.service @1.690s +26.314s
  └─basic.target @1.667s
    └─dbus-broker.service @1.627s +38ms
      └─dbus.socket @1.622s
        └─sysinit.target @1.619s
          └─systemd-resolved.service @1.579s +39ms
            └─systemd-tmpfiles-setup.service @1.465s +102ms
              └─local-fs.target @1.463s
                └─run-user-1000-doc.mount @17.432s
                  └─run-user-1000.mount @16.937s
                    └─swap.target @699ms
                      └─dev-zram0.swap @649ms +48ms
                        └─systemd-zram-setup@zram0.service @633ms +15ms
                          └─dev-zram0.device @625ms
7 
● upower.service - Daemon for power management
     Loaded: loaded (/usr/lib/systemd/system/upower.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (running) since Wed 2025-04-30 08:52:37 EDT; 6min ago
 Invocation: 20ac40fe044e4d118352ca1358ead920
       Docs: man:upowerd(8)
   Main PID: 1172 (upowerd)
      Tasks: 4 (limit: 37288)
     Memory: 4.6M (peak: 5M)
        CPU: 89ms
     CGroup: /system.slice/upower.service
             └─1172 /usr/libexec/upowerd
8

Please show us the list of devices: upower --enumerate (the “DisplayDevice” refers to how power status is displayed) and the output from journalctl --no-hostname -b -g upower.

1 Like
9

Here you go:

upower --enumerate
/org/freedesktop/UPower/devices/DisplayDevice

journalctl --no-hostname -b -g upower
Apr 30 11:37:28 systemd[1]: Starting upower.service - Daemon for power management...
Apr 30 11:37:32 wireplumber[1532]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Apr 30 11:37:55 systemd[1]: Started upower.service - Daemon for power management.
Apr 30 11:37:55 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" h>

upower -i /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         no
  updated:              Wed 30 Apr 2025 11:37:55 AM EDT (1061 seconds ago)
  has history:          no
  has statistics:       no
  unknown
    warning-level:       none
    percentage:          0%
    icon-name:          'battery-missing-symbolic'
10

Looks like upower couldn’t determine how your system is powered. Is there something unusual about your system’s power source (e.g., laptop without battery or very old desktop hardware)?

11

Its a new PC that i built. Nothing unusual about the setup or power. The power supply is a Corsair RM1200, AMD Processor and Radeon Hellhound GPU. Is there a way to fix this?

Processor: AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 32 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT
Motherboard: ASUS
Power Supply: Corsair RM1200
12

The problem could be a linux bug, defective system board, or firmware. Try booting a couple different distros’ “Live USB” and see if upower works. If not, you should check for firmware updates and if that doesn’t help, contact ASUS.

13

It could be a usb device delaying upower

post

upower -d

also it’s normal for desktops to show ‘no power’ for /org/freedesktop/UPower/devices/DisplayDevice

$ upower -d
Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0
  native-path:          hidpp_battery_0
  model:                Logitech K400 Plus
  serial:               43-64-12-ad
  power supply:         no
  updated:              Thu 01 May 2025 01:02:02 BST (13 seconds ago)
  has history:          yes
  has statistics:       yes
  mouse
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       none
    battery-level:       normal
    percentage:          55% (should be ignored)
    icon-name:          'battery-low-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         no
  updated:              Thu 24 Apr 2025 15:33:27 BST (552528 seconds ago)
  has history:          no
  has statistics:       no
  unknown
    warning-level:       none
    percentage:          0%
    icon-name:          'battery-missing-symbolic'

Daemon:
  daemon-version:  1.90.9
  on-battery:      no
  lid-is-closed:   no
  lid-is-present:  no
  critical-action: PowerOff
14

I unplugged all USB devices and then only plugged in my keyboard when I got to the login screen. Unfortunately, it didnt work.

I was able to shed 20+ seconds by changing these settings in my Asus Bios:

The first setting is: AI Tweaker - DRAM Timing Control - Memory Context Restore - Enabled.

Second: Advanced - AMD CBS - UMC Common Options - DDR Options - DDR Memory Features - Memory Context Restore - Enabled.

Last boot:

systemd-analyze
Startup finished in 13.606s (firmware) + 1.733s (loader) + 1.870s (kernel) + 3.837s (initrd) + 28.089s (userspace) = 49.138s 
graphical.target reached after 28.066s in userspace.

Unfortunately upower.service is still at 26.355s and I just don’t know what the issue is.

15 
systemd-analyze critical-chain upower.service
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.

upower.service +26.429s
└─basic.target @1.689s
  └─dbus-broker.service @1.655s +32ms
    └─dbus.socket @1.651s
      └─sysinit.target @1.648s
        └─systemd-resolved.service @1.607s +41ms
          └─systemd-tmpfiles-setup.service @1.479s +106ms
            └─local-fs.target @1.476s
              └─run-user-1000-doc.mount @11.177s
                └─run-user-1000.mount @10.648s
                  └─swap.target @696ms
                    └─dev-zram0.swap @650ms +45ms
                      └─systemd-zram-setup@zram0.service @634ms +14ms
                        └─dev-zram0.device @624ms

Looks like run-user-1000.mount is the issue with upower. This is my Gaming second drive that I had to add to fstab manually to mount. Not sure if I am right and no idea how to fix it.

16

Not sure if this is the right solution, but we are down to 28s.

systemd-analyze
Startup finished in 14.444s (firmware) + 1.776s (loader) + 1.861s (kernel) + 5.306s (initrd) + 4.818s (userspace) = 28.208s 
graphical.target reached after 4.798s in userspace.

Basically to achieve this I disabled upower.service using these commands:

sudo systemctl disable upower.service
sudo systemctl mask upower.service

This seems like im just covering up a potential issue, instead of fixing it. Please let me know if this will hurt anything? Thanks for the help to all of you.