Hello everyone,
I have encountered a frustrating issue with the slow boot time of my Raspberry Pi Zero W running Raspberry Pi OS Lite (Legacy). My main purpose for this RPi is to create a timelapse device powered by an external power bank and Witty Pi 4 Mini to capture photos and shut down immediately. Given the power constraints, a quick boot time is crucial to save power.
I am using a SanDisk Extreme Pro 64GB SD card, so the boot time should be faster. However, I am unsure why the dev-mmcblk0p2.device is taking so long to start.
To provide some context, here is the current output from the "systemd-analyze" command:And from systemd-analyze blame:I am seeking advice on how to troubleshoot and improve the boot time to at least 15 seconds, but I want to be able eventually connect to the wifi (I disable wait for connection in raspi-config) and establish SSH connection, access files on my Mac with netatalk and be able to use WItty Pi 4 Mini. Other functions are not so important for me.
Thank you in advance!
I have encountered a frustrating issue with the slow boot time of my Raspberry Pi Zero W running Raspberry Pi OS Lite (Legacy). My main purpose for this RPi is to create a timelapse device powered by an external power bank and Witty Pi 4 Mini to capture photos and shut down immediately. Given the power constraints, a quick boot time is crucial to save power.
I am using a SanDisk Extreme Pro 64GB SD card, so the boot time should be faster. However, I am unsure why the dev-mmcblk0p2.device is taking so long to start.
To provide some context, here is the current output from the "systemd-analyze" command:
Code:
Startup finished in 4.446s (kernel) + 24.813s (userspace) = 29.259smulti-user.target reached after 24.169s in userspaceCode:
9.248s dev-mmcblk0p2.device7.196s systemd-rfkill.service4.171s user@1000.service3.202s systemd-logind.service2.988s systemd-udev-trigger.service2.807s avahi-daemon.service2.723s raspi-config.service2.498s dphys-swapfile.service2.460s systemd-timesyncd.service2.439s polkit.service2.307s systemd-journald.service2.256s networking.service2.181s ModemManager.service2.118s systemd-fsck-root.service2.110s ssh.service2.065s upower.service1.945s e2scrub_reap.service1.530s modprobe@drm.service1.502s systemd-journal-flush.service1.288s dhcpcd.service1.268s wpa_supplicant.service1.169s netatalk.service1.140s rpi-eeprom-update.service1.079s systemd-modules-load.service1.073s systemd-udevd.service 952ms run-rpc_pipefs.mount 924ms sys-kernel-debug.mount 914ms dev-mqueue.mount 889ms systemd-fsck@dev-disk-by\x2dpartuuid-51030cfd\x2d01.service 883ms sys-kernel-tracing.mount 859ms rsyslog.service 836ms systemd-tmpfiles-setup.service 828ms fake-hwclock.service 808ms kmod-static-nodes.service 790ms modprobe@configfs.service 761ms systemd-remount-fs.service 726ms systemd-update-utmp.service 695ms modprobe@fuse.service 552ms sys-kernel-config.mount 546ms systemd-user-sessions.service 535ms systemd-random-seed.service 529ms systemd-sysctl.service 520ms systemd-sysusers.service 509ms systemd-update-utmp-runlevel.service 479ms sys-fs-fuse-connections.mount 443ms user-runtime-dir@1000.service 335ms systemd-tmpfiles-setup-dev.service 312ms triggerhappy.service 295ms rc-local.service 283ms console-setup.service 170ms nfs-config.service 147ms alsa-restore.service 135ms boot.mount 127ms ifupdown-pre.serviceThank you in advance!
Statistics: Posted by branislavbudzak — Thu May 02, 2024 2:05 pm