You are not logged in.
Hello,
has anyone encountered the problem too?
In Daedalus I had entries in /etc/fstab to mount NFS shares from the server at boot, and this worked fine.
No longer in Excalibur. I have tried with OpenRC / Excalibur. I couldn't solve the problem with mount-options nor with sysv-init. Upgrade, Fresh Install, fiddling... no success.
I have to mount (sudo mount -a) after login to access my files.
Just curious..... any hint is appreciated. Thanks.
Offline
I gave up using fstab to mount nfs shares a few years ago. I think it was because of problems if the server or the client rebooted. I use autofs now. It auto-mounts the share when you access the share. Simple config desribed here: https://dev1galaxy.org/viewtopic.php?pid=58917#p58917
I use these options in /etc/export. It looks like I added 'sync' either in daedalus or excalibur. (I don't have a daedalus to check right now.)
(rw,sync,no_subtree_check,crossmnt)Offline
Me too. I don't use fstab, I wrote a cron script that is executed @reboot on the clients. My setup is a bit special anyhow. The server is shut down at nigth when all clients are off, and woken up in the morning by the first client in the morning. It checks if the network is available, if the server can be pinged, if the shares have been setup. Then the shares are mounted on the client(s). Server and clients are encrypted, the server is on a RAID6.
Online
@Andre4freedom: please show the error log, from the boot with fstab set up as in your daedalus. (It's awfully hard to just guess)
Probably logged to /var/log/dmesg and/or /var/log/syslog.
Offline
Thank you for your reaction, Ralph.
Of course, I have searched the files (dmesg and syslog) for these problems and found not a hint.
I could never get that autofs-thing to work, only a tiny part of it. Sometimes.... So I postpone my research.
I have temporarily switched to Linux Mint. There /etc/fstab still works correctly.
BTW: Daedalus did not show the problem, only excalibur.
I will pick up the task again, later.
I tried with these help-files:
https://thelinuxcode.com/mount-filesyst … ng-autofs/
https://cloudspinx.com/how-to-automatic … th-autofs/
Offline
@ralph.ronnquist
I could install excalibur on a spare machine.
Excalibur-openrc-cinnamon-nfs-common
I have extracted 3 log files: dmesg, syslog, boot
Where can I post or send this files?
I found no hints in them at all.
NB, the same problem again, no NFS resource is mounted at boot. But,
sudo mount -a mounts the all
Thanks for your efforts.
Offline
Without logs, crystal ball says boot service ordering issue - i.e. netmount runs before network is up. Especially likely if using some newfangled network "manager" rather than ifupdown.
Where can I post or send this files?
Any pastebin or fileshare service that isn't obnoxious... or just use pastebinit.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Offline
@steve_v : Thank you.
I have tried my luck to upload some files. You can find them here (hopefully):
(dmesg):
https://pastebin.com/V3iQa77z
(fstab):
https://pastebin.com/HiGjWMAj
(hosts):
https://pastebin.com/hX8evCQY
(syslog):
https://pastebin.com/UvuWqyVw
(boot-log):
https://pastebin.com/s6tumGik
Thank you for volunteering into that mystery.
Sincerely, Andre4Freedom
Offline
Tue Nov 4 17:25:19 2025: Starting network connection manager: NetworkManager.
I suspected as much.
The traditional ifupdown setup runs /etc/network/if-up.d/mountnfs to scan fstab once the network interface is up.
I don't have a Devuan install with NetworkMangler to check, but IIRC NM should call the same via /etc/NetworkManager/dispatcher.d/01-ifupdown...
Which is suspiciously absent in the Excalibur package.
Poking about...
network-manager (1.44.2-2) unstable; urgency=medium
NetworkManager or rather NetworkManager-dispatcher will no longer execute
ifupdown hook scripts from /etc/network/if-*.d/ on network state changes.Packages that want to be notified and react on such network state changes
are advised to ship native NetworkManager scripts in
/usr/lib/NetworkManager/dispatcher.d.Users may provide local hook scripts or override package provided ones by
installing those into /etc/NetworkManager/dispatcher.d.For further information about the NetworkManager-dispatcher interface see
the NetworkManager-dispatcher(8) man page.-- Michael Biebl <biebl@debian.org> Wed, 18 Oct 2023 13:55:54 +0200
I don't use the thing myself, perhaps someone who does might explain how mountnfs is intended to be called by NM now (sans systemd, which would otherwise handle all this)? I dont see a new dispatcher hook file in initscripts (which provides /etc/network/if-up.d/mountnfs), or the Excalibur network-manager package itself.
@ralph.ronnquist: Unless I'm missing some other mechanism, I don't see how the setup in Excalibur is going to work as packaged, at least without a bunch of (somewhat arcane) end-user shenanigans creating a new hook to call mountnfs.
NFS in fstab isn't unusual and should really work OOTB for the default desktop install, was this configuration tested prior to release?
Last edited by steve_v (Today 12:21:27)
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Offline
Thank you, steve_v and ralph.ronnquist!
That shows that something is wrong with the default setup.
I will try to find a solution (not sure if I'm up to it).
When and if solved, I will let you know, and post the solution.
Have a good day, andre4freedom
Offline