Hello, I'm really happy being a part of OMV community as a user and this is my first post to the forums!
I'm running the last OMV5 stable with the latest stable updates installed. Last days I'm facing really slow boot to my machine so I gave a #systemd-analyze to translate the problem to numbers
Code
Startup finished in 8.067s (kernel) + 3min 31.535s (userspace) = 3min 39.602s
graphical.target reached after 3min 31.114s in userspaceThe machine uses HDD if it's not obvious!!
Continued with a #systemd-analyze blame and I see that the problem is caused by the openmediavault-issue.service
Code
3min 16.703s openmediavault-issue.service
1min 45.147s docker.service
23.110s salt-minion.service
21.124s apt-daily.service
17.432s nmbd.service
14.888s phpsessionclean.service
13.493s openmediavault-engined.service
13.298s php7.3-fpm.service
11.745s nginx.service
8.210s rrdcached.service
5.497s smbd.service
4.949s dev-sda1.device
4.773s quotaon.service
3.492s folder2ram_startup.service
3.420s collectd.service
3.168s ssh.service
2.970s systemd-networkd-wait-online.service
2.399s monit.service
1.824s quotarpc.service
1.566s networking.service
1.474s wpa_supplicant.service
1.470s avahi-daemon.service
1.426s rsyslog.service
1.425s systemd-fsck@dev-disk-by\x2dlabel-Raid1.service
1.410s systemd-logind.service
1.395s e2scrub_reap.service
1.343s chrony.service
1.296s systemd-resolved.service
1.287s apt-daily-upgrade.service
1.158s loadcpufreq.service
925ms quota.service
883ms keyboard-setup.service
695ms cpufrequtils.service
593ms systemd-modules-load.service
588ms containerd.service
573ms systemd-udev-trigger.service
540ms systemd-sysusers.service
528ms systemd-journald.service
516ms rpcbind.service
509ms srv-dev\x2ddisk\x2dby\x2did\x2data\x2dWDC_WD800JD\x2d55MUA1_WD\x2dWMAMD5415017\x2dpart3.mount
496ms run-rpc_pipefs.mount
489ms openmediavault-beep-up.service
448ms systemd-udevd.service
447ms systemd-networkd.service
417ms systemd-random-seed.service
387ms nfs-config.service
382ms openmediavault-cleanup-php.service
314ms dev-disk-by\x2duuid-f0de3fb9\x2d4209\x2d4cf0\x2da97c\x2da34d29943903.swap
304ms systemd-journal-flush.service
301ms console-setup.service
299ms openmediavault-cleanup-monit.service
290ms dev-mqueue.mount
290ms lvm2-monitor.service
283ms dev-hugepages.mount
283ms systemd-tmpfiles-setup-dev.service
281ms sys-kernel-debug.mount
280ms kmod-static-nodes.service
261ms srv-dev\x2ddisk\x2dby\x2dlabel\x2dRaid1.mount
250ms systemd-remount-fs.service
245ms systemd-fsck@dev-disk-by\x2did-ata\x2dWDC_WD800JD\x2d55MUA1_WD\x2dWMAMD5415017\x2dpart3.service
245ms blk-availability.service
219ms ifupdown-pre.service
208ms systemd-tmpfiles-setup.service
193ms systemd-quotacheck.service
148ms systemd-update-utmp.service
141ms systemd-user-sessions.service
139ms systemd-sysctl.service
104ms nfs-blkmap.service
84ms watchdog.service
23ms systemd-update-utmp-runlevel.service
6ms tmp.mount
5ms docker.socketI don't find normal for this service to take so long to start and with a search I didn't find anything about it.
Has anyone any idea or a different opinion in comparison with his own boot times?
