wlog106
(log w)
March 22, 2025, 6:30pm
1
I’ve ran these command (imgs below) and found that a lot of blame start with “dev-disk-by…”.
Therefore, I thought it’s might cause by some disk partitioning or mounting issue.
However, I chose automatically partition when install fedora 41 so I not pretty sure about that…
31.397s sys-module-fuse.device
31.360s sys-devices-LNXSYSTM:00-LNXSYBUS:00-INTC7001:00-tpmrm-tpmrm0.device
31.360s dev-tpmrm0.device
31.359s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
31.359s dev-ttyS3.device
31.358s dev-ttyS1.device
31.358s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
31.357s dev-ttyS2.device
31.357s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
31.355s dev-ttyS0.device
31.355s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
31.347s sys-module-configfs.device
31.046s dev-disk-by\x2dpartuuid-0d97320e\x2d243a\x2d447b\x2db5b1\x2dae0b9ff70a5c.device
31.046s dev-disk-by\x2ddiskseq-1\x2dpart1.device
31.046s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
31.046s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-3310\x2d985D.device
31.046s dev-nvme0n1p1.device
31.046s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
31.046s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart1.device
31.046s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVL2512HDJD\x2d00BT7_S7CGNF0WC07406_1\x2dpart1.device
31.046s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0d97320e\x2d243a\x2d447b\x2>
31.046s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVL2512HDJD\x2d00BT7_S7CGNF0WC07406\x2dpart1.device
31.046s dev-disk-by\x2duuid-3310\x2d985D.device
31.046s dev-disk-by\x2did-nvme\x2deui.002538bc31c6dc1f\x2dpart1.device
31.046s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Par>
31.046s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
31.044s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-db79766b\x2dc569\x2d462b\x2>
31.044s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVL2512HDJD\x2d00BT7_S7CGNF0WC07406\x2dpart3.device
31.044s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
31.044s dev-disk-by\x2dpartuuid-db79766b\x2dc569\x2d462b\x2d9da0\x2dcf4478fa11c6.device
31.044s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
graphical.target @15.088s
└─multi-user.target @15.088s
└─plymouth-quit-wait.service @12.906s +2.180s
└─systemd-user-sessions.service @12.888s +16ms
└─remote-fs.target @12.885s
└─remote-fs-pre.target @2.439s
└─nfs-client.target @2.439s
└─gssproxy.service @2.062s +20ms
└─network.target @2.054s
└─wpa_supplicant.service @14.532s +16ms
└─basic.target @1.720s
└─dbus-broker.service @1.664s +54ms
└─dbus.socket @1.656s
└─sysinit.target @1.653s
└─systemd-resolved.service @1.614s +38ms
└─run-credentials-systemd\x2dresolved.service.mount @2.376s
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 3310-985D 579.4M 3% /boot/efi
├─nvme0n1p2 ext4 1.0 a2b2d8f6-6909-4e46-b82f-926b2d47505a 520.7M 40% /boot
└─nvme0n1p3 btrfs fedora 36c5319f-22f0-4b0f-9421-b5d3108d9428 1.4T 1% /home
/
nvme1n1
└─nvme1n1p1 btrfs fedora 36c5319f-22f0-4b0f-9421-b5d3108d9428
#
# /etc/fstab
# Created by anaconda on Sat Mar 22 02:07:24 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=36c5319f-22f0-4b0f-9421-b5d3108d9428 / btrfs subvol=root,compress=zstd:1 0 0
UUID=a2b2d8f6-6909-4e46-b82f-926b2d47505a /boot ext4 defaults 1 2
UUID=3310-985D /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=36c5319f-22f0-4b0f-9421-b5d3108d9428 /home btrfs subvol=home,compress=zstd:1 0 0
You can get a nice graphical printout and breakdown of boot times with
systemd-analyze plot > bootchart.svg
Which puts a file at /home/user/bootchart.svg
I have a similar login time, if it can be lowered that would be great, but I do not consider it overly long.
Please post text as preformatted text and not as screen shots using the </>
button. Please update your post with the text.
wlog106
(log w)
March 23, 2025, 9:07am
6
I will give it a try, thank you very much
wlog106
(log w)
March 23, 2025, 9:15am
7
Thanks you for pointing it out, I’d updated the post.
liviu
(.)
March 23, 2025, 9:45am
8
Yeah, the same, I dont know what’s the thing with those disks:
$ systemd-analyze blame
5.670s NetworkManager-wait-online.service
5.476s sys-module-configfs.device
5.469s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
5.469s dev-ttyS1.device
5.468s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
5.468s dev-ttyS2.device
5.466s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
5.466s dev-ttyS0.device
5.465s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.465s dev-ttyS3.device
5.462s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
5.462s dev-tpmrm0.device
5.175s dev-rfkill.device
5.175s sys-devices-virtual-misc-rfkill.device
5.035s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1d.4-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p3.device
5.035s dev-disk-by\x2dpartlabel-DEV.device
5.035s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE_1\x2dpart3.device
5.035s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-527f9c3c\x2d88a1\x2d49d2\x2d8ba2\x2d3473dbf1c6ea.device
5.035s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE\x2dpart3.device
5.035s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-DEV.device
5.035s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
5.035s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-520610ed\x2da51a\x2d4829\x2d8e8c\x2d832599b8b745.device
5.035s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart3.device
5.035s dev-disk-by\x2dpartuuid-527f9c3c\x2d88a1\x2d49d2\x2d8ba2\x2d3473dbf1c6ea.device
5.035s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223c6886ae\x2dpart3.device
5.035s dev-disk-by\x2ddiskseq-2\x2dpart3.device
5.035s dev-nvme1n1p3.device
5.035s dev-disk-by\x2duuid-520610ed\x2da51a\x2d4829\x2d8e8c\x2d832599b8b745.device
5.033s dev-disk-by\x2dpartuuid-6534b84d\x2d7972\x2d4e55\x2dad12\x2d3f447df6b426.device
5.033s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1d.4-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
5.033s dev-disk-by\x2ddiskseq-2\x2dpart1.device
5.033s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE_1\x2dpart1.device
5.033s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
5.033s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-73CF\x2d2AFD.device
5.033s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223c6886ae\x2dpart1.device
5.033s dev-disk-by\x2duuid-73CF\x2d2AFD.device
5.033s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE\x2dpart1.device
5.033s dev-nvme1n1p1.device
5.033s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart1.device
5.033s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-BOOT.device
5.033s dev-disk-by\x2dpartlabel-BOOT.device
5.033s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-6534b84d\x2d7972\x2d4e55\x2dad12\x2d3f447df6b426.device
5.026s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1b.4-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
5.026s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76863bcb725\x2dpart2.device
5.026s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72\x2dpart2.device
5.026s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
5.026s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-29b259a5\x2d9721\x2d4e99\x2d86f3\x2dad1bdbced61f.device
5.026s dev-disk-by\x2dpartlabel-REST.device
5.026s dev-nvme0n1p2.device
5.026s dev-disk-by\x2dpartuuid-29b259a5\x2d9721\x2d4e99\x2d86f3\x2dad1bdbced61f.device
5.026s dev-disk-by\x2ddiskseq-1\x2dpart2.device
5.026s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-REST.device
5.026s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72_1\x2dpart2.device
5.026s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart2.device
5.010s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1.device
5.010s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72_1.device
5.010s dev-nvme0n1.device
5.010s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1b.4-10000:e1:00.0-nvme-nvme0-nvme0n1.device
5.010s dev-disk-by\x2ddiskseq-1.device
5.010s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72.device
5.010s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76863bcb725.device
5.007s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223c6886ae.device
5.007s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1.device
5.007s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE.device
5.007s dev-disk-by\x2ddiskseq-2.device
5.007s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE_1.device
5.007s dev-nvme1n1.device
5.007s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1d.4-10000:e2:00.0-nvme-nvme1-nvme1n1.device
4.254s systemd-udev-settle.service
4.209s sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d3-1\x2d3:1.0-0003:0B05:19B6.0002-leds-asus::kbd_backlight.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart1.device
4.111s dev-disk-by\x2dlabel-zroot.device
4.111s dev-disk-by\x2dpartuuid-ff914b23\x2d6f7f\x2d4b82\x2db095\x2dcc0626123492.device
4.111s dev-disk-by\x2duuid-14302112488605340870.device
4.111s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1b.4-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
4.111s dev-disk-by\x2ddiskseq-1\x2dpart1.device
4.111s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76863bcb725\x2dpart1.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
4.111s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72\x2dpart1.device
4.111s dev-disk-by\x2dpartlabel-POOL\x2dDISK1.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-zroot.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-POOL\x2dDISK1.device
4.111s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76863BCB72_1\x2dpart1.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-ff914b23\x2d6f7f\x2d4b82\x2db095\x2dcc0626123492.device
4.111s dev-nvme0n1p1.device
4.111s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-14302112488605340870.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-zroot.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart2.device
4.109s dev-nvme1n1p2.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-3802ff34\x2d6ee3\x2d4c1a\x2d974f\x2d84638cb2f6bc.device
4.109s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE\x2dpart2.device
4.109s dev-disk-by\x2dpartlabel-POOL\x2dDISK0.device
4.109s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223c6886ae\x2dpart2.device
4.109s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:1d.4-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
4.109s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA1T0QFM_22423C6886AE_1\x2dpart2.device
4.109s dev-disk-by\x2ddiskseq-2\x2dpart2.device
4.109s dev-disk-by\x2dpartuuid-3802ff34\x2d6ee3\x2d4c1a\x2d974f\x2d84638cb2f6bc.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-14302112488605340870.device
4.109s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-POOL\x2dDISK0.device
1 Like
I see graphical.target in 15s but the other log shows times into the 30’s.
Are they from the same boot?
wlog106
(log w)
March 23, 2025, 4:23pm
10
I think the 15s is indicate that graphical.target reach after 15s in userspace
and the 30s maybe the time spent to run the device… etc.
yes they are from same boot!
I expect the disks to be mounted before graphical target is reached.
Are all the disks listed in /etc/fstab?
wlog106
(log w)
March 23, 2025, 4:31pm
12
I’m pretty sure that the disks are mounted before graphical target is reached
after I check the systemd-analyze plot? Am I miss anything?
And YES all the disks are listed in /etc/fstab
wlog106
(log w)
March 23, 2025, 4:34pm
13
btw, my last boot time decrease from about 1 min to 25s
I’m not sure if it can be attribute to that I mask sys-module-fuse.device or not
There is an issue with initing some GPUs for plymouth.
Maybe you have one of these GPUs?
I do not recall which GPUs are affected.
I understood that the DRM driver is loaded in response to plymouth requesting it to be loaded. So it may well be different apparently.
wlog106
(log w)
March 24, 2025, 2:34am
19
Isn’t the DRM driver need to be loaded to help plymouth show that splash booting animation?
I found that disable plymouth may not directly affect the boot times.
Maybe plymouth request the DRM driver to load is the true cause?
A problem in 2018 is unlikely to be an issue in 2025.
1 Like