Description of problem: when i boot my linux system, it takes very long. compared to windows with veracrypt, which is very fast. Version-Release number of selected component (if applicable): systemd-245.4-1.fc32.x86_64 How reproducible: always Steps to Reproduce: 1. install a fresh f32 spin with encrypted partitions 2. 3. Actual results: a very long boot time, see systemd-analyze blame report below Expected results: at least the same boot time like on my windows partition Additional info: 1min 5.010s systemd-udev-settle.service 7.699s systemd-cryptsetup@luks\x2d509163fe\x2d882c\x2d47f7\x2d9d8d\x2de4600c0e048b.service 6.884s dracut-initqueue.service 4.042s dnf-makecache.service 3.314s NetworkManager-wait-online.service 3.074s lvm2-monitor.service 2.243s smartd.service 1.442s systemd-tmpfiles-setup-dev.service 1.135s systemd-random-seed.service 998ms upower.service 886ms systemd-journald.service 869ms udisks2.service 756ms systemd-udev-trigger.service 695ms systemd-journal-flush.service 636ms initrd-switch-root.service 613ms systemd-logind.service 560ms firewalld.service 297ms sssd.service 250ms ModemManager.service 247ms systemd-homed.service 202ms systemd-udevd.service 194ms lvm2-pvscan@253:0.service 179ms abrtd.service 159ms systemd-userdbd.service 142ms dracut-pre-udev.service 121ms dracut-cmdline.service 121ms avahi-daemon.service 116ms rtkit-daemon.service 111ms user 101ms polkit.service 99ms dmraid-activation.service 97ms initrd-parse-etc.service 91ms dbus-broker.service 69ms NetworkManager.service 61ms systemd-fsck-root.service 50ms boot-efi.mount 49ms chronyd.service 46ms rsyslog.service 46ms dracut-pre-pivot.service 42ms systemd-fsck@dev-disk-by\x2duuid-62EB\x2d1CF3.service 41ms auditd.service 39ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service 37ms dracut-pre-trigger.service 35ms gssproxy.service 35ms systemd-tmpfiles-setup.service 34ms systemd-vconsole-setup.service 30ms systemd-fsck@dev-disk-by\x2duuid-8b61ffc1\x2d97be\x2d46b0\x2db390\x2d5bf5d6083af8.service 28ms plymouth-switch-root.service 26ms dev-mapper-fedora_localhost\x2d\x2dlive\x2dswap.swap 24ms plymouth-quit-wait.service 23ms plymouth-quit.service 21ms import-state.service 14ms home.mount 13ms plymouth-read-write.service 13ms sysroot.mount 12ms user-runtime-dir 12ms plymouth-start.service 11ms boot.mount 10ms systemd-repart.service 9ms systemd-sysctl.service 9ms livesys.service 9ms initrd-cleanup.service 8ms dev-hugepages.mount 8ms systemd-remount-fs.service 7ms dev-mqueue.mount
Why do you need/care about systemd-udev-settle.service? Using that service is not recommended.
this is a fresh install of fedora. i did not enable that service. i even dont know what that service is for. if this is enabled by default, but not needed (if its not recommended), then this is a bug. i used the lxqt spin of fedora 32.
Oh, OK. Two questions: 1. systemctl show -p RequiredBy,WantedBy systemd-udev-settle.service ? 2. Please attach the log: 'journalctl -b -o short-monotonic --no-hostname'
systemctl show -p RequiredBy,WantedBy systemd-udev-settle.service RequiredBy= WantedBy=multipathd.service dmraid-activation.service
Created attachment 1695410 [details] the log of journalctl -b -o short-monotonic --no-hostname
OK, it seems to be the same as the other bug. Thanks for the info. *** This bug has been marked as a duplicate of bug 1816885 ***