NFS and Kodi

  • I'm using OMV 5.6.22 and Kodi 19.3.

    I am unable to access OMV with NFS using Kodi, or MrMC. I have tried different server options. Like this:

    - insecure,no_subtree_check

    - insecure,no_subtree_check.all_sqash

    No success. The access via SMB works.

    What can I do? Thanks!

  • What kind of client machine are you trying to access OMV via NFS from?


    How are you doing the NFS mounts on the client machine?


    Does the client machine have all the required NFS client packages installed?

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • I was having a similar problem with my NFS shares and it turned out to be the NFS version that the Kodi client was using. I am using MrMc so I do not have direct access to a CLI on the client.


    You can run sudo showmount -e on your server to check for the NFS shares and that the shares are available. Also when you setup your kodi client try to use the NFS3 mount points.


    nfs://<IP_ADDRESS>/export/sharename/folderinshare

  • I had an issue due to permissions. The shared folder was owned by root so wouldn’t work on remote system. I chown’d from command line to a regular user and users group and it finally worked.


    However I figured that out after I changed shield to use SMB so not going to revert unless there is an issue.

    Former Xpenology user moved to OMV 7.x with ZFS.

    HP Microserver Gen8 - 16GB RAM - 1x 32GB USB - 1x 480 GB SSD - 4x 16TB Exos (Shucked) / ZFS - OMV 7.x bare metal

    HP Microserver Gen7 N54L - 8GB RAM - 1x 32GB USB - 1x 240 GB SSD - 4x 4TB / ZFS - OMV 7.x bare metal

  • Thank you. I will try it. But I don't find an option in Kodi or MrMC to change the NFS-version.

    If you are running MrMC there is no way that I could find to choose the NFS version that client uses. That is why I mentioned the use of the export in the NFS path. I struggled for a day after moving from OMV 4 to OMV 5 and not being able to get NFS shares connected on MrMC, turned out I can not type well with an apple remote. :)


    If you use the NFS4 mount point of nfs://IP_ADDRESS/MOVIES and not nfs://IP_ADDRESS/export/MOVIES MrMC will not connect.


    Aside from that my configuration is very straight forward the only options I have on my NFS shares as what come as default.

    Code
    no_subtree_check,insecure


    Oh one other note, within MrMC you will most likely not be able to browse for your NFS shares. This has something to due with NFS in Debian and I have not located what the NFS advertisement protocol/feature is called to try to enable it. So you will have to type the share in your connect media screen.


    Let us know how you make out.

Participate now!

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