On Mon, 2023-10-23 at 17:40 +0200, hw wrote: > On Mon, 2023-10-23 at 16:53 +0200, Christoph Brinkhaus wrote: > > Am Mon, Oct 23, 2023 at 04:17:11PM +0200 schrieb hw: > > > Hi, > > > > > > I have an entry in the fstab to mount an NFS share via IPv6. For > > > unknown reasons, the entry is being ignored on boot, so after booting, > > > I have to log in as root and do a 'mount -a' which mounts the share > > > without problems. > > > > > > The entry in the fstab looks like this: > > > > > > > > > [fd53::11]:/srv/example /home/example/foo nfs > > > _netdev 0 0
Ok, it seems to work with: ... nfs defaults,_netdev,x-systemd.after=network-online.target 0 0 So the '_netdev' option is broken. I'll have to see if this reboot was an exception, but there's no good reason to assume that it won't work next time, too. So the next question remains: > [...] > > > So how do I force it that the entries in fstab are not being silently > > > ignored? I want these shares either mounted, like through like 3 > > > retries, or booting to stop when they can't be mounted. > > > > > I have never tried to implement things as 3x retries or so. > > Well, the retries are not so relevant; I'd expect that to happen > anyway. But how can I stop the booting when a mount fails? > > Alternatively, how can I prevent booting or have the machine becoming > inaccessible when it's not connected to a particular VLAN? Like the > users can't log in and instead get a message that the computer is > incorrectly connected ... Let me add that the machines are currently unaware that they are connected to a VLAN because the switch ports are configured untagged. I could change that to tagged but I don't see how that would solve anything. Unless maybe I could intervene before starting gdm by pinging a server and bringing up a message instead of starting gdm when the server can't be reached. That should be possible, but how would I bring up a message instead of gdm? It doesn't even have to be a GUI that's starting, just a message would suffice. After that, automatically shut down after a 2 minutes or so ...
