Configuring fstab based NFS share mounts

Using root directory is probably not the best option. I have made /home/osmc/mnt directory for my fstab nfs mounts and all is working as expected.

Why is that?

1 Like

Simply because OSMC is set up as a user on the underlying Linux base. Sam has mentioned in the past that it is advisable to use the /home/osmc directory. I’ll see if I can dig up the post. Granted it’s from a few years ago so maybe not entirely relevant anymore. Truth of the matter is it works both ways.

That’s what matters… :wink: Fstab is an underlying process (kernel mount) anyway. You can’t even access the fstab file without root privileges. Mounting this way is already something for more experienced users and therefore going beyond normal home folder access business. Can’t see why advising to not work with the directory made for mounts would bring profit in any scenario :thinking:

1 Like

Agreed, if it works I’ll leave things alone. Thanks for chiming in on this.

1 Like

A post was split to a new topic: Nfs one mount, not mounting on boot

51 posts were split to a new topic: NFS mounts from fedora laptop not working

A post was merged into an existing topic: NFS mounts from fedora laptop not working

A post was split to a new topic: NFS Shares with emby

A post was split to a new topic: Fstab NFS mount, export path is

A post was split to a new topic: Fstab nfs mounts errors in logs

A post was split to a new topic: Cannot mount a NFS share

A post was split to a new topic: Unmounting FSTAB nfs

Can anyone confirm that this tutorial works at all or is there something seriously wrong with my system?

I have Win10 and Mapped Drive set to my IP ( I connect to my RaspB 3 with SSH (Putty). When I use “showmount -e IP_of_your_NAS”, nothing happens at all. I cannot even use fstab SMB because not single command will work.

Step-by-step assistance would be most generous.

Most Windows 10 OS’s lack support for NFS so this guide is not for you. I would suggest you look at the fstab based Samba thread instead.

Hi! Thanks for the guide.

All working well until testing where it says permission denied. Any thoughts? No other problems during setup.

For context - weirdly have been having same problem with vero’s gui smb method hence looking for alternative. Using the gui I am able to browse the NAS and all folders are fine except for the one I’m testing which denies permission. Has been running absolutely fine for the last year and have made no changes on the NAS for a very long time. Accidentally removed the video source path in kodi and trying to add it back has got me into this mess! Not sure if due to cache holding incorrect password etc

also - stupid question - but should the mounted share appear in the gui for scanning etc?

I would double check your settings on your NAS.

If you would like to post a log then we can take a look.

Making a system mount does not make any changes in Kodi. If you want to use that new system mount you will have to either make the mount a new source and rescan your library, otherwise you leave the old path as it was and put a path substitution in an advancedsettings.xml file to redirect from the old path to the new one.

9 posts were split to a new topic: NFS fstab issues

I am not able to mount the share, getting an error where trying the mount command

Here are the logs

"osmc@osmc:/$ sudo mount /mnt/media
mount.nfs: mount system call failed"

Can you help me? If you need more info than the log just tell me. I have done a fresh install of OSMC yeserday

Extra info

osmc@osmc:~$ showmount -e
Export list for
/c/media *

Fstab line added /mnt/media nfs noauto,x-systemd.automount 0 0

and also this

osmc@osmc:/$ sudo mount -v /mnt/media
mount.nfs: timeout set for Sun Nov 21 10:52:07 2021
mount.nfs: trying text-based options ‘vers=4.2,addr=,clientaddr=’
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options ‘vers=4.1,addr=,clientaddr=’
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed

added nfsvers=3 to fstab did the trick. I’m using an old NAS, was suspecting an issue around incompatible protocol

1 Like