Beiträge von MarcS

  • Storage-Filesystem errors after upgrade

    I deleted and recreated all remote mounts. The Filesystems works but when I reboot the same error comes up.

    Every single remote mount throws that error when installed via Plugin.

  • Storage-Filesystem errors after upgrade

    After recent upgrade (and reboot), I am getting an error, when clicking on Storage options in the OMV GUI menue
    >>File Systems:

  • Docker still not working after OMV Upgrade

    Journalctl says nothing usefull

  • Docker still not working after OMV Upgrade

    After recent OMV Upgrades, Docker still did not launch and I had to downgrade docker to make it work.


    This downgrade still seems to be the only workaround for the bugs.

    Beitrag
    RE: docker not working since omv-upgrade
    I've had the same problem on my Odroid HC2, I fixed it by downgrading the docker-ce and docker-ce-cli packages, then restarting the docker service:

    (Quelltext, 4 Zeilen)

    NothingNowhere


    Is there no solution in sight?

  • OMV without nfs v4 server


    At votdev: This text in GUI should probably be changed to reflect the fact that for v4 to work, the share definition MUST NOT have a path (like ..export) included, otherwise the server will automoatically default to v3, and not even tell anybody about it :)

    As jeff0001 kindly pointed out above, the def for v4 must only be server IP.

  • OMV without nfs v4 server

    Incredible. thanks Jeff001. That fixed it! Thank you very much!

    The reason why I used the old convention is that OMV GUI is asking to do so (including export). I did not know that v4 required a different mount path and it seems strange that the server changes protocol version just because of a way to describe the access path, even though I explicitly ask vor v4 in the command. Anyway thanks for pointing this out.

    Probably worth changing the wording in the OMV Plugin to correct that. Otherwise people will always connect as v3.

  • How do I remount a MergerFS mount point without rebooting the system?

    OK - I have now setup all LUKS drives to auto-mount via /etc/crypttab so they cannot be the cause of MergerFS failing.

    After booting the MergerFS pool is still not available although it shows in GUI as defined. If I manually restarting the pool (inside GUI) I am getting this error:

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; systemctl restart srv-mergerfs-JPool.mount' with exit code '1': 

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; systemctl restart srv-mergerfs-JPool.mount' with exit code '1':  in /usr/share/php/openmediavault/system/process.inc:220
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/mergerfs.inc(197): OMV\System\Process->execute(Array, 1)
#1 [internal function]: OMVRpcServiceMergerfs->restartPool(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('restartPool', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Mergerfs', 'restartPool', Array, Array, 1)
#5 {main}