Hello,
I am trying to install OMV 6.9.4-2 on a Zyxel NSA310.
I am running Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 installed following this guide: https://forum.doozan.com/read.php?2,12096
On top of that I installed systemd.
Initially I tried installing with this script: sudo wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash but this fails because of "Unsupported architecture: armel"
Then I followed the installation procedure for Debian from here: https://docs.openmediavault.or…stallation/on_debian.html
The installation stuck on Deploying service configurations ... and after restart I can connect to OMV but the page says Dashboard unconfigured. (I am connecting to OMV with a normal user. The default admin/openmediavault login says wrong credentials. The default login also doesn't work on an install I did a few day ago on a R Pi4, but there a normal user works fine, I have all the options in the OMV interface)
During startup everything is ok except this:
[FAILED] Failed to start chrony, an NTP client/server.
See 'systemctl status chrony.service' for details.systemctl status chrony.service :
root@debian:~# systemctl status chrony.service
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-10-29 15:24:17 PDT; 36s a go
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 500 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1 /FAILURE)
CPU: 337ms
Oct 29 15:24:14 debian systemd[1]: Starting chrony, an NTP client/server...
Oct 29 15:24:16 debian chronyd[513]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Oct 29 15:24:17 debian chronyd[513]: Fatal error : Failed to load seccomp rules
Oct 29 15:24:17 debian chronyd[500]: Failed to load seccomp rules
Oct 29 15:24:17 debian systemd[1]: chrony.service: Control process exited, code= exited, status=1/FAILURE
Oct 29 15:24:17 debian systemd[1]: chrony.service: Failed with result 'exit-code '.
Oct 29 15:24:17 debian systemd[1]: Failed to start chrony, an NTP client/server.
root@debian:~#I also tried configuring the OMV package and I also get and error about the chrony service:
root@debian:/# dpkg --configure -a
Setting up openmediavault (6.9.4-2) ...
Creating users/groups ...
Updating local package archive ...
Updating service units ...
sshd.service is a disabled or a static unit, not starting it.
systemd-journald.service is a disabled or a static unit, not starting it.
Creating configuration database ...
Setting up Salt environment ...
Setting up system ...
Site configuration file 'default' not found.
Deploying service configurations ...
[ERROR ] Command '/usr/bin/systemd-run' failed with return code: 1
[ERROR ] stderr: Running scope as unit: run-rec771030d64a4d2188b12f9adbf078f1.scope
Job for chrony.service failed because the control process exited with error code.
See "systemctl status chrony.service" and "journalctl -xe" for details.
[ERROR ] retcode: 1
[ERROR ] Job for chrony.service failed because the control process exited with error code.
See "systemctl status chrony.service" and "journalctl -xe" for details.
Processing system modifications ...
Processing triggers for openmediavault (6.9.4-2) ...
Restarting engine daemon ...
Updating workbench configuration files ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.13.6-kirkwood-tld-1
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
root@debian:/#Do you have any ideas what I should try?
