No it was not! This probably explains why the Kodi client could never service nfs status
If there wasn't confusing enough, I checked on the server to see if the nfs service was even running. I do not know why I seem to have two shares when the OMV GUI indicates that I only have one, and why are there so many options specified when I only have subtree_check,insecure specified in the GUI. The server's current output from exportfs -v exportfs -v I have made multiple NFS share configuration changes in the OMV GUI as I've tried to find the right combination of options to make the share visible to the Kodi client. For example, /export had not been created and only appeared after I issued exportfs -a from the CLI of the server. I have only ever used the OMV GUI to set up the NFS share and assumed that the necessary files, folders and permissions would be created as a consequence of this. I am now wondering whether the NFS share is even visible on the network and/or whether OMV is behaving correctly for me. Thanks mikebetz42 and subzero79 for your suggestions. I am able to connect to the share from Kodi on everything from a CU-Boxi, Pi3, PC, Android, etc. When configuring the NFS share in OMV, make sure you enter the client IP address not the server IP address! Share options rw,subtree_check,insecure seem to work well for most users.Ĭhanging "secure" in extra options to "insecure" did it for me.
Kodi unable to create gui install#
Install libnfs on the arch linux box to fix this. TL dr Kodi on Arch Linux does not support NFS by default.
Again, I feel that there is something obvious that I am missing. I'll be very grateful for some guidance on this.
I am now going around in circles and making no meaningful progress in solving this problem. This has made no difference to the visibility of the share. I've tried various versions of a potential URL such as 192.168.1.125/24/export/ and 192.168.1.125/export/ but the share remains invisible on the network to any of my devices.Īfter some online searching, I was advised to add a Kodi user to OMV and to change the share's options to subtree_check,insecure,all_squash,anonuid=1002,anongid=100 where anonuid is the guid of the Kodi user. I'm therefore expecting that the share will be visible on 192.168.1.125/24 and have used this in the Kodi interface to find the shared files. When editing the share in the NFS configuration panel, under the Shared folder box appears the following text: The location of the files to share. In the OMV GUI, I've created a shared folder (/media), enabled NFS and added the shared folder, initially with the default shared options of (rw,secure) and with read/write privileges. I want to use NFS rather than SMB because of its (apparently) lower CPU overhead. I have just installed Kodi on a Pi 2 to use as a media server that I want to connect to the OMV/Pi3 NAS drive (where all the media files reside). I'm running OMV 3.0.98 on a Raspberry Pi 3, with an external USB hard drive and sharing folders successfully with SMB. I'm new(ish) to OMV, am a mid-level Linux user but am new to NFS. I feel that there's something obvious that I'm missing but cannot see the wood for the trees, so to speak. My NFS share is not visible to any other device on the network and it's driving me mad trying to troubleshoot what might be wrong.