You are not logged in.
Hi,
I'm posting as I'm a little bit confused and did not know where to search further for my issue.
Here is the context:
I decided to reinstall my computer from scratch and use from the begining a pure systemd system.
I use netcfg with a fixed ip address in a profile.
My fstab mount 4 shares on a synology 1511+ and of them is especialy important for me as it's the /home ![]()
During the boot process I see red and yelow color complaining about the nfs mount share (but it's too fast and I can't read it).
The result is; when I log in, there is no nfs mount at all but if I run a 'mount -a' command, everything is here without any problem.
In my understanding it's as if the network is bringing up after systemd tries to mount fstab shares. I'm pretty sure that it's possible to force the network up before fstab but I do not know where to find the information.
Did someone have an idea?
Last edited by beber75 (2012-09-04 20:03:16)
Offline
Everything that you see during boot up is in systemd's journal, so don't worry about it scrolling too fast. The error messages there should be enough for you to sort it out.
FWIW my NFS shares work fine under systemd, and I'm also using netcfg with static ip.
Offline
Hi,
thanks tomk.
After consulting 'journaltcl' it appears that I havent installed 'rpcbind' and I needed to add the 'nolock' option on my nfs mount.
Currious about the 'nolock' option as it's the first time it requires it. I was using it with only 'defaults' option for monthes.
Regards
Offline