Boot lento di Ubuntu 24.10

Compilazione del kernel, gestione moduli, servizi attivi, e tutti gli interventi per l'ottimizzazione del sistema operativo.
Scrivi risposta
ivan p
Scoppiettante Seguace
Scoppiettante Seguace
Messaggi: 564
Iscrizione: lunedì 2 giugno 2008, 12:05

Boot lento di Ubuntu 24.10

Messaggio da ivan p »

Salve.

Prima il notebook si avviava in circa 30 s. Non so se possa centrare ma dopo aver installato affianco win10 il boot è lento. Qualche volta ottengo pure un messaggio di errore e non si avvia e devo riavviare. Non so se centri ma se provo ad avviare win10 dal grub ricevo un errore e non si avvia. Leggendo altri post non ho trovato la soluzione ma ho capito che l eseguenti info potrebbero essere utili.

Codice: Seleziona tutto

systemd-analyze blame
13.051s apport-autoreport.service
 7.552s NetworkManager-wait-online.service
 3.456s plymouth-quit-wait.service
 2.556s fwupd.service
 1.502s snapd.seeded.service
 1.364s NetworkManager.service
  964ms boot-efi.mount
  955ms home.mount
  943ms snap-bare-5.mount
  933ms snap-core22-1621.mount
  898ms snapd.service
  830ms snap-desktop\x2dsecurity\x2dcenter-32.mount
  828ms snap-firefox-5091.mount
  818ms apport.service
  810ms snap-firefox-5187.mount
  650ms dev-nvme0n1p4.device
  644ms snap-firmware\x2dupdater-127.mount
  579ms udisks2.service
  540ms polkit.service
  507ms accounts-daemon.service
  500ms gnome-remote-desktop-configuration.service
  465ms gnome-remote-desktop.service
  437ms secureboot-db.service
  422ms gpu-manager.service
  388ms upower.service
  384ms systemd-udev-trigger.service
  359ms apparmor.service
  357ms systemd-logind.service
  339ms user@1000.service
  332ms grub-common.service
  314ms bluetooth.service
  306ms thermald.service
  297ms avahi-daemon.service
  257ms sysstat.service
  247ms snapd.apparmor.service
  241ms systemd-resolved.service
  213ms systemd-timesyncd.service
  203ms dev-loop12.device
  197ms keyboard-setup.service
  196ms dev-loop7.device
  196ms dev-loop11.device
  196ms dev-loop13.device
  196ms dev-loop16.device
  195ms dev-loop10.device
  195ms systemd-oomd.service
  190ms dev-loop14.device
  190ms dev-loop15.device
  189ms dev-loop9.device
  188ms dev-loop6.device
  187ms dev-loop2.device
  184ms dev-loop8.device
  184ms ModemManager.service
  182ms dev-loop5.device
  182ms dev-loop4.device
  182ms switcheroo-control.service
  179ms update-notifier-download.service
  177ms dev-loop3.device
  175ms dev-loop1.device
  167ms systemd-fsck@dev-disk-by\x2duuid-757f254f\x2d7fe8\x2d49ce\x2dbae9\x2dfa>
  161ms snap-firmware\x2dupdater-147.mount
  157ms systemd-udevd.service
  157ms e2scrub_reap.service
  155ms dev-loop0.device
  155ms snap-gnome\x2d42\x2d2204-176.mount
  153ms dbus.service
  150ms snap-gtk\x2dcommon\x2dthemes-1535.mount
  149ms systemd-journald.service
  148ms snap-gtk\x2dcommon\x2dthemes-1536.mount
  143ms snap-prompting\x2dclient-51.mount
  137ms kdump-tools.service
  133ms snap-snap\x2dstore-1218.mount
  127ms grub-initrd-fallback.service
  127ms alsa-restore.service
  126ms snap-snapd-21759.mount
  118ms snap-snapd\x2ddesktop\x2dintegration-247.mount
  111ms gdm.service
  109ms systemd-hostnamed.service
  109ms snap-snapd\x2ddesktop\x2dintegration-253.mount
   99ms systemd-journal-flush.service
   97ms systemd-binfmt.service
   89ms colord.service
   86ms systemd-fsck@dev-disk-by\x2duuid-82D2\x2d7AE2.service
   86ms snap-thunderbird-526.mount
   76ms systemd-modules-load.service
   74ms snap-thunderbird-546.mount
   73ms power-profiles-daemon.service
   67ms dev-hugepages.mount
   67ms wpa_supplicant.service
   66ms dev-mqueue.mount
   66ms plymouth-start.service
   65ms systemd-tmpfiles-setup.service
   65ms run-lock.mount
   65ms packagekit.service
   62ms systemd-tmpfiles-setup-dev-early.service
   61ms sys-kernel-debug.mount
   60ms openvpn.service
   60ms systemd-sysctl.service
   57ms sys-kernel-tracing.mount
   56ms systemd-user-sessions.service
   55ms systemd-random-seed.service
   54ms sysstat-collect.service
   53ms kmod-static-nodes.service
   51ms systemd-remount-fs.service
   51ms modprobe@configfs.service
   48ms modprobe@drm.service
   47ms systemd-udev-load-credentials.service
   44ms systemd-update-utmp.service
   41ms rtkit-daemon.service
   39ms proc-sys-fs-binfmt_misc.mount
   37ms modprobe@fuse.service
   36ms systemd-backlight@leds:dell::kbd_backlight.service
   34ms swap.img.swap
   33ms sys-kernel-config.mount
   33ms systemd-tmpfiles-setup-dev.service
   32ms console-setup.service
   30ms setvtrgb.service
   28ms tmp.mount
   28ms plymouth-read-write.service
   23ms user-runtime-dir@1000.service
   20ms systemd-update-utmp-runlevel.service
   19ms sys-fs-fuse-connections.mount
   18ms systemd-backlight@backlight:intel_backlight.service
   17ms modprobe@efi_pstore.service
   17ms systemd-rfkill.service
   12ms ufw.service
   10ms snapd.socket

Codice: Seleziona tutto

systemd-analyze
Startup finished in 14.439s (firmware) + 7.177s (loader) + 2.411s (kernel) + 1min 40.571s (userspace) = 2min 4.600s

Codice: Seleziona tutto

systemd-analyze critical-chain --no-pager
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 40.547s
└─power-profiles-daemon.service @1min 40.472s +73ms
  └─multi-user.target @1min 40.466s
    └─plymouth-quit-wait.service @1min 32.985s +3.456s
      └─systemd-user-sessions.service @1min 32.917s +56ms
        └─network.target @1min 32.905s
          └─NetworkManager.service @1min 31.540s +1.364s
            └─dbus.service @1min 31.249s +153ms
              └─basic.target @1min 31.216s
                └─sockets.target @1min 31.216s
                  └─snapd.socket @1min 31.205s +10ms
                    └─sysinit.target @1min 31.199s
                      └─snapd.apparmor.service @1min 30.950s +247ms
                        └─apparmor.service @1min 30.588s +359ms
                          └─systemd-sysctl.service @492ms +60ms
                            └─run-credentials-systemd\x2dsysctl.service.mount @508ms
Grazie.
Scrivi risposta

Ritorna a “Kernel e servizi di sistema”

Chi c’è in linea

Visualizzano questa sezione: 0 utenti iscritti e 4 ospiti