About 2 minutes delay on boot Fedora 36

[admin@main ~]$ systemd-analyze
Startup finished in 1.324s (kernel) + 4.353s (initrd) + 1min 59.397s (userspace) = 2min 5.075s
graphical.target reached after 1min 59.375s in userspace

[admin@main ~]$ 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 @1min 59.375s
└─multi-user.target @1min 59.375s
└─plymouth-quit-wait.service @1min 38.607s +20.762s
└─systemd-user-sessions.service @1min 38.574s +28ms
└─remote-fs.target @1min 38.571s
└─remote-fs-pre.target @1min 38.571s
└─nfs-client.target @1min 32.877s
└─gssproxy.service @1min 32.842s +33ms
└─network.target @1min 32.838s
└─wpa_supplicant.service @1min 41.410s +18ms
└─dbus-broker.service @1min 31.485s +120ms
└─dbus.socket @1min 31.402s
└─sysinit.target @1min 31.398s
└─systemd-update-utmp.service @1min 31.378s +19ms
└─auditd.service @1min 31.290s +86ms
└─systemd-tmpfiles-setup.service @1min 31.189s +97ms
└─import-state.service @1min 31.151s +36ms
└─local-fs.target @1min 31.149s
└─run-user-1000-doc.mount @1min 43.272s
└─run-user-1000.mount @1min 38.987s
└─local-fs-pre.target @1min 10.636s
└─lvm2-monitor.service @1.003s +884ms
└─dm-event.socket @993ms
└─system.slice
└─-.slice
[admin@main ~]$

[admin@main ~]$ systemd-analyze blame

Спойлер

1min 9.474s systemd-udev-settle.service
20.762s plymouth-quit-wait.service
8.011s systemd-cryptsetup@luks\x2d714fc88b\x2d1278\x2d4ba8\x2dbb0c\x2d43de>
5.729s NetworkManager-wait-online.service
2.191s dracut-initqueue.service
1.392s dkms.service
1.299s initrd-switch-root.service
943ms udisks2.service
884ms lvm2-monitor.service
650ms systemd-fsck-root.service
606ms fwupd.service
461ms power-profiles-daemon.service
444ms accounts-daemon.service
429ms polkit.service
320ms sssd-kcm.service
305ms dnf-makecache.service
295ms user@1000.service
278ms systemd-journal-flush.service
217ms avahi-daemon.service
216ms upower.service
207ms akmods.service
201ms rtkit-daemon.service
198ms firewalld.service
197ms initrd-cleanup.service
186ms switcheroo-control.service
185ms systemd-machined.service
179ms systemd-homed.service
176ms systemd-logind.service
173ms thermald.service
173ms initrd-parse-etc.service
165ms abrtd.service
162ms systemd-resolved.service
153ms smartd.service
137ms systemd-udev-trigger.service
135ms i2pd.service
134ms cups.service
120ms dbus-broker.service
112ms lm_sensors.service
97ms systemd-tmpfiles-setup.service

I cannot be sure but that problem exists since my manipulations with grub when Nvidia driver install (nano /etc/default/grub). There is another assumption. The problem arose after increasing the /boot partition (swap was reduced). The standard Disks program was used.

Any help appreciated.

[admin@main ~]$ systemctl list-dependencies plymouth-quit-wait.service

Спойлер

plymouth-quit-wait.service
● ├─system.slice
● └─sysinit.target
● ├─dev-hugepages.mount
● ├─dev-mqueue.mount
● ├─dracut-shutdown.service
● ├─import-state.service
○ ├─iscsi-onboot.service
● ├─kmod-static-nodes.service
○ ├─ldconfig.service
● ├─lvm2-lvmpolld.socket
● ├─lvm2-monitor.service
○ ├─multipathd.service
● ├─plymouth-read-write.service
● ├─plymouth-start.service
plymouth-quit-wait.service
● ├─system.slice
● └─sysinit.target
● ├─dev-hugepages.mount
● ├─dev-mqueue.mount
● ├─dracut-shutdown.service
● ├─import-state.service
○ ├─iscsi-onboot.service
● ├─kmod-static-nodes.service
○ ├─ldconfig.service
● ├─lvm2-lvmpolld.socket
● ├─lvm2-monitor.service
○ ├─multipathd.service
● ├─plymouth-read-write.service
● ├─plymouth-start.service
plymouth-quit-wait.service
● ├─system.slice
● └─sysinit.target
● ├─dev-hugepages.mount
● ├─dev-mqueue.mount
● ├─dracut-shutdown.service
● ├─import-state.service
○ ├─iscsi-onboot.service
● ├─kmod-static-nodes.service
○ ├─ldconfig.service
● ├─lvm2-lvmpolld.socket
● ├─lvm2-monitor.service
○ ├─multipathd.service
● ├─plymouth-read-write.service
● ├─plymouth-start.service
● ├─proc-sys-fs-binfmt_misc.automount
○ ├─selinux-autorelabel-mark.service
● ├─sys-fs-fuse-connections.mount
● ├─sys-kernel-config.mount
● ├─sys-kernel-debug.mount
● ├─sys-kernel-tracing.mount
○ ├─systemd-ask-password-console.path
● ├─systemd-binfmt.service
○ ├─systemd-boot-system-token.service
○ ├─systemd-firstboot.service
○ ├─systemd-hwdb-update.service
○ ├─systemd-journal-catalog-update.service
● ├─systemd-journal-flush.service
● ├─systemd-journald.service
○ ├─systemd-machine-id-commit.service
● ├─systemd-modules-load.service
● ├─systemd-random-seed.service
○ ├─systemd-repart.service
● ├─systemd-sysctl.service
○ ├─systemd-sysusers.service
● ├─systemd-tmpfiles-setup-dev.service
● ├─systemd-tmpfiles-setup.service
● ├─systemd-udev-trigger.service
● ├─systemd-udevd.service
○ ├─systemd-update-done.service
● ├─systemd-update-utmp.service
● ├─cryptsetup.target
● │ └─systemd-cryptsetup@luks\x2d714fc88b\x2d1278\x2d4ba8\x2dbb0c\x2d43de1223>
● ├─integritysetup.target
● ├─local-fs.target
● │ ├─-.mount
● │ ├─boot.mount
● │ ├─home.mount
○ │ ├─ostree-remount.service
● │ ├─systemd-fsck-root.service
● │ ├─systemd-remount-fs.service
● │ └─tmp.mount
○ ├─swap.target
○ │ ├─dev-disk-by\x2duuid-c267faa9\x2d4020\x2d4d5c\x2d840c\x2d71b21c883e34.sw>
● │ └─dev-zram0.swap
● └─veritysetup.target
lines 16-56/56 (END)

You said you made changes.
Please list in detail exactly what changes were made from the default.

Also, the systemd-analyze blame shows that over a minute of that was taken by systemd-udev-settle.service. What is attached (USB or otherwise) that may take that long to configure? NAS, flash drives, SSD, ?

Hi Jeff!
Thanks for the response!

[admin@main ~]$ lsblk

Спойлер

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1,4G 0 part /boot
├─sda2 8:2 0 23,1G 0 part
├─sda3 8:3 0 112,3G 0 part /
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 794,8G 0 part
└─luks-714fc88b-1278-4ba8-bb0c-43de1223f6bf
253:0 0 794,7G 0 crypt /home
sdb 8:16 0 5,5T 0 disk
├─sdb1 8:17 0 100M 0 part
├─sdb2 8:18 0 16M 0 part
├─sdb3 8:19 0 839,2G 0 part
├─sdb4 8:20 0 521M 0 part
├─sdb5 8:21 0 1,6T 0 part
└─sdb6 8:22 0 3,1T 0 part
sr0 11:0 1 1024M 0 rom
zram0 252:0 0 8G 0 disk [SWAP]

[admin@main ~]$ lsblk -f

Спойлер

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
│ ext4 1.0 24b0f64f-1539-4adc-a4a2-4aba4ab16cc2 888,1M 30% /boot
├─sda2
│ ext4 1.0 2b95b2e7-3101-498f-aa75-a528c0454e9a
├─sda3
│ ext4 1.0 8f5e398e-4f1f-4fdb-8335-1ed064147748 72,3G 29% /
├─sda4

└─sda5
crypto 2 714fc88b-1278-4ba8-bb0c-43de1223f6bf
└─luks-714fc88b-1278-4ba8-bb0c-43de1223f6bf
ext4 1.0 1c4f9223-2862-4fc2-a4a9-506bdcd1c24c 151,2G 76% /home
sdb
├─sdb1
│ vfat FAT32 4E75-3E94
├─sdb2

├─sdb3
│ ntfs SYSTEM
│ C236B9A836B99DBB
├─sdb4
│ ntfs 18AC5040AC501A98
├─sdb5
│ ntfs WORK 66D2731FD272F323
└─sdb6
ntfs MULTIMEDIA
84DC1C82DC1C7122
sr0
zram0
[SWAP]

[admin@main ~]$ sudo lshw -class disk

Спойлер

*-disk:0
description: ATA Disk
product: WDC WDS100T2B0A
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 20WD
serial: YYYYYYYYYYYY
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=66f4d82a
*-disk:1
description: ATA Disk
product: HGST HUS726T6TAL
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/sdb
version: W984
serial: YYYYYYYY
size: 5589GiB (6001GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=ac28c045-d929-40b6-a09f-e23a8b99207d logicalsectorsize=512 sectorsize=4096
*-cdrom
description: DVD-RAM writer
product: DRW-24F1ST a
vendor: ASUS
physical id: 0.0.0
bus info: scsi@5:0.0.0
logical name: /dev/cdrom
logical name: /dev/sr0
version: 1.00
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc
[admin@main ~]$

[admin@main ~]$ nano /etc/default/grub

Спойлер

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=“$(sed ‘s, release .*$,g’ /etc/system-release)”
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT=“console”
GRUB_CMDLINE_LINUX=“resume=UUID=c267faa9-4020-4d5c-840c-71b21c883e34 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1”
GRUB_DISABLE_RECOVERY=“true”
GRUB_ENABLE_BLSCFG=true

That’s all.

Can you check systemctl --reverse list-dependencies systemd-udev-settle.service

I don’t believe that be running unless you’re using DMRAID,
ref: Disable dmraid.service on first run if no dmraid sets are found - Fedora 33 System-Wide Change proposal - devel - Fedora Mailing-Lists)

The F36 manpage of this service states: Using this service is not recommended.
I had a 2 minute delay plus error on this service, and after reading the manpage I simply disabled the service. No delay, no error, and no problems introduced.

1 Like

[admin@main ~]$ systemctl --reverse list-dependencies systemd-udev-settle.service
systemd-udev-settle.service
○ └─multipathd.service
[admin@main ~]$

:frowning: Not fixed until Fedora 37.
https://bugzilla.redhat.com/show_bug.cgi?id=2001058
Workaround from the bug:
sudo systemctl mask systemd-udev-settle.service

1 Like

Looking at the two drives, sdb is showing what appears to be an efi partition, sdb1, and is partitioned gpt as would be expected for windows with uefi boot.
Your output of lsblk -f does not show a mounted /boot/efi as would be expected for efi boot with fedora.

I wonder if you installed fedora in legacy mode with windows installed in uefi mode and if that may be part of the problem. You have not stated anything about dual booting nor if there may be an issue with that so I may be out in left field with this.

Others have made suggestions as well, so we will wait for your replies to the comments.

1 Like