Hello!
I can't connect Android-Kodi(16.1)-Clients (Lollipop and Marshmallow) via NFS to OMV3.x. My NFS-optiones:
subtree_check,insecure,fsid=2,all_squash,anonuid=1000,anongid=1000
I have no problems with this Clients:
- Ubuntu 16.04
- OSMC (Debian with Kodi 16.1 - Pi2)
- LibreElec (Kodi 17.x - odroid C2)
I asked in differnt forens:
- Kodinerds (german; Post >= 15)
- Technikaffe.de (german)
and tried different things, but no help was found.
The shares are on snaipraid with MergerFS.
The effect is:
The share is visible, but the content isn't visible.
Under OMV2.x it worked perfect - no problems.
Therefore I ask you as expert:
Does anyone use an Android-Kodi und can connet via NFS to a OMV3.x Server?
Any ideas?
I saw just your new edit from today for nfs:
Pooling filesystems (AUFS, MHDFS and MergerFS)
Since this type filesystems don't have a uuid, you need to add fsid=1 or fsid=anynumber
to the nfs extra options, make sure the number is not 0 and unique in
case you're exporting multiple pools. You also need to add the crossmnt option for mergerfs.
openmediavault 3.0 now generates a unique fsid per exported folder by default so you don't need to add it manually.
My new NFS-option line is now: subtree_check,insecure,crossmnt,all_squash,anonuid=1000,anongid=1000
The result is the same:
The share for Android-Kodi(16.1) is visible, but the content isn't visible.