Code: Select all
dietpi@DietPi:~$ sudo systemd-analyze Startup finished in 3.613s (kernel) + 47.706s (userspace) = 51.320s graphical.target reached after 47.531s in userspace dietpi@DietPi:~$ sudo 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 @47.531s └─multi-user.target @47.530s └─dropbear.service @47.263s +266ms └─dietpi-boot.service @13.075s +34.165s └─network-pre.target @13.067s └─dietpi-preboot.service @11.717s +1.336s └─dietpi-ramlog.service @11.323s +373ms └─basic.target @11.303s └─sysinit.target @11.292s └─systemd-update-utmp.service @11.020s +268ms └─systemd-tmpfiles-setup.service @10.514s +489ms └─local-fs.target @10.460s └─boot.mount @10.356s +101ms └─systemd-fsck@dev-disk-by\x2dpartuuid-0e2887fb\x2d01.service @9.127s +1.210s └─dev-disk-by\x2dpartuuid-0e2887fb\x2d01.device @8.684s
I'm running an internet radio that basically consists of an amp/speaker, lcd screen, and a few buttons, a rotary encoder, and a few leds. As I'm setting up the sound, etc. I'm noticing that the boot times are almost double what I was starting with on Raspbian.
dietpi-boot.service is clearly the primary culprit, my question is if it is normal at all for that service to take so long, and how might I stop it from taking so long?