Troubleshooting • Re: Network mount not surviving reboot

You have noauto and x-systemd.automount in your mount options. I wouldn't expect systemd to attempt mounting it until you first try to access a file or directory below the mount point.

You also have _netdev which, at least for auto mounts, flags to systemd that mounting should not be attempted until after the network is online. I'm unsure how well that plays with x-systemd.automount if the first access attempt occurs before then.

A good starting point would be a web search for "cifs_mount failed w/return code = -101"

Another test would be to let the Pi boot then run

Code:

sudo mount /media/pishare

Unlike the manual mount in your OP that will use your fstab entry to perform the mount.

Hey, ok I had to reboot this morning and again it failed to mount. checked dmesg and same error

Code:

[    5.796376] macb 1f00100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off[   13.785807] Key type cifs.spnego registered[   13.785816] Key type cifs.idmap registered[   13.786138] CIFS: enabling forceuid mount option implicitly because uid= option is specified[   13.786141] CIFS: enabling forcegid mount option implicitly because gid= option is specified[   13.786143] CIFS: Attempting to mount //192.168.1.212/PlexMedia[   13.786194] CIFS: VFS: Error connecting to socket. Aborting operation.[   13.786198] CIFS: VFS: cifs_mount failed w/return code = -101[   14.230221] Initializing XFRM netlink socket[   14.254758] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.

I performed the

Code:

sudo mount /media/pishare

and sure enough it mounted fine. What does this mean?

Statistics: Posted by thagrol — Tue Dec 17, 2024 3:51 pm