No browsing of NFS shares with Synology

kottn · 11 May 2017 18:10

Hi there,

I’m not able to browse NFS shares (Synology DS415+) on my brand new Vero 4K.

Following settings have been made on my Synology already:

steps according to: http://kodi.wiki/view/NFS#Synology

and I’ve edited the /etc/exports:

/volume1/video 192.168.178.9(rw,async,no_wdelay,insecure,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100) 192.168.178.11(rw,async,no_wdelay,crossmnt,insecure,all_squash,insecure,sec=sys,anonuid=1024,anongid=100)

sudo exportfs -ra

192.168.178.9 is my old RPi2, which is working fine; the 192.168.178.11 is my Vero 4K.

Do you have any ideas what might be wrong? Did I forget any details which you need?

Thank you in advance.

Best,
Chris

sam_nazarko · 11 May 2017 18:14

What happens when you try to browse? Can’t browse is a big vague

Do you have a log?

kottn · 11 May 2017 18:27

Hi Sam,

when hitting Network File System (NFS) on the GUI I expect the GUI to show me my Synology. Instead it’s loading and then I’m back at the menu where to select for a new share.

I’m very new to this, so I hope you mean this log: https://paste.osmc.tv/avetuyubip

Best,
Chris

dillthedog · 11 May 2017 19:06

There was a thread a short while ago where someone else was having access problems to a Synology box. Unfortunately, he’d tried all sorts of things (without success) and the state of his system had become a bit of a mess. That said, it might still be the case that Synology servers have too many idiosyncracies, though your Pi 2 clearly disagrees . It’s certainly true of Synology’s flavour of Linux.

If possible, I’d like to simplify the /etc/exports entries a bit. Can you see if:

/volume1/video 192.168.178.11(ro,all_squash,anonuid=1024,anongid=100)

works for the Vero 4K? (Comment out the rest of the file.) As you can see, I’ve gone for read-only for now.

kottn · 11 May 2017 19:29

Hi dillthedog,

unfortunately, it still has the same behavior, no change… So there is nothing I can do?

When I read the announcement the Vero 4K got out, someone was talking about Synology and NFS (which was working apparently). I’ll try to get in touch with him and see if he did something differently to get it work.

Of course I’m still open to other suggestions

Edit: I tried both, 1024 and 1025.

Chris

dillthedog · 11 May 2017 19:43

My suggestion is that instead of simply saying it doesn’t work, it’s a lot more helpful if you show us what you did and what result you got.

I’d like you to show me few of the files in /volume1/video using ls -la. Just a few files will do, including dot and double-dot.
On Synology, run id 1024 and id 1025
On the Vero 4K, run showmount -e 192.168.178.X where X is your Synology box.

Tom_Doyle · 11 May 2017 19:46

you’ve got insecure twice for vero4k, should it be insecure_locks for second reference:

192.168.178.11(rw,async,no_wdelay,crossmnt,insecure,all_squash,insecure_locks,sec=sys,anonuid=1024,anongid=100)

Have you considered doing it as one export:

/volume1/video 192.168.178.0/24(rw,async,no_wdelay,insecure,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)

Thanks Tom.

sam_nazarko · 11 May 2017 19:50

No – he was trying to change the UID for the OSMC user, which is absolutely unnecessary. In his situation, we were simply saying that OSMC follows the specification, Synology does not.

But in no way would that prevent him from streaming from a Synology NAS.

It will be a network issue or something wrong with the fstab mount.

dillthedog · 11 May 2017 19:55

As I recall, that was his first pitch, but when it became clear that it wasn’t possible, we explored other avenues but ultimately without a successful resolution to his problem…

sam_nazarko · 11 May 2017 19:56

Several users are using NFS via Synology on Vero 4K, for example @michael47.
If you have to force a UID, there is the squash option as well.

I didn’t follow the post closely, but there is no requirement for this, hence why we have authentication.

kottn · 11 May 2017 19:59

chrisg@Diskstation:/volume1/video$ ls -la
total 64
drwxrwxrwx+   8 root   root   4096 May 10 22:49 .
drwxr-xr-x   23 root   root   4096 May 10 22:48 ..
drwxrwxrwx+   5 chrisg users  4096 Jun 25  2015 doku
drwxrwxrwx+   3 root   root   4096 May 10 18:52 @eaDir
drwxrwxrwx+ 265 chrisg users 36864 Mar 18 17:56 filme
drwxrwxrwx+   3 chrisg users  4096 Jun  7  2015 konzerte
drwxrwxrwx+  78 chrisg users  4096 Feb 19 20:40 serien
drwxrwxrwx+  16 chrisg users  4096 May 11 08:19 UHD

chrisg@Diskstation:/volume1/video$ id 1024
uid=1024(admin) gid=100(users) groups=100(users),101(administrators),25(smmsp)
chrisg@Diskstation:/volume1/video$ id 1025
uid=1025(guest) gid=100(users) groups=100(users)

osmc@osmc-Ian:/$ showmount -e 192.168.178.13
Export list for 192.168.178.13:
/volume1/video 192.168.178.11,192.168.178.9
/volume1/music 192.168.178.9

kottn · 11 May 2017 20:12

Hi Tom,

I somewhere read to delete the “_locks”, but no change, when putting

/volume1/video 192.168.178.0/24(rw,async,no_wdelay,insecure,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)

to the /etc/exports + sudo exportfs -ra and trying to browse for NFS shares. I also tried to use * as wildcard instead of the subnet.

The kodi.log says the following:

22:11:16.384 T:3888096240 ERROR: NFS: Failed to mount nfs share: (nfs_mount_async failed)
22:11:19.412 T:4109295616 ERROR: GetDirectory - Error getting nfs://
22:11:19.412 T:4109295616 ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://) failed

Chris

dillthedog · 11 May 2017 20:15

1 Can we go back to the simple one-line /etc/exports please? Please amend the line to read:

/volume1/video 192.168.178.11(ro,all_squash,no_acl,anonuid=1024,anongid=100)

Please also show us the full /etc/exports formatted with the </> symbol.

2 Please run ls -la on /volume1/video/filme and again show us a few files, including dot and double-dot.

3 Are you using /etc/fstab on the Pi 2 to mount the NFS shares? If so, let’s see it, please.

Edit: Have you already seen this thread on the Kodi forum?
Edit 2: Corrected mistype of no_acl option

Tom_Doyle · 11 May 2017 20:29

Hi Chris,

Don’t if this helps:

http://forum.kodi.tv/printthread.php?tid=201201&page=2

But according this user had success by setting the permissions for user and group to everybody.

Thanks Tom.

kottn · 11 May 2017 20:33

chrisg@Diskstation:/$ sudo cat /etc/exports

/volume1/music 192.168.178.9(ro,async,no_wdelay,insecure,no_root_squash,sec=sys,anonuid=1025,anongid=100)
/volume1/video 192.168.178.11(ro,all_squash,no_acl,anonuid=1024,anongid=100)

chrisg@Diskstation:/volume1/video/filme$ ls -la
total 1316
drwxrwxrwx+ 265 chrisg users 36864 Mar 18 17:56 .
drwxrwxrwx+ 8 root root 4096 May 10 22:49 …
drwxrwxrwx+ 3 chrisg users 4096 May 10 22:45 12 Years a Slave (2013)
drwxrwxrwx+ 4 chrisg users 4096 May 10 22:44 21 (2008)
drwxrwxrwx+ 3 chrisg users 4096 May 10 22:44 99 Francs (2007)
drwxrwxrwx+ 3 chrisg users 4096 May 10 22:45 A Beautiful Mind (2001)
drwxrwxrwx+ 3 chrisg users 4096 May 10 22:44 A Clockwork Orange (1971)

I didn’t use fstab to mount NFS shares on my Pi2 (openelec), I was using the GUI as I’m trying now.

And do you mean to use the insecure option? Or to delete the “_locks” part? I tried both.

dillthedog · 11 May 2017 20:55

So not OSMC. My psychic powers are clearly failing me today.

I had a quick read of the Kodi forum and it was being suggested that the insecure option should be used. I had to look it up and it’s for NFS connections on ports >=1024. I just tried an NFS mount using Kodi on my Vero 4K, but it’s using port 564, so the insecure option is not necessary, at least in my case…

tcp 0 0 osmc:564 192.168.8.3:nfs ESTABLISHED 987/kodi.bin

Can you drill down to a real file and show me the permissions?

kottn · 11 May 2017 21:10

HI Tom,

to change the local file permission for everyone sounded promising, but neither read nor R/W (including apply to sub-folders) worked for me. I also tried a few exports (the one of my original post and the one @dillthedog mentioned in his posts) with the new permissions, no luck.

Chris

kottn · 11 May 2017 21:17

Sorry, that I didn’t mention that earlier.

Here an example:

 chrisg@Diskstation:/volume1/video/filme/12 Years a Slave (2013)$ ls -la
total 14200160
drwxrwxrwx+   3 chrisg users        4096 May 10 22:45 .
drwxrwxrwx+ 265 chrisg users       36864 Mar 18 17:56 ..
-rwxrwxrwx+   1 root   root       200076 May 10 22:45 12.Years.a.Slave.1080p.PK-fanart.jpg
-rwxrwxrwx+   1 chrisg users 14540619727 May 16  2014 12.Years.a.Slave.1080p.PK.mkv
-rwxrwxrwx+   1 root   root        23120 May 10 22:45 12.Years.a.Slave.1080p.PK.nfo
-rwxrwxrwx+   1 root   root        39147 May 10 22:45 12.Years.a.Slave.1080p.PK-poster.jpg
drwxrwxrwx+   2 root   root         4096 May 10 22:45 .actors

Permissions, owners and groups look like the same in other folders.

sam_nazarko · 11 May 2017 21:18

If you’re mounting via fstab, why are you browsing for NFS?

Should show a (local) path because mount is handled by fstab.

Tom_Doyle · 11 May 2017 21:21

Hi Chris,

When you set the file permissions to everybody, other than ro, or rw, what other settings did you have. From looking at kodi wiki link you provided, it would be something like this:

/volume1/video 192.168.178.11(ro,async,no_wdelay,crossmnt,insecure,all_squash,anonuid=1024,anongid=100)

@sam_nazarko I don’t think Chris is mounting via fstab.

Thanks Tom.