system-analyze blame
Codice: Seleziona tutto
6.502s NetworkManager-wait-online.service
597ms systemd-logind.service
571ms lightdm.service
568ms plymouth-quit-wait.service
424ms vboxdrv.service
361ms dev-nvme0n1p2.device
314ms systemd-journald.service
295ms upower.service
266ms blueman-mechanism.service
250ms systemd-resolved.service
213ms snapd.service
205ms systemd-timesyncd.service
197ms accounts-daemon.service
171ms udisks2.service
166ms systemd-backlight@leds:dell::kbd_backlight.service
163ms networkd-dispatcher.service
106ms apport-autoreport.service
100ms apparmor.service
98ms avahi-daemon.service
96ms systemd-udev-trigger.service
96ms polkit.service
95ms NetworkManager.service
90ms mnt-848AC14B8AC13A86.mount
82ms systemd-rfkill.service
76ms systemd-tmpfiles-setup.service
73ms systemd-udevd.service
73ms thermald.service
71ms apport.service
70ms wpa_supplicant.service
67ms ModemManager.service
67ms user@1000.service
65ms keyboard-setup.service
61ms grub-common.service
60ms console-setup.service
57ms plymouth-read-write.service
54ms dev-disk-by\x2duuid-5c366979\x2d6ac6\x2d40de\x2d8db0\x2d5a019a6172b6.swap
51ms gpu-manager.service
49ms secureboot-db.service
49ms alsa-restore.service
44ms lm-sensors.service
34ms grub-initrd-fallback.service
33ms e2scrub_reap.service
32ms rsyslog.service
25ms systemd-modules-load.service
21ms pppd-dns.service
20ms systemd-user-sessions.service
17ms plymouth-start.service
16ms systemd-backlight@backlight:intel_backlight.service
15ms modprobe@drm.service
15ms kerneloops.service
13ms systemd-sysctl.service
13ms snapd.seeded.service
12ms setvtrgb.service
12ms hddtemp.service
12ms colord.service
11ms systemd-tmpfiles-setup-dev.service
11ms systemd-remount-fs.service
10ms systemd-sysusers.service
10ms systemd-random-seed.service
9ms systemd-update-utmp.service
9ms snapd.apparmor.service
8ms dev-hugepages.mount
8ms dev-mqueue.mount
8ms sys-kernel-debug.mount
8ms sys-kernel-tracing.mount
8ms kmod-static-nodes.service
7ms user-runtime-dir@1000.service
6ms systemd-journal-flush.service
6ms systemd-update-utmp-runlevel.service
6ms ufw.service
5ms vboxweb-service.service
3ms vboxballoonctrl-service.service
3ms rtkit-daemon.service
3ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
3ms vboxautostart-service.service
678us snapd.socket
systemd-analyze
Codice: Seleziona tutto
Startup finished in 8.450s (firmware) + 4.366s (loader) + 3.097s (kernel) + 1min 37.544s (userspace) = 1min 53.458s
graphical.target reached after 1min 37.448s in userspace
systemd-analyze critical-chain
Codice: Seleziona tutto
graphical.target @1min 37.448s
└─multi-user.target @1min 37.448s
└─kerneloops.service @1min 37.433s +15ms
└─network-online.target @1min 37.430s
└─NetworkManager-wait-online.service @1min 30.928s +6.502s
└─NetworkManager.service @1min 30.831s +95ms
└─dbus.service @1min 30.829s
└─basic.target @1min 30.818s
└─sockets.target @1min 30.817s
└─snapd.socket @1min 30.816s +678us
└─sysinit.target @1min 30.811s
└─systemd-timesyncd.service @1min 30.605s +205ms
└─systemd-tmpfiles-setup.service @1min 30.527s +76ms
└─systemd-journal-flush.service @641ms +6ms
└─systemd-journald.service @325ms +314ms
└─systemd-journald.socket @322ms
└─system.slice @320ms
└─-.slice @320ms
Il problema sembrerebbe essere il serivizio "systemd-journal-flush.service".
Ho forzato il mask ma il problema persiste. Nell'albero compare "systemd-journal.service" con 90 secondi di esecuzione al posto del servizio precedente.
in realtà questi processi mi sembrano essere a posto, /var/log/journal è vuota , e ho dato i comandi di questa guida :
https://askubuntu.com/questions/10943 ... e/1095784
Ho cosi forzato il mask anche di questo e nell'abero. Il problema continua e al posto di "systemd-journal.service" compare "systemd-sysusers.service" con 90 secondi di esecuzione.
Non voglio fare il mask di quest'ultimo perche mi sembra essenziale come servizio.
Ho cercato in giro ma non ne sono venuto a capo.
Attualmente ho ripristintao i servizi disabilati.
Ho due hard disk , uno con win10 e l'altro con Xubnutu 20 e caelinux 2018 ( xubuntu 16.04). Una swap sul secondo disco.