REALLY appreciate you guys helping me out with this!
Hi,
I’ve got a read only share setup the same way, the only difference in mine is that under the nfs Privilege set to read/write and using squash map to guest and the ro flag on the client side. But I don’t think that should make any difference. Please clarify the following:
- When you correct the squash, you rebooted the vero?
- The vero is on a static ip of 192.168.1.180
Thanks Tom.
Yes & Yes.
Screenshot from the router (in Danish, but you’ll get it, I think 
)
Hi,
Yep dhcp reservation
Try setting nfs Privilege read/write and then restart the vero4k.
Thanks Tom.
Still no luck.
What I don’t like is that all the original shares are still showing up when I browse to the mnt folder, but when accessing the command line I only see the “film” share. Is that normal or is kodi not communicating with the OS?
Hmmm, what I havent tried is restarting NAS, Will give that a shot…
EDIT: no luck with that either…
Hi,
I can’t reproduce this, whats the output of:
ls -lah /mnt
So you are are still getting permission denied when: cd /mnt/Film ?
It could be that the dhcp assignment from the router is not working correctly, whats the output of ifconfig ?
You could also consider trying to change Hostname or IP* under Edit NFS rule to: 192.168.1.0/24
Thanks Tom.
osmc@osmc:~$ ls -lah /mnt
total 24K
drwxr-xr-x 7 root root 4.0K Feb 4 12:02 .
drwxr-xr-x 23 root root 4.0K Jan 10 14:33 …
d--------- 1 root root 5.1K Feb 4 18:55 Film
dr-xr-xr-x 2 root root 4.0K Feb 4 12:02 Musik
dr-xr-xr-x 2 root root 4.0K Feb 4 12:02 Musikvideo
dr-xr-xr-x 2 root root 4.0K Feb 4 12:02 Serier
dr-xr-xr-x 2 root root 4.0K Feb 4 12:02 Video
changed the IP as you suggested.
Hi,
If you want film to appear when you browse the root file system, you need to remove them from mnt; aswell as the fstab entry. So for example:
sudo rmdir /mnt/Musik
If you added these locations as a source in kodi, you will need to remove them using the contect menu as advised earlier.
Did changing the IP help?
Whats output of:
sudo mount /mnt/Film
ls -lah /mnt/Film
Thanks Tom.
Changing the IP didn’t help, so I changed it back (only one mediaplayer on the network)
Thanks for the Rmdir hint - that got rid of the other shares. interestingly, I can’t remove the “film” share that way, then I get: rmdir: failed to remove ‘/mnt/Film’: Device or resource busy
sudo mount…: just a new prompt
ls -lah…: cannot open directory ‘/mnt/Film’: Permission denied
Hi,
Dilthedog just spotted this, we believe this is the cause of the problem; as the permissions are not set correctly. The easy way to fix this is:
sudo umount /mnt/Film
Comment out the fstab entry:
#192.168.1.170:/volume1/Film /mnt/Film nfs noauto,x-systemd.automount 0 0
Restart the the vero4k.
Now remove the the the Film mnt folder
sudo rmdir /mnt/Film
Now lets recreate the mnt folder:
sudo mkdir /mnt/Film
check the permissions:
ls -lah /mnt
the film entry should look something like this:
drwxr-xr-x 2 root root 4.0K Feb 4 19:35 Film
if not issue:
sudo chmod 755 /mnt/Film
Uncomment the fstab entry
192.168.1.170:/volume1/Film /mnt/Film nfs noauto,x-systemd.automount 0 0
sudo mount /mnt/Film
you should now be able to cd /mnt/Film, with no issues; please check and advise?
Then reboot, just to make sure it survives the reboot.
Thanks Tom.
Sorry, a non-native speaker and a noob to boot 
can you please explain you mean by “comment” and “uncomment” before I make matters worse 
Placing a # symbol at the beginning of the lines in fstab will cause the system to ignore them, making them only a comment. So uncommenting (removing the pound symbol) will cause the system to read and apply the line.
1 Like
Hi,
Or if you are unhappy with comments, just remove the entry and put it back in again; after /mnt/Film has been recreated with the correct permissions.
Thanks Tom.
Nope. Still out of luck, I think:
osmc@osmc:~$ sudo rmdir /mnt/Film
osmc@osmc:~$ sudo mkdir /mnt/Film
osmc@osmc:~$ ls -lah /mnt
total 12K
drwxr-xr-x 3 root root 4.0K Feb 4 21:27 .
drwxr-xr-x 23 root root 4.0K Jan 10 14:33 …
drwxr-xr-x 2 root root 4.0K Feb 4 21:27 Film
osmc@osmc:~$ sudo nano /etc/fstab
osmc@osmc:~$ sudo mount /mnt/Film
osmc@osmc:~$ cd /mnt/Film
-bash: cd: /mnt/Film: Permission denied
osmc@osmc:~$
Could this be the problem: If I go to User → Guest, the Synology keeps assigning a username/PW and I haven’t found a way to prevent this.
Hi,
NFS doesn’t use a username and password, I think it can do so by using a third party like kerberos; so I think the guest username and password is for samba/smb.
Could you please post the output off:
ls - lah /mnt
After /mnt/Films has been mounted. Also the output of:
ifconfig
Thanks Tom.
Ifconfig:
osmc@osmc:~$ ifconfig
eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
ether c4:4e:ac:11:8a:69 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 758 (758.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
eth1: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.180 netmask 255.255.255.0 broadcast 192.168.1.255
ether 00:e0:4c:0c:38:4b txqueuelen 1000 (Ethernet)
RX packets 11647 bytes 1519751 (1.4 MiB)
RX errors 0 dropped 50 overruns 0 frame 0
TX packets 3050 bytes 1103784 (1.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 4096
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 115 bytes 35287 (34.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 115 bytes 35287 (34.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ls - lah… : osmc@osmc:~$ ls - lah /mnt
ls: cannot access ‘-’: No such file or directory
ls: cannot access ‘lah’: No such file or directory
/mnt:
Film
Hi,
Sorry typo, should have been: ls -lah /mnt
Thanks Tom.
No problem - looks like this, then:
osmc@osmc:~$ ls -lah /mnt
total 8.0K
drwxr-xr-x 3 root root 4.0K Feb 4 21:27 .
drwxr-xr-x 23 root root 4.0K Jan 10 14:33 …
d--------- 1 root root 8.6K Feb 4 21:54 Film
Hi,
Ok so the nas is not passing the correct permissions, the only thing I can suggest is change the squash to: map root to admin, under Edit NFS rules on the synology. Still will be mounted read only because of the flag in the fstab entry.
Once you’ve made change reboot the vero4k.
Thanks Tom.