Unreliable mount of network drive, through fstab

WillemH

I can't get my nfs mount to reliably connect at boot. Could any one please advice?
3 out of 10 boots or so, the network drive will not mount; and the only way to get it mounted is to do a reboot, or to do a

sudo mount -t nfs etc.`

current relevant fstab entry:

`` xyz.xyz.xyz.xy:/home/pi/SSD2TB /home/willemh/SSD2TB nfs _netdev,x-systemd.after=network-online.target,noauto,x-systemd.automount
`
Normally it is enough to put "defaults" as the mount option in fstab, but not with Neptune.
Is there a recommended option to add?

Neptune 7.5; Linux willem-neptune 5.18.0-0.deb11.3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.14-1~bpo11+1 (2022-07-28) x86_64 GNU/Linux

Operating System: Neptune 7.5
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.18.0-0.deb11.3-amd64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 3.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

02:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)
        Subsystem: Lite-On Communications Inc Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [11ad:08a6]
        Kernel driver in use: ath10k_pci

leszek

WillemH The x-systemd.after=network-online is also what I use and it works fine. Could it be that you need to specify a special nfs version eventually?

WillemH

Thanks, leszek .

I don't think that's likely - I can mount without problems when I use BunsenLabs, Xubuntu, or Ubuntu, in which distributions I only need to specify "defaults" in sftab.

I have now also installed Kubuntu, to see how that behaves; and Kubuntu has the same problem as Neptune: unreliable mounts at boot... Not sure what this signifies, though.
A sudo mount -a after boot does mount without fail.

I'll have a think; perhaps I'll see if I can get autofs to work reliably...

leszek

WillemH x-systemd.automount should only mount the drives on first access with the dolphin file manager I think. Maybe try that out. In general only the x-systemd.after=network-online.target should be necessary and the noauto option indicates it not automounting at all.

WillemH

leszek Indeed, x-systemd.automount, seems to be doing the trick - I rebooted twice and the mount succeeded both times. I'll leave it at that for now, and see what the mileage is, that I get. Thanks!