possibly fixed in OMV 5.5.17?
i am running my disks off a usb enclosure with a JMicron controller.
hopefully updating to this version and following the procedure to remove, then reconfigure everything has fixed the problem permanently.
Posts by szech
-
-
i had a similar problem and discuss my fix here: RE: Broken connection to shared directories
-
I had exactly this issue.
Couldn't even run the updater in the omv web interface without an error.
In my case i fixed it by removing all the smb integrations, all the references in the omv interface (virus scan, shared folders, SMART schedules etc etc), unmounted the file systems and finally the drives themselves.
Then i restarted the system with the media drives unplugged, and was able to run the updater.
I also removed any reference to media disks in the omv interface so there is just the system disks.
Then i shut down and plugged the drives back in, and remounted all the filesystems and restored all the integrations.
This fixed the issue.
I suspect it was caused by omv having stale entries in its database, so its expecting drives to exist in /srv/ that are no longer there.
Doing this was less work than re-installing and rebuilding from scratch, so its worth a try imo.Display MoreOK omv-update did not seem to change anything.
The quotaoff -v /srv/* command reported back that five differernt mountpoints or devices were not found or have no quota enabled.
Still when trying to apply changes, I receive the error. Uggh
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color quota 2>&1' with exit code '1': Compound: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1 found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 69, column 1
