You asked the right question! Thank you so much!!! 
After setting it back to on, the mounting and auto updating of my library worked like a charm again.
Didn’t even have that setting in mind. It seems that it had been set as the mounts and the auto updating used to work… Maybe the Stretch test build reset that setting to off. 
What is the default state of this setting? If it’s off, it sould definitely be on in my oppinion!
Glad it worked. It makes sense to have Wait for Network on when you have a remote library but probably not otherwise.
FWIW, I enabled library update on startup on my vero and didn’t have any issues. I think that’s because I have
in my systemd unit file. I believe you can put similar options in an fstab line but haven’t tried it.
Well, the library files are located on my Vero, but the music and video files are on the NAS which isn’t so remote - it’s in the same network.
What would be the downside of having “waiting for network” on by default? If there’s no network or it’s unavailable no service would be starting until a network is available? Or is it just stopping services which need a network/internet connection?
Yeah, maybe this would be an option. The problem is: FSTAB did work before, so I never dug deeper into how it works and what can be configured. Also now, I didn’t really understand a lot when I looked for guides on how NFS and FSTAB work in general. My Linux knowledge is very limited…
Maybe someone could write a wiki entry not only for FSTAB mounts, but especially for NFS FSTAB mounts explaining what commands (like defaults,x-systemd.automount,noauto) actually do and which are useful to add… This would be awesome! 
I there is no network, a 1-minute delay in starting kodi
Well, that’s a big downside Could a setting just for library auto updating be useful here? Under “auto update library on startup” something like: wait for network to be ready before starting library auto update service
This option could be on by default and not interfere with the general “wait for network” option under MyOSMC - and the downsides of that one being turned on by default.
Might that be possible and a good idea, @sam_nazarko?
I’m not sure whether that’s something that can be done trivially.
Kodi’s ability to detect network connectivity is not always reliable; and we may end up blocking or waiting unnecessarily.
I see… That’s a bummer.
Is this option something that can be added to a NFS FSTAB mount, too? This would solve the issue, too, I guess. And “wait for network” under MyOSMC could be turned off again.
I don’t see how that would help. You won’t be able to do anything with kodi without access to your media so might as well use the setting already there in MyOSMC.
It could go in the wiki article when you have given us the first draft 
I’m a bit late to this thread, but x-systemd.automount should try to mount the share once it’s been accessed - and it’s not usually an issue that the network comes up a bit late.
I have a hunch that some of the other /etc/fstab options, notably soft and timeo, might be conflicting with x-systemd.automount. Setting “Wait for network” might work but it’s probably just side-stepping the underlying problem.
intr in /etc/fstab is ignored after kernel 2.6.25.
It just made sense in this scenario we’re talking about, because it seems to be issue - the library updating service not waiting for the network to be ready. But if it can be solved differently, obviously that would be the way to go. My point just is: the “wait for network” under MyOSMC sounds a lot more general and basic than what I proposed and doesn’t really make sense in this scenario either.
I see 
I could try… But as I said, I don’t understand FSTAB or NFS at all (and I couldn’t manage to do so until now). Would it be a good idea to have someone write a wiki entry who doesn’t understand what he’s writing about? 
But if I get help with it from others who can provide me with a list of commands one can use with NFS FTSAB mounts and what they do in which scenario, I’d be willing to do the typing…
Well, that was what I was asking before… Could someone tell me whether my FSTAB line itself is the problem. I don’t know
So, that I can take out of my line?
Let’s keep it simple:
192.168.10.26:/nfs /mnt/MyBookLive_HH nfs noauto,x-systemd.automount 0 0Ok, I’ll try that… No “soft” needed?
Just that line.
So, I changed the line and turned off “wait for network” again: Seems to be working now as it should.
Kool. Sometimes less is more.
Yep, you were right as well. But I’m happy to have gone a bit deeper into the issue… There’s always something to learn.
Thank you all for your patience! 
When there’s time, I’ll take the wiki tutorial by @bmillham (Configuring fstab based Samba share mounts) as a basis for a slightly changed second one for fstab based NFS share mounts, if that’s ok with him…
That’s fine with me 
Hello.
I also bumped into this problem this morning. After the October update reboot I realised that some of my smb mounts did not mount properly. So, the fstab file looks like that:
//192.168.1.3/media/TOSH/Movies /mnt/TOSHMovies cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/TOSH/TVShows /mnt/TOSHTVShows cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/EXT4/Movies /mnt/EXT4Movies cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/EXT4/TVShows /mnt/EXT4TVShows cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/WDPP/Movies /mnt/WDPPMovies cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/WDPP/TVShows /mnt/WDPPTVShows cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/EXT4/Music /mnt/EXT4Music cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
//192.168.1.3/media/EXT4/OSMC /mnt/OSMC cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=xxxx,password=xxxx,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770 0 0
Everything mounts properly, except EXT4TVShows and WDPPTVShows. Please, notice that EXT4Movies and EXT4TVShows are on the same NAS (192.168.1.3) and even on the same disk (EXT4), but EXT4Movies mounts normally on startup while EXT4TVShows does not. If I manually mount /mnt/EXT4TVShows everything is ok. Ditto for WDPPTVShows.
The other workaround that seems to solve the issue is to disable “update library on startup”, as already mentioned in a post above.
I have used Configuring fstab based Samba share mounts for setting up fstab with no deviation in the “options” and beyond the fore-mentioned problem everything works as expected.
Should I change something in the fstab line?
Thanks.
Just bumping this as I had a successful fstab automount on my Vero 4k to my Synology NAS that has been working very well for the last 18 months or more. Used the simple fstab lines as per the Wiki and this post.
3 days ago tho, it went tits up and stopped mounting/I lost access to my share. I had changed nothing … although it is possible my Synology had auto-updated some settings. I’m not sure if NAS performance was possibly factor.
Anyway, after a few hours searching the forums, came across this thread. Toggled the wait for network setting on the Vero 4k and it is now working again. Thx for the solution.