Will OMV5 support the remote-mount plugin?

    • OMV 5.x (beta)
    • Will OMV5 support the remote-mount plugin?

      Hi. I successfully installed OMV5 BETA on Armbian Buster. Everything seems to work fine :)

      I've got a question about the "remote-mount" plugin which I used on OMV4 for the old NAS backups.
      Will this plugin be available in OMV5? If yes, is there any known ETA for it? I'm asking, because if this plugin was dropped, then I will already try to find an alternative for it.

      Greetings.
    • Moan wrote:

      Will this plugin be available in OMV5? If yes, is there any known ETA for it? I'm asking, because if this plugin was dropped, then I will already try to find an alternative for it.
      Eventually I plan to port it. I really hate that plugin. It generates sooo many support requests caused by improper setup and/or doing bad things with it. The plugin needs to be flexible though. I don't have an ETA. I need to finish porting rsnapshot first and barely have any time for that.

      If the old server supports rsync, you don't need remotemount.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I vote for this too. I have a remote windows server that I am offering to the local users as NFS shares and without this plugin it would be a lot more complicated to do this.

      Another use is to connect to a remote repository to be used as target bor backups so it is quite useful.
    • No need to vote for it. I have it on my list to port. I just don't like the plugin.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Thank you. Unfortunately, for now it doesn't want to work for me:
      0 2 +//192.168.1.130/40b40e40r40n40a40d40e40t40a40 /srv/402be38b-a450-4be2-a1f7-6433854231d9 cifs _netdev,iocharset=utf8,vers=2.0,nofail,credentials=/root/.cifscredentials-11a9d9b9-265b-41bf-b8a6-c45da5a6a5f8 0 0 # <<< [openmediavault] Summary for odroidn2 ------------- Succeeded: 10 (changed=5) Failed: 1 ------------- Total states run: 11 Total run time: 911.169 ms

      I noticed that /etc/fstab has:
      //192.168.1.130/^@40b^@40e^@40r^@40n^@40a^@40d^@40e^@40t^@40a^@40 /srv/402be38b-a450-4be2-a1f7-6433854231d9 cifs _netdev,iocharset=utf8,vers=2.0,nofail,credentials=/root/.cifscredentials-...

      is "^@40" an expected encoding for the share name?

      When I removed the remote share from the "Remote Mount" page, the configuration saved successfully, so I'm sure it doesn't fail due to any other local mount.

      EDIT:
      (this is the line with new entry)
      root@odroidn2:~# mount -a

      mount: /etc/fstab: parse error at line 8 -- ignored


      EDIT2:
      I manually edited file:
      /srv/salt/omv/deploy/fstab/90remotemount.sls

      And replaced:
      {% set share = '//' + mnt.server + '/' + mnt.sharename | replace('', '\\040') %}
      to:
      {% set share = '//' + mnt.server + '/' + mnt.sharename %}

      And the problem is gone.

      Thank you once again for this plugin!

      The post was edited 7 times, last by Moan ().

    • Moan wrote:

      And the problem is gone.
      I just fixed the plugin a little bit ago. 5.0.1 is in the repo. Removing the replace line is not the correct fix. It is just supposed to replace spaces with \\040.
      omv 5.2.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!