Долгая загрузка Ubuntu 20.04.2 LTS
Всем доброго времени суток! С недавнего времени Ubuntu 20.04.2(focal) стала долго загружаться. Помогите разобраться в чём причина и как это пофиксить. Заранее всем спасибо! Вот выхлоп:
systemd-analyze blame43.454s nmbd.service
23.780s man-db.service
17.484s dev-sda6.device
15.888s systemd-journal-flush.service
11.161s udisks2.service
9.807s fwupd.service
8.505s dev-loop0.device
8.380s dev-loop6.device
8.315s dev-loop1.device
7.986s dev-loop2.device
7.978s dev-loop7.device
7.608s dev-loop5.device
7.511s logrotate.service
7.465s dev-loop11.device
7.411s dev-loop8.device
6.837s dev-loop4.device
6.836s dev-loop3.device
6.747s dev-loop9.device
6.676s dev-loop10.device
6.597s NetworkManager.service
6.578s networkd-dispatcher.service
6.468s snapd.service
5.293s apparmor.service
5.189s bolt.service
4.279s systemd-udevd.service
3.640s accounts-daemon.service
3.470s networking.service
3.469s snapd.apparmor.service
2.425s polkit.service
2.278s avahi-daemon.service
2.088s switcheroo-control.service
2.078s wpa_supplicant.service
2.072s thermald.service
2.071s systemd-logind.service
2.070s ModemManager.service
1.662s systemd-resolved.service
1.448s gpu-manager.service
1.346s colord.service
1.293s binfmt-support.service
1.149s systemd-tmpfiles-setup-dev.service
1.088s systemd-modules-load.service
867ms systemd-sysusers.service
802ms systemd-tmpfiles-setup.service
798ms rc.local.service
767ms apport.service
747ms grub-initrd-fallback.service
711ms snap-chromium-1479.mount
709ms setserial.service
696ms snap-chromium-1497.mount
693ms grub-common.service
676ms etc-setserial.service
669ms systemd-random-seed.service
647ms lm-sensors.service
579ms systemd-sysctl.service
577ms rsyslog.service
553ms apt-daily-upgrade.service
540ms snap-core-10583.mount
538ms snap-core-10823.mount
534ms systemd-timesyncd.service
520ms lightdm.service
517ms keyboard-setup.service
511ms plymouth-quit-wait.service
499ms snap-core18-1944.mount
491ms snap-core18-1988.mount
477ms upower.service
472ms virtualbox.service
472ms console-setup.service
411ms snap-gtk\x2dcommon\x2dthemes-1474.mount
325ms snap-jdownloader2-13.mount
302ms systemd-udev-trigger.service
302ms snap-gnome\x2d3\x2d28\x2d1804-145.mount
266ms snap-gtk\x2dcommon\x2dthemes-1514.mount
240ms aumix.service
235ms setvtrgb.service
230ms snap-hello\x2dworld-29.mount
212ms kerneloops.service
202ms systemd-remount-fs.service
183ms snap-hello\x2dworld-27.mount
175ms ufw.service
140ms systemd-update-utmp.service
136ms snapd.seeded.service
135ms systemd-journald.service
134ms smbd.service
128ms dev-hugepages.mount
127ms dev-mqueue.mount
126ms sys-kernel-debug.mount
126ms sys-kernel-tracing.mount
124ms kmod-static-nodes.service
123ms e2scrub_reap.service
116ms winbind.service
112ms ifupdown-pre.service
111ms proc-sys-fs-binfmt_misc.mount
111ms dns-clean.service
102ms user@1000.service
46ms hddtemp.service
36ms resolvconf-pull-resolved.service
29ms gdm3.service
26ms pppd-dns.service
22ms openvpn.service
22ms systemd-update-utmp-runlevel.service
22ms systemd-user-sessions.service
18ms user-runtime-dir@1000.service
14ms plymouth-start.service
11ms rtkit-daemon.service
11ms plymouth-read-write.service
9ms alsa-restore.service
8ms systemd-tmpfiles-clean.service
7ms ureadahead-stop.service
3ms sys-fs-fuse-connections.mount
2ms sys-kernel-config.mount
589us snapd.socket Также еще вот
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 @2min 24.507s
└─multi-user.target @2min 24.507s
└─smbd.service @2min 24.371s +134ms
└─winbind.service @2min 24.253s +116ms
└─nmbd.service @1min 40.794s +43.454s
└─network-online.target @1min 40.781s
└─network.target @1min 40.781s
└─NetworkManager.service @1min 34.183s +6.597s
└─dbus.service @1min 34.179s
└─basic.target @1min 34.035s
└─sockets.target @1min 34.035s
└─snapd.socket @1min 34.034s +589us
└─sysinit.target @1min 33.952s
└─systemd-timesyncd.service @20.994s +534ms
└─systemd-tmpfiles-setup.service @20.101s +802ms
└─systemd-journal-flush.service @4.211s +15.888s
└─systemd-remount-fs.service @3.953s +202ms
└─systemd-journald.socket @3.828s
└─system.slice @3.808s
└─-.slice @3.808s
