Best way to mount remote shares

[rhodesda]

I’ve been accessing my QNAP shares via nfs in the kodi interface and understand this isn’t the best way to do this.

My shares are 192.168.0.80/Movies and 192.168.0.80/Kids Movies

I’ve tried the systemd method that @grahamh suggests below, is the recommended way?

[How to] Use systemd to mount remote shares

You will get better performance out of remote shares if they are mounted in OSMC’s filesystem. You can do this by putting lines in fstab as described here. But there have been reports of time-outs when OSMC is shutting down. This is probably because systemd is stopping services in the wrong order. Using systemd to mount, rather than fstab, gives us greater control. Here’s how. We are going to share a folder on server 192.168.1.11 which has a share name of ShareFolder and needs username you…

[fzinken]

@rhodesda

I’ve tried the systemd method that @grahamh suggests below, is the recommended way?

It seems the most stable also for reconnections seems to be autofs

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…

[Smurphy]

@rhodesda

I’ve been accessing my QNAP shares via nfs in the kodi interface and understand this isn’t the best way to do this.

That is not totally correct. It works very nicely out of the Box if your NAS, and your network are stable (so it happens to be here).
Best is to have a decent NAS, and Vero + NAS hooked up to Ethernet. That’s how you’ll have least problems.

From experience, using autofs/systemd etc. is done only to handle the disconnects happening from time to time in WiFi enabled environment, or unstable network/server setups.

[rhodesda]

Yeah I’m on WiFi. Occasionally the network seems to disconnect, fixed by rebooting, so thought I’d try one of the alternative methods.

[grahamh]

My vote is for autofs, these days.

[rhodesda]

@grahamh

My vote is for autofs, these days

Thanks, if I’ve already done your systemd method do I just delete the files and reboot, or do I need to run something to unmount them?

[bmillham]

Just manually unmount the fstab entries:

sudo umount /mnt/<MOUNTPOINT>

and then remove them from fstab. Or you could remove them and reboot.

[rhodesda]

Thanks, they weren’t fstab entries, I used the method in my 1st post. I’ve done the autofs thing now and rescanned, all looks good.

Thanks all

[bmillham]

@rhodesda

Thanks, they weren’t fstab entries, I used the method in my 1st post.

I didn’t read your post close enough, I thought when you mentioned systemd that you had used fstab (since fstab uses systemd). I had totally forgotten about the pure systemd method.

Definitely autofs is the way to go nowdays. I use it and it works great.

@rhodesda

I’ve done the autofs thing now and rescanned, all looks good.

You could have used path substitution instead of re-scanning, but it’s probably cleaner in the long run to have done the scan. And it makes it easier in the future to add another device with a shared library.