Home / ubuntu / Questions / 1300221
In Process
2new
Asked: 2020-12-15 23:51:49 +0800 CST

Slow boot time on Ubuntu 20.04.1 LTS

  • 772

I've just installed Ubuntu on a new build PC and I'm consistently experiencing long boot times of well over 2 minutes. I saw a lot of advice to use systemd-analyze, but wasn't sure how to interpret it for my situation. I've included the output of systemd-analyze and systemd-analyze critical-chain, below. Any help greatly appreciated.

$ systemd-analyze
Startup finished in 7.372s (firmware) + 5.319s (loader) + 3.706s (kernel) + 2min 22.911s (userspace) = 2min 39.309s 

$ 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 22.683s
└─multi-user.target @2min 22.683s
  └─snapd.seeded.service @1min 17.297s +497ms
    └─snapd.service @32.501s +44.790s
      └─basic.target @32.359s
        └─sockets.target @32.359s
          └─snapd.socket @32.358s +662us
            └─sysinit.target @32.251s
              └─systemd-timesyncd.service @31.837s +414ms
                └─systemd-tmpfiles-setup.service @30.880s +915ms
                  └─systemd-journal-flush.service @4.100s +26.779s
                    └─systemd-remount-fs.service @3.866s +165ms
                      └─systemd-journald.socket @3.526s
                        └─system.slice @3.524s
                          └─-.slice @3.524s

-----Edit----- Hardware Specs:

  • Processor: Intel Core i7-6700K 4 GHz Quad-Core
  • CPU Cooler: Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing
  • Motherboard: Asus B150M-C Micro ATX LGA1151
  • Memory: Corsair Vengeance RGB Pro 32 GB (2 x 16 GB) DDR4-3200 CL16
  • Storage: Seagate BarraCuda 4 TB 2.5" 5400RPM Internal HDD
  • Power supply: be quiet! System Power 9 600 W 80+ Bronze Certified ATX

-----Edit 2----- Output of systemd-anaylze critical-chain after running sudo apt autoremove --purge snapd and sudo reboot.

$ 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 @1min 30.725s
└─multi-user.target @1min 30.725s
  └─kerneloops.service @1min 396ms +66ms
    └─network-online.target @1min 389ms
      └─NetworkManager-wait-online.service @47.348s +13.040s
        └─NetworkManager.service @38.520s +8.823s
          └─dbus.service @38.517s
            └─basic.target @38.479s
              └─sockets.target @38.479s
                └─uuidd.socket @38.479s
                  └─sysinit.target @38.465s
                    └─systemd-timesyncd.service @38.109s +356ms
                      └─systemd-tmpfiles-setup.service @37.043s +1.028s
                        └─systemd-journal-flush.service @4.294s +32.747s
                          └─systemd-journald.service @3.840s +453ms
                            └─systemd-journald.socket @3.837s
                              └─-.mount @3.835s
                                └─system.slice @3.835s
                                  └─-.slice @3.835s
systemd boot-time 20.04

0 Answers