Failing to mount multiple NFS shares properly

Now I’m getting the same error on both mounts.

osmc@osmc-basil:~$ sudo mount -a 
mount.nfs4: mounting 192.168.1.215:/srv/nfs4/video failed, reason given by server: No such file or directory
mount.nfs4: mounting 192.168.1.215:/srv/nfs4/video1 failed, reason given by server: No such file or directory

As I understand fstab, you should declare nfs mounts in the /etc/fstab - I still can’t see what you think might be wrong with this fstab? I have now been awake for nearly 18 hours, so I am bound to be wrong somewhere here. :slight_smile:

and the /etc/fstab file for the client:

osmc@osmc-basil:~$ cat /etc/fstab
/dev/mmcblk0p6  /boot    vfat     defaults,noatime    0   0
/dev/mmcblk0p7  /    ext4      defaults,noatime    0   0

192.168.1.215:/srv/nfs4/video /home/osmc/disk3 nfs4 rsize=8192,wsize=8192,timeo=14,_netdev 0 0 
192.168.1.215:/srv/nfs4/video1 /home/osmc/disk4 nfs4 rsize=8192,wsize=8192,timeo=14,_netdev 0 0

Reboot the server and client to make sure everything is OK right now. You’ve been making a lot of changes and may have some old mounts hanging around.

The client fstab looks OK now.

OK, after rebooting both - still the same result:

osmc@osmc-basil:~/disk4$ sudo mount -a 
mount.nfs4: mounting 192.168.1.215:/srv/nfs4/video failed, reason given by server: No such file or directory
mount.nfs4: mounting 192.168.1.215:/srv/nfs4/video1 failed, reason given by server: No such file or directory
osmc@osmc-basil:~/disk4$ showmount -e 192.168.1.215
Export list for 192.168.1.215:
/srv/nfs4/video1 192.168.1.0/24
/srv/nfs4/video  192.168.1.0/24

Why are you usinf nfs4 fstype? That is depreciated, you should use nfs as fstype and if you want to force nfs4 you set option nfsvers=4

Try this
192.168.1.215:/srv/nfs4/video /home/osmc/disk3 nfs nfsvers=4,rsize=8192,wsize=8192,udp,retrans=2 0 0

@fzinken: thanks - that’s fixed the automounting.

However, OSMC is still mounting the wrong filesystem - i.e. disk3 and disk4 have the same contents.

 osmc@osmc-basil:~$ ls -l disk3 |head
total 50485566
-rwxrwxrwx 1 root root       12415 Dec 10  2014 017FC0A5E28D5213D510FA627CA6F02BBAD360E9.meta
-rwxrwxrwx 1 root root       82537 Nov  7 10:00 0616E870BA646BF6D9A747A0BD7FD4304EC6446D.meta
-rwxrwxrwx 1 root root       14558 Aug 22  2014 061725C1C280F8494D4EC240F9C89E79988D7FDF.meta
-rwxrwxrwx 1 root root           0 Nov 17 06:02 06D5D30D72AAA9F683A6076A4CA7CA8E30D1121F.meta
-rwxrwxrwx 1 root root           0 Nov 14 06:24 092C0DFA9F7B44A4BE44B16B47D70134C9ABD83A.meta
-rwxrwxrwx 1 root root       19035 Jan 17  2014 09EE9BD74991E2D3E57F0110F1995330FD685E88.meta
-rwxrwxrwx 1 root root       15944 Mar 19 18:32 0D1E4B5FB76081D346107BF55E01FCF40A45919E.meta
-rwxrwxrwx 1 root root      108189 Mar 28  2014 140C8996BBE8C5200C4F043BFBA76EB418AC359A.meta
-rwxrwxrwx 2 root root        1024 Mar 16  2014 16GB-sd-card2.iso
osmc@osmc-basil:~$ ls -l disk4 |head
total 50485566
-rwxrwxrwx 1 root root       12415 Dec 10  2014 017FC0A5E28D5213D510FA627CA6F02BBAD360E9.meta
-rwxrwxrwx 1 root root       82537 Nov  7 10:00 0616E870BA646BF6D9A747A0BD7FD4304EC6446D.meta
-rwxrwxrwx 1 root root       14558 Aug 22  2014 061725C1C280F8494D4EC240F9C89E79988D7FDF.meta
-rwxrwxrwx 1 root root           0 Nov 17 06:02 06D5D30D72AAA9F683A6076A4CA7CA8E30D1121F.meta
-rwxrwxrwx 1 root root           0 Nov 14 06:24 092C0DFA9F7B44A4BE44B16B47D70134C9ABD83A.meta
-rwxrwxrwx 1 root root       19035 Jan 17  2014 09EE9BD74991E2D3E57F0110F1995330FD685E88.meta
-rwxrwxrwx 1 root root       15944 Mar 19 18:32 0D1E4B5FB76081D346107BF55E01FCF40A45919E.meta
-rwxrwxrwx 1 root root      108189 Mar 28  2014 140C8996BBE8C5200C4F043BFBA76EB418AC359A.meta
-rwxrwxrwx 2 root root        1024 Mar 16  2014 16GB-sd-card2.iso

I am still clueless on that but can only say it is unlikely a OSMC or client/server issue.
Provide the sudo journalctl output from both PIs and post them (best via paste.osmc.io).
And maybe also show the mounts/fstab from your notebook.

Comment out the lines on the client in fstab that mount the network drives and reboot. Then check to see what is mounted. I’m betting at this point that you have a script running at boot thats doing some mounting…