[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)