OMV on RPi3 unable to display file system after adding Remote Share

    • Resolved
    • OMV 3.x
    • OMV on RPi3 unable to display file system after adding Remote Share

      I have installed OMV on a RPi3 - all went well for some time.

      I then decided to install Plex Media Server and to mount some remote share (from another NAS running OMV in the same network).
      These share are shared via SMB/CIFS as read only and equally mounted with the "ro" switch.

      Every time I try to browse to Storage > File Systems I get the following error.


      1. Could not fetch a matching mount point from the provided fsname: '/media/56ce3c2c-9f9a-47c9-94ce-802744ba02b8'.

      The details of the error are the following.


      1. Error #0:
      2. exception 'OMV\Exception' with message 'Could not fetch a matching mount point from the provided fsname: '/media/56ce3c2c-9f9a-47c9-94ce-802744ba02b8'.' in /usr/share/php/openmediavault/system/filesystem/backend/
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/system/filesystem/backend/ OMV\System\Filesystem\Backend\RemoteAbstract::fetchMountPointFromFstabByFsnameAndType('/media/56ce3c2c...', 'cifs')
      5. #1 /usr/share/php/openmediavault/system/filesystem/ OMV\System\Filesystem\Backend\RemoteAbstract->getImpl('/media/56ce3c2c...')
      6. #2 /usr/share/openmediavault/engined/rpc/ OMV\System\Filesystem\Filesystem::getFilesystems()
      7. #3 [internal function]: OMVRpcServiceFileSystemMgmt->enumerateFilesystems(NULL, Array)
      8. #4 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
      9. #5 /usr/share/openmediavault/engined/rpc/ OMV\Rpc\ServiceAbstract->callMethod('enumerateFilesy...', NULL, Array)
      10. #6 [internal function]: OMVRpcServiceFileSystemMgmt->getList(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
      12. #8 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
      13. #9 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getList', Array, Array, 1)
      14. #10 {main}
      Display All

      If I look at /etc/fstab, the entry '/media/56ce3c2c-9f9a-47c9-94ce-802744ba02b8' is there.
      Equally the mountpoint exists in the '/media/' directory and is fully accessible (II can browse the content of the share).

      Has anyone got any suggestion on how to overcome this?

      Thank you.

      Best regards,
    • Replying to myself in case someone else faces the same issue.

      I think there are 2 factors that have a barring on this issue.

      /etc/fstab contained some '\n' as opposed to have one entry per line.

      The Remote Share plugin was not in fact able to fetch the share from /etc/fstab as the entries were separated by '/n' and there wasn't an entry per line.

      The file looked like:

      Source Code

      1. /media/75ea105e-129b-4406-b371-7ee2ac17d7e9 nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0\n10.0.0.1:Share2 /media/acce9ca3-32cc-4bfe-ba4c-992bb5fcccc0 nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0

      I had to manually alter the file so that there was an entry per line, as follows.

      Source Code

      1. /media/75ea105e-129b-4406-b371-7ee2ac17d7e9 nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0
      2. /media/acce9ca3-32cc-4bfe-ba4c-992bb5fcccc0 nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0

      This has addressed the issue with the Remote Share plugin which is now able to retrieve both the NFS Shares.
      Needless to say that if I make any change via the Web UI, that reintroduces the '\n' in /etc/fstab and the issue comes back.

      The shares were not getting mounted on reboot.

      I also noticed sometimes neither of the 2 shares were getting mounted, due to a latency in acquiring an IP via DHCP.

      Adding ',ro,noexec,noauto,noatime,x-systemd.automount' to the default 'rsize=8192,wsize=8192,timeo=14,intr' seems to have addressed this problem.
      Now both the shares gets resiliently mounted after each reboot.

      /etc/fstab now looks like the following.

      Source Code

      1. /media/75ea105e-129b-4406-b371-7ee2ac17d7e9 nfs4 rsize=8192,wsize=8192,timeo=14,intr,ro,noexec,noauto,noatime,x-systemd.automount 0 0
      2. /media/acce9ca3-32cc-4bfe-ba4c-992bb5fcccc0 nfs4 rsize=8192,wsize=8192,timeo=14,intr,ro,noexec,noauto,noatime,x-systemd.automount 0 0

      Hope this can be of help to others as well.

    • I don't know why the linefeed character (\n) is working on some systems and not others. I will have to try my RPi.

      As far as the other issue, the noauto,x-systemd.automount are the important options. I would have to do more testing to determine if these should be default options.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13 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!