NFS folder access problem

[mataus19]

Hi,

I have been using the VERO 4K+ for 3 months now with no issue however suddenly, the Vero is unable to access my NAS. I have not altered the Vero’s NFS sources. I detected the problem when playing a video and Kodi gave the message “This file is no longer available . Would you like to remove it from the library?”

Now I am having trouble accessing my video folder on my NAS. When I add a source and select NFS it detects the I.P of my NAS and allows access in to the Root folders but will not allow me to access folders within the root?

Initially I thought it was a permission problem with my NAS, so I checked all shared folder settings were correct which they were, and the problem persists.

I have a 2nd Kodi box in another room that works find using same NFS sources, so I thought there may be a network issue from my router via the LAN cable to the Vero? So, I used a Raspberry Pi2 using same network cable the Vero uses and the Pi2 works fine…full access to all shared folders on NAS via NFS.

I then did a fresh install on the Vero of the latest OSMC release [2019.05-1] using USB flash drive and still the problem persists.

Lastly, I did a reset of my NAS settings and still no fix… (since reset all other Kodi boxes, phones, laptops, etc on the network can still access the NAS via NFS)

I’ve ran out of ideas now, so any suggestions would be appreciated.

Thanks!

[ActionA]

SSH into the Vero and enter:
showmount -e (your NAS IP address here)
and paste the output here. Also provide the URL from grab-logs -A

[mataus19]

@ActionA

grab-logs -A

Hi,

Please see details below:

/home/osmc$ showmount -e 192.168.1.2
Export list for 192.168.1.2:
/test
/homes
/Web
/Public
/Multimedia
/Download

https://paste.osmc.tv/lixekumeqa

Thanks!

[bmillham]

Where are your movies? /Multimedia?

[mataus19]

Yes

[bmillham]

When you mount it, you should be able to use:

nfs://192.168.1.2/Multimedia

You may want to consider using fstab or autofs mounts instead of Kodi mounts as they will perform better.

[mataus19]

I think I have proven the issue is with the NAS, I’ve just created a shared test folder and it seems to be working. I have tried all options with other shared folders and matched settings with the test folder but it still will not allow access?

I’ll try another reset on the NAS and create all the folders again to see if that works. Thanks all for your help!

I’m not familiar with fstab or autofs so I’ll read up on it! Thanks for the suggestion.

[bmillham]

If you consider switching to system mounts, I’d suggest autofs. It’s more tolerant of network issues and server reboots.

Mounting network shares with autofs (alternative to fstab)

This how-to describes how to mount your network shares via autofs. Autofs should be as performant as fstab based mounting but has the advantage that your shares are mounted on demand which also should give you more reliability in case of network interuptions. First install the autofs package sudo apt-get install autofs If you already have mounted your shares already via fstab comment out that line in fstab and reboot. For this how-to we are going to use a directory for each server, if you wa…

[dillthedog]

Irrespective of whether you end up using fstab or autofs, you can still try to mount the share interactively from the command line using the -v (verbose) option:

sudo mkdir /mnt/multimedia
sudo mount -v -t nfs 192.168.1.2:/Multimedia /mnt/multimedia

(If you’ve already created a mount point, skip step 1 and use it in step 2.)

[mataus19]

Thanks for the advice!

I still cannot get the NFS share to work using Kodi even after I’ve reinitialised my QNAP NAS… complete factory reset and wiping the drives and the problem still persists? Every other Kodi client I have on the network is able to mount the NFS from within Kodi. Really strange why it’s only the Vero that has this problem. I’ve never had this issue in all the years using Kodi?

I’ll give fstab / autofs a go and see if it works.

[bmillham]

Did you try manually mounting as @dillthedog suggested? That’s the best way to track down the problem.

[mataus19]

Hi,

I’ve tried mounting with autofs but I’m struggling as I’m a noob when it comes to linux command… I’ve followed the info in the link @bmillham sent:

Mounting network shares with autofs (alternative to fstab)

This how-to describes how to mount your network shares via autofs. Autofs should be as performant as fstab based mounting but has the advantage that your shares are mounted on demand which also should give you more reliability in case of network interuptions. First install the autofs package sudo apt-get install autofs If you already have mounted your shares already via fstab comment out that line in fstab and reboot. For this how-to we are going to use a directory for each server, if you wa…

I have got as far as:

First install the autofs package
“sudo apt-get install autofs”

but once I type this command:

edit auto.master
“sudo nano /etc/auto.master”

I don’t know what to do… I typed in " /- /etc/auto.nfs.shares --timeout 15 browse" but don’t know where to place it in the text and how to save?

Also after typing “sudo nano /etc/auto.nfs.shares” I don’t know what to edit the following to: “/mnt// :</path/to/share1>”

Any help would be appreciated. Thanks!

[bmillham]

@mataus19

I don’t know what to do… I typed in " /- /etc/auto.nfs.shares --timeout 15 browse" but don’t know where to place it in the text and how to save?

The instructions are clear on this:

and add

 /- /etc/auto.nfs.shares --timeout 15 browse

to the end of the file

As to saving, nano shows at the bottom of the screen the various commands. CTRL-O to save, CTRL-X to exit.

/mnt/<server1>/<share1> <IP of server1>:</path/to/share1>

If you server is named myserver.local and the share is /nfs/myshare and you want in /mnt/Movies:

/mnt/Movies myserver.local:/nfs/myshare

You can replace myserver.local with its IP address instead.

[mataus19]

I’ve managed to mount the multimedia shared folder and I tested it with “ls -lah /mnt//” and it details all the folders within Multimedia.

Thanks for you help with this!

In order for Kodi to scrape videos do I just access the NFS via the normal method of ‘add videos’ then select NFS?

Is autofs running in the background on the Vero now or do I have to enable it?

[bmillham]

@mataus19

Thanks for you help with this!

No problem, I’m glad you got it working!

@mataus19

In order for Kodi to scrape videos do I just access the NFS via the normal method of ‘add videos’ then select NFS?

Add the folders in Kodi as /mnt/Movies (for example). Use the share names like you set them up in autofs.

@mataus19

Is autofs running in the background on the Vero now or do I have to enable it?

Yes, autofs is running automatically. The shares will be mounted when accessed.

[mataus19]

@bmillham

Add the folders in Kodi as /mnt/Movies (for example). Use the share names like you set them up in autofs.

Do I do this by selecting ‘Add Videos’ then ‘Browse’?

[mataus19]

It’s OK I just found it in ‘Root’ then ‘mnt’. Cheers

[mataus19]

Going back to the initial problem I had at the start of this thread with not being able to access folders within the share, I’ve just typed in

‘ls -lah /mnt/QNAP/Movies/Test’

and it states:

'ls: cannot open directory ‘/mnt/QNAP/Movies/Test’: Permission denied.

This is a folder I have created today via the QNAP NAS QTS interface and I’ve ensured all user permissions are set to Read/Write and that NFS is enabled for the Multimedia share. I can open other folders in the share just not recently added ones.

Also this same ‘Test’ folder can be accessed via my NUC running latest release of LibeElec.

So the problem still persists with the Vero!

[bmillham]

It’s not the Vero, it’s a permissions problem on the QNAP. Do you also have execute permissions set on the folder? With linux (that’s what I assume that the QNAP is running) you have to have execute permissions set to access a directory.

[mataus19]

@bmillham

execute permissions

Do you mean execute permissions per client on the LAN. Would that explain why the LibreElec NUC can access the ‘Test’ folder?
I’ve checked all permissions for my only user ‘admin’ and R/W is selected for all shares and NFS is allowed for all clients on the LAN.