This is the boot log: https://paste.libreelec.tv/skilled-lemming.log
I think it started occurring only recently but not sure as I haven't rebooted in a while.
The wait times for each service are:
Code
44.744s wait-time-sync.service
34.878s dev-loop0.device
34.760s dev-mmcblk0p7.device
34.717s dev-mmcblk0p6.device
34.306s systemd-hwdb-update.service
31.903s pulseaudio.service
26.629s nmbd.service
26.612s smbd.service
17.268s swap.service
17.049s add-entropy.service
17.015s envconfig.service
16.972s userconfig.service
16.969s usercache.service
16.964s systemd-udev-trigger.service
16.925s rpcbind.service
16.914s systemd-modules-load.service
16.912s systemd-tmpfiles-setup-dev-early.service
16.906s openssl-config.service
16.880s systemd-journald.service
10.008s kodi-waitonnetwork.service
4.853s sshd.service
711ms connman-vpn.service
686ms iwd.service
633ms dbus.service
525ms samba-config.service
374ms systemd-logind.service
315ms udevil-mount@-dev-mmcblk0p8.service
313ms udevil-mount@-dev-mmcblk0p9.service
272ms kodi-cleanlogs.service
167ms connman.service
143ms dev-mmcblk0p9.device
141ms dev-mqueue.mount
140ms sys-kernel-debug.mount
139ms sys-kernel-tracing.mount
136ms var.mount
136ms kmod-static-nodes.service
135ms machine-id.service
134ms modprobe@configfs.service
132ms storage-log.service
130ms modprobe@drm.service
123ms modprobe@fuse.service
122ms show-version.service
112ms dev-mmcblk0p8.device
87ms kodi-autostart.service
57ms cpufreq.service
56ms cron.service
40ms ledfix.service
36ms systemd-timesyncd-setup.service
30ms vfd-clock.service
30ms systemd-update-utmp.service
28ms systemd-sysctl.service
25ms systemd-update-utmp-runlevel.service
20ms systemd-journal-flush.service
17ms systemd-journal-catalog-update.service
15ms systemd-udevd.service
15ms tz-data.service
15ms network-base.service
13ms sys-fs-fuse-connections.mount
12ms sys-kernel-config.mount
12ms systemd-tmpfiles-setup-dev.service
9ms systemd-tmpfiles-setup.service
7ms kodi.service
7ms systemd-tmpfiles-clean.service
1ms tmp.mount
For comparison this is on a Pi4:
10.247s wait-time-sync.service
7.738s kodi-waitonnetwork.service
7.648s network-online.service
1.706s dev-mmcblk0p7.device
1.663s dev-mmcblk0p6.device
1.618s dev-loop0.device
1.213s systemd-hwdb-update.service
1.191s pulseaudio.service
1.024s connman-vpn.service
963ms dbus.service
934ms iwd.service
817ms samba-config.service
758ms swap.service
551ms udevil-mount@-dev-mmcblk0p9.service
497ms udevil-mount@-dev-mmcblk0p8.service
493ms systemd-logind.service
400ms envconfig.service
377ms add-entropy.service
326ms kodi-cleanlogs.service
266ms systemd-udev-trigger.service
227ms dev-mmcblk0p9.device
222ms sshd.service
213ms userconfig.service
191ms usercache.service
183ms connman.service
175ms storage-log.service
171ms kodi-autostart.service
156ms dev-mmcblk0p8.device
151ms dev-mqueue.mount
150ms nmbd.service
149ms sys-kernel-debug.mount
147ms sys-kernel-tracing.mount
144ms smbd.service
142ms rpcbind.service
142ms var.mount
139ms kmod-static-nodes.service
137ms machine-id.service
135ms modprobe@configfs.service
128ms modprobe@drm.service
125ms systemd-tmpfiles-setup-dev-early.service
124ms modprobe@fuse.service
123ms cpufreq.service
117ms show-version.service
117ms cron.service
113ms systemd-journald.service
109ms openssl-config.service
100ms systemd-modules-load.service
95ms storage-RouterSeagate.mount
87ms storage-RouterSamsung.mount
73ms network-base.service
52ms systemd-sysctl.service
51ms systemd-update-utmp.service
48ms systemd-timesyncd-setup.service
43ms systemd-udevd.service
39ms ledfix.service
33ms tz-data.service
30ms vfd-clock.service
27ms systemd-update-utmp-runlevel.service
25ms systemd-tmpfiles-setup.service
25ms systemd-tmpfiles-setup-dev.service
24ms sys-fs-fuse-connections.mount
22ms systemd-journal-flush.service
20ms systemd-journal-catalog-update.service
19ms sys-kernel-config.mount
16ms kodi.service
3ms tmp.mountThe much longer wait time on dev-loop0.device could be a bad SD card? How to diagnose? Otherwise once booted operational speed seems unchanged. Thanks.
