Description of problem: the system takes more than a minute to boot Version-Release number of selected component (if applicable): systemd-libs-248.7-1.fc34.x86_64 systemd-rpm-macros-248.7-1.fc34.noarch systemd-networkd-248.7-1.fc34.x86_64 systemd-pam-248.7-1.fc34.x86_64 systemd-248.7-1.fc34.x86_64 systemd-udev-248.7-1.fc34.x86_64 How reproducible: always Steps to Reproduce: 1. just boot 2. 3. Actual results: the boot takes over a minute Expected results: a fast boot Additional info: i have a nvidia gpu so i tried to disable the i2c of that card, but that did not help [root@DESKTOP-E83VF5L oli]# systemd-analyze blame 6min 12.025s dracut-initqueue.service 6min 11.555s systemd-cryptsetup@luks\x2d673654a4\x2d1003\x2d4baf\x2d803b\x2d1d3> 1min 3.026s systemd-udev-settle.service 3.152s NetworkManager-wait-online.service 984ms plymouth-quit-wait.service 585ms systemd-journal-flush.service 569ms firewalld.service 537ms lvm2-monitor.service 461ms upower.service 444ms akmods.service 421ms sssd.service 363ms initrd-switch-root.service 320ms lightdm.service 161ms udisks2.service 107ms user 102ms abrtd.service 90ms systemd-resolved.service 87ms ModemManager.service 87ms initrd-parse-etc.service 76ms polkit.service 65ms cups.service 54ms systemd-udev-trigger.service 49ms systemd-udevd.service i was not at the pc when the password prompt appeared, so the cryptsetup thing can be ignored [root@DESKTOP-E83VF5L modprobe.d]# cat blackist-i2c-nvidia-gpu.conf blacklist i2c_nvidia_gpu
systemd-udev-settle.service is only provided for backwards compatibility and is not recommended to be used. Please figure out what uses it and reassign this bug against that package.
systemd-udev-settle.service ○ └─multipathd.service ● └─sysinit.target ● ├─abrt-journal-core.service ● │ └─multi-user.target ● │ └─graphical.target ● ├─abrt-oops.service ● │ └─multi-user.target ● │ └─graphical.target ○ ├─abrt-vmcore.service ● │ └─multi-user.target ● │ └─graphical.target ● ├─abrt-xorg.service ● │ └─multi-user.target ● │ └─graphical.target ● ├─abrtd.service ● │ ├─abrt-journal-core.service ● │ │ └─multi-user.target ● │ │ └─graphical.target ● │ ├─abrt-oops.service ● │ │ └─multi-user.target ● │ │ └─graphical.target ○ │ ├─abrt-vmcore.service ● │ │ └─multi-user.target ● │ │ └─graphical.target ● │ ├─abrt-xorg.service ● │ │ └─multi-user.target ● │ │ └─graphical.target ● │ └─multi-user.target ● │ └─graphical.target ● ├─accounts-daemon.service ● │ └─graphical.target ● ├─akmods.service ● │ └─multi-user.target ● │ └─graphical.target ● ├─akmods.16-200.fc34.x86_64.service ○ ├─alsa-restore.service ● │ └─sound.target ● │ ├─sys-devices-pci0000:00-0000:00:01.3-0000:01:00.0-usb1-1\x2d6-1\x2d6:1… ● │ ├─sys-devices-pci0000:00-0000:00:01.3-0000:01:00.2-0000:02:07.0-0000:09… ● │ ├─sys-devices-pci0000:00-0000:00:03.1-0000:0a:00.1-sound-card2-controlC… ● │ ├─sys-devices-pci0000:00-0000:00:08.1-0000:0c:00.3-usb3-3\x2d2-3\x2d2:1… ● │ └─sys-devices-pci0000:00-0000:00:08.1-0000:0c:00.4-sound-card3-controlC… ● ├─alsa-state.service ● │ └─sound.target not sure how to find out what service/application that installed/required, can you tell me how to figure that out? i used systemctl list-dependencies systemd-udev-settle.service --all --reverse
Oh, multipath. This is a known issue. If you are NOT using multipath, you can disable the service with 'sudo systemctl disable --now multipathd'. If you ARE using it, then please see the linked bug. *** This bug has been marked as a duplicate of bug 2001058 ***