How to prevent auto mount of remote mounts?

  • My omv machine remote mounts a folder on my windows machine for rsync. The problem is when my windows PC goes to sleep, the omv dashboard is unable to load information and frequently freezes. Unmounting from the dashboard does not work and fails with some error message about the remote mount not being reachable. To get around this, I have to make sure I unmount the remote mount BEFORE putting my windows machine to sleep.


    I think if I could prevent my omv machine from trying to auto mount in the first place, I can just manually mount and unmount whenever I need to run a rsync task. That said, maybe there should be a way for the omv machine to auto mount and unmount depending on reachability? Thanks in advance.

  • crashtest

    Approved the thread.
    • Official Post

    maybe there should be a way for the omv machine to auto mount and unmount depending on reachability?

    This is going against what OMV is designed for. OMV expects its disks to be available all the time. When I wrote the remotemount (remoteshare before that), it was meant to have the share mounted all of the time. I did add the mount/unmount but typically the mount is in use. You could try adding noauto to the options in the remotemount but you probably going to run into weird issues.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    This is going against what OMV is designed for. OMV expects its disks to be available all the time. When I wrote the remotemount (remoteshare before that), it was meant to have the share mounted all of the time. I did add the mount/unmount but typically the mount is in use. You could try adding noauto to the options in the remotemount but you probably going to run into weird issues.

    bogardon This behaviour is derived by the fact that all services that rely on those file systems and the shared folders that are created on top of them will failure if the file system is not available anymore. So this is not only a design decision of OMV out of the blue.

    • Official Post

    This behaviour is derived by the fact that all services that rely on those file systems and the shared that are created on top of them will failure if the file system is not available anymore. So this is not only a design decision of OMV out of the blue.

    I know. I am just bad at explaining.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Ah ok. Thanks for the explanations. FWIW i did try add `noauto` to the relevant entry in `conf.system.filesystem.mountpoint`, but it seems to still automount on boot.


    No big deal, I almost never reboot my omv machine anyways.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!