Slow boot even after all optimizations

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
arahasya
Posts: 3
Joined: Wed Oct 14, 2020 8:38 pm

Slow boot even after all optimizations

Post by arahasya »

Hi,

I have disabled the network wait time and ntp. I have setup chromium autostart. Waiting for dietpi- post boot is taking more than 40 seconds. Why is this happening ? Using Rpi 3b+

root@DietPi:~# systemd-analyze blame
1.168s dev-mmcblk0p2.device
462ms systemd-fsck@dev-disk-by\x2dpartuuid-907af7d0\x2d01.service
338ms keyboard-setup.service
289ms var-swap.swap
240ms dietpi-preboot.service
223ms dietpi-boot.service
215ms systemd-udev-trigger.service
183ms systemd-fsck-root.service
162ms dietpi-ramlog.service
124ms systemd-remount-fs.service
123ms networking.service
122ms dropbear.service
117ms systemd-journald.service
97ms systemd-udevd.service
95ms fake-hwclock.service
84ms dev-mqueue.mount
79ms systemd-modules-load.service
79ms kmod-static-nodes.service
75ms sys-kernel-debug.mount
70ms systemd-sysctl.service
66ms boot.mount
66ms systemd-sysusers.service
64ms systemd-journal-flush.service
63ms systemd-tmpfiles-setup.service
58ms systemd-update-utmp.service
52ms systemd-tmpfiles-setup-dev.service
50ms systemd-random-seed.service
47ms systemd-update-utmp-runlevel.service
40ms rng-tools.service
31ms systemd-user-sessions.service
27ms ifupdown-pre.service
19ms console-setup.service
17ms var-log.mount
15ms tmp.mount
15ms alsa-restore.service
13ms sys-kernel-config.mount
User avatar
Joulinar
Posts: 2287
Joined: Sat Nov 16, 2019 12:49 am

Re: Slow boot even after all optimizations

Post by Joulinar »

Hi,

many thanks for your message. The boot process until login prompt looks pretty much ok. Larges part is mounting the SD card. But with 1 sec, it's quite fast. There is nothing serious on your systemd-analyze blame. To get a better inside what is happening after reaching login prompt, I would recommend to have a look into journalctl. This should give you full overview with all time stems and activities.
  1. reboot your system
  2. wait until all is finished and started
  3. export the journalctl, as it will be quite long output and might be easier to verify once exported
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply