Vero 4K+ forgets or cannot mount at all one of the autonfs share (at least one)

Help and Support Vero 4K / Vero 4K +
1

Hi,
Today I nearly finished my setup, when ran into another problem.
I made a OpenMediaVault NAS on a Raspberry Pi with the connected USB HDDs, and shared them via SMB and NFS as well. (13 HDDs)

Everything works prefectly, I can see all HDDs on my LAN on Windows PC (SMB).

My Vero mounts the drives via auto.nfs.shares, however for some reason it creates an additional nfs4 shares with the same name destroying the access to the NTFS HDD.

In Vero’s Settings/MediaFiles/Videos … I can see all the mounted HDDs, but one of them (the newest one) is rarely available, or disappears after a few minutes (or library scanning). Sometimes more HDDs disappear as well, so I need to reboot the Vero, and they are mostly back, except that particular one.

I SSH the Vero, and ran the mount command:

=============================================================================

osmc@Vero-Bedroom:~$ mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=757400k,nr_inodes=189350,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
/dev/mapper/vero--nand-root on / type ext4 (rw,relatime,stripe=1024,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/bfqio type cgroup (rw,nosuid,nodev,noexec,relatime,bfqio)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/etc/auto.nfs.shares on /mnt/MOVIES-2 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-MOVIES-2 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/X-FILES type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/FAMILY-VIDEOS type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MUSIC type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-5 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TVSHOW-DOC-CONCERT type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-DOLBYVISION-1 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/KODI-SSD-STORAGE type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-2 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-3 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-4 type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/3D-MOVIES type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-DOCUMENTARIES type autofs (rw,relatime,fd=6,pgrp=480,timeout=15,minproto=5,maxproto=5,direct)
192.168.1.130:/4K-MOVIES-2/4K-DOCUMENTARIES on /mnt/4K-DOCUMENTARIES type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.132,local_lock=none,addr=192.168.1.130)
192.168.1.130:/4K-MOVIES-2/4K-MOVIES_2 on /mnt/4K-MOVIES-2 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.132,local_lock=none,addr=192.168.1.130)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=176412k,mode=700,uid=1000,gid=1000)

osmc@Vero-Bedroom:~$ ls -lah /mnt/4K-MOVIES-2
ls: cannot access ‘/mnt/4K-MOVIES-2’: Stale file handle

The problematic NFS share is the 4K-MOVIES-2, and after the auto.nfs.shares list, it lists again them as a type nfs4…

As you can see, I tried to list the share and it says: stale file handle

Can you please tell me what can cause this problem?
In addition to that, when I try to browse in the Vero’s Settings/MediaFiles/Videos… /Add Share, I can see a share under the Root/mnt folder which does not exists at all anymore. (4K-MOVIES-3), however this is not listed here at all.

Thanks in advance for your help.

2

I used the Blockquote format button to make your post better readable.

3

Looks like you have mixed autofs and fstab entries.
What’s the output of paste-log /etc/fstab

4

This is the output

5

Btw, I have 2 Vero’s at home, and both does the same weird thing with this shared NFS HDD.

6

Strange there are no entries in the fstab which could have caused this.
Suggest to upload full logs via grab-logs -A and share the URL.
And also paste-log /etc/auto.nfs.shares
Also just to reconfirm all shares are on the same machine and configured identically?

7

Here is the gab-logs -A link: https://paste.osmc.tv/vuyozudiwu
And the autonfs log: [(https://paste.osmc.tv/vadaqaveri)]

Yes, all shares are USB HDDs connected to the OpenMediaVault NAS server on my Raspberry Pi, and shared with the same settings as NFS and SAMBA shares as well.

I’m not sure, if I have 13 HDDs, that the timeout can be problematic if they are in low power usage spindown state. But then why only the last HDD causing the problem, and if it manages to mount, why vero forgets it after a few minutes - sometimes pulling with itself some other NFS shares as well.

8

If you comment the following lines in /etc/auto.nfs.shares and reboot and then run mount what is the output>

#/mnt/4K-MOVIES-2 192.168.1.130:/4K-MOVIES-2/4K-MOVIES_2
#/mnt/4K-DOLBYVISION-1 192.168.1.130:/4K-MOVIES-2/4K-DOLBYVISION_1
#/mnt/4K-DOCUMENTARIES 192.168.1.130:/4K-MOVIES-2/4K-DOCUMENTARIES

9 
> Blockquote
osmc@Vero-Bedroom:~$ sudo nano /etc/auto.nfs.shares
osmc@Vero-Bedroom:~$ sudo systemctl restart autofs
osmc@Vero-Bedroom:~$ mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=757400k,nr_inodes=189350,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
/dev/mapper/vero--nand-root on / type ext4 (rw,relatime,stripe=1024,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/bfqio type cgroup (rw,nosuid,nodev,noexec,relatime,bfqio)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=176412k,mode=700,uid=1000,gid=1000)
/etc/auto.nfs.shares on /mnt/MOVIES-2 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/X-FILES type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/FAMILY-VIDEOS type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MUSIC type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-5 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TVSHOW-DOC-CONCERT type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/KODI-SSD-STORAGE type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-2 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-3 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-4 type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/3D-MOVIES type autofs (rw,relatime,fd=6,pgrp=10120,timeout=15,minproto=5,maxproto=5,direct)
10

It looks better, no fstab mounts…

11

OK, I added back the commented out lines one by one, and restarted the autonfs with
sudo systemctl restart autofs and the mount list look OK now.
However I cannot restart the Vero at the moment, as I do not have access to that TV, or I may try this process on the other one, if you think that the hardware restart messing up the mounts.

However its still magical, from where Vero gets the ‘4K-MOVIES-3’ share under Root/mnt when it is not even exists anywhere.

12

Is it a mount or just an empty folder?

13

Well, I’m not sure, I can create a link to it in Vero, so it thinks its a share (I think it just was a share in the past), but its empty inside.

14

Well that would indicate that they are actually not fstab related but somehow related to autofs.

15

Definitely strange, did you used before any other way to mount shares? E.g. system service or crontab?

16

Hi, no, as I do not even know what they are.
But here’s the thing. After repairing the mounts I went to the Vero, and Browsed the mounted HDDs in the MediaSettings/Videos …

All shares were listing nicely the HDD content, and Clicked on all of them, but all of the sudden, they started to be unavailable. Just by accessing them.

I checked again in the SSH the mounts, and the fstab nfs4 shares appeared again.

Blockquote
/etc/auto.nfs.shares on /mnt/MOVIES-2 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-1 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-MOVIES-2 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/X-FILES type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/FAMILY-VIDEOS type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MUSIC type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-5 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TVSHOW-DOC-CONCERT type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-1 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-DOLBYVISION-1 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/KODI-SSD-STORAGE type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/TV-SERIES-2 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-3 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/MOVIES-4 type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/3D-MOVIES type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
/etc/auto.nfs.shares on /mnt/4K-DOCUMENTARIES type autofs (rw,relatime,fd=6,pgrp=14059,timeout=15,minproto=5,maxproto=5,direct)
192.168.1.130:/TV-SERIES-1/TV-SERIES_1 on /mnt/TV-SERIES-1 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)
192.168.1.130:/MOVIES-3/MOVIES_3 on /mnt/MOVIES-3 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)
192.168.1.130:/MOVIES-4/MOVIES_4 on /mnt/MOVIES-4 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)
192.168.1.130:/4K-MOVIES-2/4K-DOCUMENTARIES on /mnt/4K-DOCUMENTARIES type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)
192.168.1.130:/4K-MOVIES-2/4K-DOLBYVISION_1 on /mnt/4K-DOLBYVISION-1 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)
192.168.1.130:/4K-MOVIES-2/4K-TV-SERIES_1 on /mnt/4K-TV-SERIES-1 type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.131,local_lock=none,addr=192.168.1.130)

What is going on?

17

And meanwhile the HDD and all its folders are fully accessible on my Windows PC, so its not a NAS or hardware issue, rather than the NFS share and Vero cooperation.

After sending the sudo systemctl restart autofs command, all sets back to normal for a while.

18

Ok, checking some old posts. Maybe try to limit to nfs version3 only
In /etc/autofs.conf set mount_nfs_default_protocol = 3
And restart autofs

19

Now I resetted again the mounts, and started to browse between the hard drive shares, and now two other NFS shares became unavailable.

I will try your suggestion now with protocol 3.

20

Hi fzinken,
Thanks a lot, it seems its much more stable with this protocol 3 settings, I was jumping in and out from the shares, and could not recreate the problem. I even rebooted the Vero to see if it messing up something or not, but it seems all OK.

Except… I decided to run the Library Update now, as I can safely see all the shares, and while I do not see any share access problem, when I check the mounts on the SSH, I can see another NFS share again became nfs4 share :frowning: Interestingly, Vero does not care about it, and nicely browsing the content, but its still annoying.

I also checked in the File Exporer of Vero, and I can still see in the root/mnt the non existing 4K-MOVIES-3 fictional share.

So I’m not sure how safe or stable it will be, when these weird extra shares appears.

And few minutes later, many other shares became duplicated again while the Library Update is running on Vero. :rage:

Then slowly disappeared, only the original 4K-MOVIES-2 remained duplicated now, but this time I can list it and access it without any problem.

And now, the update finished, and the extra shares disappeared again…