Ubuntu загружается за 1 минуту 25 секунд
вот так выглядит журнал критической цепи systemd-analyze
graphical.target @ 1 мин 20,643 с
ââmulti-user.target @1min 20.643s
ââsnapd.seeded.service @1min 10.553s +37ms
ââsnapd.service @38.570s +31.978s
ââbasic.target @37.598s
ââsockets.target @37.598s
ââsnapd.socket @37.595s +2ms
ââsysinit.target @37.433s
ââsnapd.apparmor.service @36.725s +706ms
ââapparmor.service @34,732 с +1,989 с
ââlocal-fs.target @34.729s
ââboot-efi.mount @ 34,644 с + 84 мс
ââsystemd-fsck@dev-disk-by\x2duuid-9CF8\x2dBDA7.service @>
ââdev-disk-by\x2duuid-9CF8\x2dBDA7.device @32.121s
Лог systemd-analyze выглядит так
32.976s plymouth-quit-wait.service >
31.978s snapd.service >
28.705s udisks2.service >
26.038s dev-sda8.device >
13.347s учетные записи-daemon.service >
12.292s NetworkManager-wait-online.service >
11.534s dev-loop7.device >
11.211s dev-loop8.device >
10.921s dev-loop3.device >
10.733s dev-loop2.device >
10.451s dev-loop5.device >
9.934s dev-loop9.device >
9.686s dev-loop4.device >
9.532s NetworkManager.service >
9.332s avahi-daemon.service >
9.326s bluetooth.сервис >
9.326s dev-loop0.device >
9.057s dev-loop6.device >
8.898s polkit.service >
8.468s switcheroo-control.service >
8.451s термический сервис >
8.447s systemd-logind.service >
8.232s wpa_supplicant.service >
8.027s dev-loop1.device >
6.343s systemd-resolved.service >
5.664s systemd-udevd.service >
4.572s gpu-manager.service >
4.227s mono-xsp4.service >
4.138s аппорт.сервис >
4.019s ModemManager.service >
3.765s secureboot-db.service >
3.580s gdm.service >
3.345s e2scrub_reap.service >
3.322s rc.local.service >
2.942s grub-common.service >
2.495s systemd-fsck@dev-disk-by\x2duuid-9CF8\x2dBDA7.service >
2.214s сетевой.сервис >
2.060s systemd-modules-load.service >
1.989s apparmor.service >
1.693s systemd-tmpfiles-setup-dev.service >
1.663s клавиатура-настройка.сервис >
1.609s systemd-sysusers.service >
1.599s grub-initrd-fallback.service >
1.303s lm-sensors.service >
1.263s rsyslog.service >
1.203s plymouth-start.service >
1.136s [email protected] >
1.098s systemd-random-seed.service >
1.048s resolvconf-pull-resolved.service >
1.028s systemd-udev-trigger.service >
1.016s systemd-sysctl.service >
855ms systemd-tmpfiles-setup.service >
792ms ufw.service >
706 мс snapd.apparmor.service >
698 мс snap-core18-2074.mount >
695 мс snap-wine\x2dplatform\x2d6\x2dstable-5.mount >
642 мс snap-wine\x2dplatform\x2d6\x2dstable-8.mount >
641 мс dns-clean.service >
634 мс binfmt-support.service >
611 мс snap-wine\x2dplatform\x2druntime-240.mount >
592 мс snap-snapd-12704.mount >
557 мс pppd-dns.service >
542 мс kerneloops.service >
522 мс snap-snapd-12883.mount >
506 мс systemd-backlight@backlight:intel_backlight.service >
497 мс
459 мс hddtemp.service >
401 мс snap-wine\x2dplatform\x2druntime-239.mount >
400 мс snap-core18-2128.mount >
396 мс openvpn.service >
375 мс systemd-timesyncd.service >
352 мс dev-hugepages.mount >
351ms dev-mqueue.mount >
351ms sys-kernel-debug.mount >
350 мс sys-kernel-tracing.mount >
348ms systemd-journald.service >
348 мс kmod-static-nodes.service >
336 мс console-setup.service >
316 мс systemd-remount-fs.service >
303 мс packagekit.service >
282 мс upower.service >
269 мс snap-gtk\x2dcommon\x2dthemes-1515.mount >
252 мс tlp.service >
210 мс snap-gnome\x2d3\x2d28\x2d1804-161.mount >
200 мс plymouth-read-write.service >
188 мс пользователь@1000.service >
179 мс systemd-update-utmp.service >
172ms dev-disk-by\x2duuid-fd7235f1\x2d1d46\x2d4b9e\x2da017\x2dd9d72c3566b2.sw>
130 мс proc-sys-fs-binfmt_misc.mount >
94ms systemd-user-sessions.service >
84 мс загрузочный-efi.mount >
76ms colord.service >
54ms systemd-journal-flush.service >
52 мс setvtrgb.service >
37 мс snapd.seeded.service >
34 мс [email protected] >
32 мс systemd-update-utmp-runlevel.service >
14 мс alsa-restore.service >
13 мс ureadahead-stop.service >
10 мс rtkit-daemon.service >
2ms sys-fs-fuse-connections.mount >
2 мс snapd.socket >
1 мс sys-kernel-config.mount >
Изменить 1
После отключения NetworkManager-wait-online.service и snapd.service
Журнал критической цепочки systemd-analyze выглядит так
graphical.target @ 1 мин 19,553 с
ââmulti-user.target @1min 19.553s
ââsnapd.seeded.service @37.019s +32.434s
ââsnapd.service @37.813s +31.624s
ââbasic.target @ 36.069s
ââsockets.target @ 36.069s
ââsnapd.socket @36.069s +554us
ââsysinit.target @35.888s
ââsnapd.apparmor.service @34.888s +999ms
ââapparmor.service @33.060s +1.825s
ââlocal-fs.target @33.060s
ââboot-efi.mount @ 32,970 с + 89 мс
ââsystemd-fsck@dev-disk-by\x2duuid-9CF8\x2dBDA7.service @>
ââdev-disk-by\x2duuid-9CF8\x2dBDA7.device @30.385s
systemd-analyze виноват выглядит так
32.742s plymouth-quit-wait.service >
32.434s snapd.seed.service >
31.624s snapd.service >
24.802s dev-sda8.device >
22.646s udisks2.service >
13.990s account-daemon.service >
10.964s dev-loop1.device >
10.335s NetworkManager.service >
10.306s dev-loop4.device >
10.121s dev-loop8.device >
10.065s dev-loop9.device >
10.023s dev-loop7.device >
10.012s dev-loop5.device >
9.480s avahi-daemon.service >
9.468s bluetooth.сервис >
9.449s dev-loop0.device >
9.095s polkit.service >
8.814s dev-loop3.device >
8.707s switcheroo-control.service >
8.696s термическая служба >
8.684s systemd-logind.service >
8.630s wpa_supplicant.service >
8.422s dev-loop2.device >
7.155s dev-loop6.device >
5.716s systemd-udevd.service >
4.381s gpu-manager.service >
4.302s ModemManager.service >
3.050s mono-xsp4.service >
3.026s secureboot-db.service >
2.992s systemd-resolved.service >
2.970s аппорт.сервис >
2.861s e2scrub_reap.service >
2.761s rsyslog.service >
2.610s resolvconf-pull-resolved.service >
2.546s systemd-fsck@dev-disk-by\x2duuid-9CF8\x2dBDA7.service >
2.464s grub-common.service >
2.204s сетевой.сервис >
2.076s plymouth-start.service >
1.915s systemd-modules-load.service >
1.825s apparmor.service >
1.781s gdm.service >
1.679s systemd-tmpfiles-setup-dev.service >
1.668s systemd-sysusers.service >
1.500s lm-sensors.service >
1.407s snap-gnome\x2d3\x2d28\x2d1804-161.mount >
1.283s grub-initrd-fallback.service >
1.205s snap-wine\x2dplatform\x2d6\x2dstable-5.mount >
1.170s rc.local.service >
1.059s клавиатура-настройка.сервис >
1.058s [email protected] >
1.046s systemd-sysctl.service >
1.031s snap-gtk\x2dcommon\x2dthemes-1515.mount >
999 мс snapd.apparmor.service >
952 мс snap-core18-2074.mount >
923ms snap-snapd-12883.mount >
869 мс snap-wine\x2dplatform\x2druntime-239.mount >
837ms systemd-random-seed.service >
805 мс binfmt-support.service >
799 мс pppd-dns.service >
790 мс systemd-tmpfiles-setup.service>
646ms systemd-udev-trigger.service >
601 мс snap-snapd-12704.mount >
594 мс tlp.service >
592ms ufw.service >
591 мс hddtemp.service >
569 мс packagekit.service >
534 мс kerneloops.service >
525 мс snap-wine\x2dplatform\x2d6\x2dstable-8.mount >
474 мс dev-hugepages.mount >
474 мс dev-mqueue.mount >
473 мс sys-kernel-debug.mount >
473 мс sys-kernel-tracing.mount >
471 мс systemd-journald.service >
470 мс kmod-static-nodes.service >
408 мс systemd-remount-fs.service >
405 мс snap-wine\x2dplatform\x2druntime-240.mount >
388 мс snap-core18-2128.mount >
378ms dev-disk-by\x2duuid-fd7235f1\x2d1d46\x2d4b9e\x2da017\x2dd9d72c3566b2.sw>
374 мс systemd-timesyncd.service >
372 мс
345 мс systemd-backlight@backlight:intel_backlight.service >
308 мс console-setup.service >
298ms systemd-journal-flush.service >
253 мс upower.service >
197 мс systemd-update-utmp.service >
186 мс пользователь@1000.service >
185 мс dns-clean.service >
178ms colord.service >
95 мс plymouth-read-write.service >
89 мс загрузочный-efi.mount >
85 мс openvpn.service >
84ms systemd-user-sessions.service >
54 мс proc-sys-fs-binfmt_misc.mount >
43 мс geoclue.service >
33 мс setvtrgb.service >
22ms realmd.service >
21 мс [email protected] >
16 мс ureadahead-stop.service >
12 мс alsa-restore.service >
8ms systemd-update-utmp-runlevel.service >
5 мс rtkit-daemon.service >
2ms sys-fs-fuse-connections.mount >
2ms sys-kernel-config.mount >
554us snapd.socket >
Редактировать 2
после запуска этих команд
sudo systemctl stop snapd.service и sudo systemctl mask snapd.service
журналы выглядят так
graphical.target @ 1 мин 16,891 с
ââmulti-user.target @1min 16.891s
ââModemManager.service @45.278s +5.350s
ââpolkit.service @38.513s +6.761s
ââbasic.target @37.579s
ââsockets.target @37.579s
ââuuidd.socket @37.579s
ââsysinit.target @37.512s
ââsnapd.apparmor.service @36.546s +965ms
ââapparmor.service @33.786s +2.759s
ââlocal-fs.target @33.785s
ââboot-efi.mount @ 33.701 с + 83 мс
ââsystemd-fsck@dev-disk-by\x2duuid-9CF8\x2dBDA7.service @>
ââdev-disk-by\x2duuid-9CF8\x2dBDA7.device @31.041s
31.507s plymouth-quit-wait.service >
25.108s dev-sda8.device >
23.215s udisks2.service >
11.035s dev-loop6.device >
10.919s dev-loop7.device >
10.632s dev-loop1.device >
10.555s учетные записи-daemon.service >
10.166s dev-loop5.device >
10.163s dev-loop4.device >
9.656s dev-loop3.device >
9.646s dev-loop8.device >
9.570s dev-loop0.device >
9.545s dev-loop9.device >
9.411s dev-loop2.device >
7.520s avahi-daemon.service >
7.518s bluetooth.сервис >
7.224s NetworkManager.service >
6.761s polkit.service >
6.657s switcheroo-control.service >
6.651s термический сервис >
6.649s systemd-logind.service >
6.432s wpa_supplicant.service >
