This is an automated archive.

The original was posted on /r/debian by /u/Rikki_Codes on 2023-08-07 13:22:37+00:00.

I’m running my machine on Debian 12 XFCE (dual boot with windows 10, though I rarely boot into windows) on an old machine. The boot time isn’t thaaat bad but it feels like the userspace part takes a bit too long.

When I run systemd-analyze time I get:

Startup finished in 3.847s (firmware) + 2.990s (loader) + 7.574s (kernel) + 38.557s (userspace) = 52.970s 
graphical.target reached after 38.517s in userspace.

The systemd-analyze critical-chain command gives the following output:

And the command systemd-analyze blame gives:

21.211s e2scrub_reap.service
11.032s dev-sda5.device
 9.418s snapd.service
 8.583s udisks2.service
 8.478s NetworkManager-wait-online.service
 6.484s snapd.seeded.service
 6.241s accounts-daemon.service
 5.453s power-profiles-daemon.service
 5.372s polkit.service
 5.280s NetworkManager.service
 5.093s ModemManager.service
 4.948s systemd-journal-flush.service
 4.705s apache2.service
 4.653s avahi-daemon.service
 4.651s bluetooth.service
 4.595s dbus.service
 4.383s switcheroo-control.service
 4.382s smartmontools.service
 4.372s systemd-logind.service
 3.923s lvm2-monitor.service
 2.991s keyboard-setup.service
 2.684s systemd-modules-load.service
 2.496s cups.service
 2.409s networking.service
 2.247s wpa_supplicant.service
 2.234s plymouth-start.service
 2.186s systemd-sysusers.service
 1.667s systemd-udevd.service
 1.597s exim4.service
 1.572s ssh.service
 1.429s lightdm.service
1.399s plymouth-quit-wait.service
 1.315s apparmor.service
 1.122s systemd-random-seed.service
 1.073s systemd-tmpfiles-setup-dev.service
 1.041s lm-sensors.service

(+ other services that took less than a second each).

Is it normal? Is there something to fix? Maybe useless services to disable at boot?

Thank you in advance! :)

Hardware details: I’m using an old HP with i3-5005U, 2GHz, 4Gb of RAM and 500Gb HDD.