LINUX.ORG.RU

Xubuntu 24.04 долго грузится (6-8 минут)

 


0

1

Xubuntu (xubuntu-24.04-desktop-amd64) пользуюсь недавно. Возникла проблема в загрузке ОС. Долго грузится 6-8 минут. Сама система работает нормально. Быстро отвечать не смогу, но обязательно отвечу.

Vsevolod-linuxoid тебе дело говорит, делай

потом открой терминал и дай команду
systemd-analyze plot > Desktop/boot_analysis.svg

на рабочем столе появится файл boot_analysis.svg
открой его в firefox’e и найди самую длинную красную стрелку

d00fy ★★★
()
Ответ на: комментарий от Vsevolod-linuxoid
11.353s gpu-manager.service
 6.473s plymouth-quit-wait.service
 4.528s logrotate.service
 4.371s snapd.seeded.service
 4.329s apt-daily-upgrade.service
 4.201s dev-sda1.device
 3.711s dev-loop12.device
 3.707s dev-loop13.device
 3.699s dev-loop10.device
 3.685s dev-loop9.device
 3.685s dev-loop11.device
 3.660s dev-loop14.device
 3.647s NetworkManager.service
 3.640s dev-loop8.device
 3.139s NetworkManager-wait-online.service
 2.154s snapd.service
 2.018s blueman-mechanism.service
 1.939s accounts-daemon.service
 1.801s apport.service
 1.630s alsa-restore.service
 1.431s avahi-daemon.service
 1.388s polkit.service
 1.380s udisks2.service
lines 1-23...skipping...
11.353s gpu-manager.service
 6.473s plymouth-quit-wait.service
 4.528s logrotate.service
 4.371s snapd.seeded.service
 4.329s apt-daily-upgrade.service
 4.201s dev-sda1.device
 3.711s dev-loop12.device
 3.707s dev-loop13.device
 3.699s dev-loop10.device
 3.685s dev-loop9.device
 3.685s dev-loop11.device
 3.660s dev-loop14.device
 3.647s NetworkManager.service
 3.640s dev-loop8.device
 3.139s NetworkManager-wait-online.service
 2.154s snapd.service
 2.018s blueman-mechanism.service
 1.939s accounts-daemon.service
 1.801s apport.service
 1.630s alsa-restore.service
 1.431s avahi-daemon.service
 1.388s polkit.service
 1.380s udisks2.service
 1.300s rsyslog.service
 1.280s fwupd-refresh.service
  995ms grub-common.service
  905ms dev-loop2.device
  889ms dev-loop1.device
  883ms lm-sensors.service
  858ms dev-loop6.device
  828ms dev-loop4.device
  805ms dev-loop0.device
  805ms dev-loop7.device
  805ms dev-loop5.device
  797ms fwupd.service
  796ms switcheroo-control.service
  785ms dev-loop3.device
  784ms dbus.service
  764ms apparmor.service
boris54
() автор топика
Ответ на: комментарий от rupert
11.387s gpu-manager.service
 6.454s plymouth-quit-wait.service
 4.053s NetworkManager.service
 3.635s dev-loop13.device
 3.628s dev-loop11.device
 3.607s dev-loop9.device
 3.606s dev-loop14.device
 3.567s dev-loop12.device
 3.551s dev-loop10.device
 3.485s dev-loop8.device
 3.124s NetworkManager-wait-online.service
 2.960s snapd.seeded.service
 2.898s dev-sda1.device
 2.308s blueman-mechanism.service
 2.184s snapd.service
 1.965s accounts-daemon.service
 1.873s rsyslog.service
 1.783s apport.service
 1.695s udisks2.service
 1.330s polkit.service
 1.158s avahi-daemon.service
  808ms dev-loop1.device
  781ms grub-common.service

три минуты 53 секунды

boris54
() автор топика
Ответ на: комментарий от boris54

Там ничего не понятно. Лучше сделай так:

$ systemd-analyze      
Startup finished in 14.089s (firmware) + 7.074s (loader) + 2.703s (kernel) + 5.090s (initrd) + 8.677s (userspace) = 37.634s 
graphical.target reached after 8.490s in userspace.

$ 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 @8.490s
└─multi-user.target @8.490s
  └─plymouth-quit-wait.service @3.833s +4.655s
    └─systemd-user-sessions.service @3.800s +15ms
      └─remote-fs.target @3.795s
        └─remote-fs-pre.target @3.795s
          └─nfs-client.target @3.795s
            └─gssproxy.service @3.741s +52ms
              └─network.target @3.737s
                └─wpa_supplicant.service @3.725s +11ms
                  └─basic.target @1.844s
                    └─dbus-broker.service @1.817s +24ms
                      └─dbus.socket @1.796s
                        └─sysinit.target @1.793s
                          └─systemd-resolved.service @1.525s +267ms
                            └─systemd-tmpfiles-setup.service @1.193s +301ms
                              └─local-fs.target @1.165s
                                └─run-user-1000.mount @2.238s
                                  └─swap.target @905ms
                                    └─dev-zram0.swap @730ms +78ms
                                      └─systemd-zram-setup@zram0.service @638ms +65ms
                                        └─dev-zram0.device @620ms
rupert ★★★★★
()

4 минуты 22 секунды

11.763s gpu-manager.service
 6.638s plymouth-quit-wait.service
 4.889s dev-loop12.device
 4.874s dev-loop14.device
 4.687s dev-loop15.device
 4.678s dev-loop13.device
 4.671s dev-loop11.device
 4.632s snapd.seeded.service
 4.630s dev-loop10.device
 4.618s dev-loop9.device
 4.215s NetworkManager.service
 4.111s dev-loop8.device
 3.389s NetworkManager-wait-online.service
 2.492s dev-sda1.device
 2.419s systemd-rfkill.service
 1.982s snapd.service
 1.651s blueman-mechanism.service
 1.644s apport.service
 1.551s accounts-daemon.service
 1.294s udisks2.service
 1.255s polkit.service
 1.142s rsyslog.service
 1.089s avahi-daemon.service
boris54
() автор топика
Ответ на: комментарий от rupert
$ systemd-analyze
Startup finished in 4.509s (kernel) + 15.317s (userspace) = 19.827s 
graphical.target reached after 15.264s in userspace.

$ 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 @15.264s
└─multi-user.target @15.264s
  └─getty.target @15.264s
    └─getty@tty1.service @15.261s
      └─system-getty.slice @15.252s
        └─setvtrgb.service @15.234s +14ms
          └─plymouth-quit-wait.service @8.585s +6.638s
            └─systemd-user-sessions.service @8.468s +82ms
              └─network.target @8.353s
                └─NetworkManager.service @4.128s +4.215s
                  └─dbus.service @3.235s +516ms
                    └─basic.target @3.104s
                      └─sockets.target @3.104s
                        └─snapd.socket @3.096s +7ms
                          └─sysinit.target @3.080s
                            └─systemd-backlight@backlight:acpi_video0.service @>
                              └─system-systemd\x2dbacklight.slice @8.150s
                                └─system.slice @492ms
                                  └─-.slice @493ms
lines 1-22/22 (END)
boris54
() автор топика

Твоя хубунта у меня, когда-то с флешки загрузочной (liveusb) загружалась минуты 3-4. Давно ещё понял, что с этой сборкой что-то не так…

temak
()