vespaman
Guru
Joined: 28 Aug 2002
Posts: 380
Location: Stockholm, Sweden
|
 Posted: Wed Dec 25, 2024 10:20 am Post subject: nfs mount (systemd) fails during boot. |
 |
|
Hi all (merry Christmas!),
I have some problem with booting a laptop of mine - during boot, I cannot get a nfs mount point to work when I am connecting to network using wifi. This is systemd, and I simply put 'noauto' when I installed this box last spring.
I am not sure how it is supposed to work, so I figured I should ask.
This is what journalctl has to say about it;
| Code: | dec 25 10:47:25 think3 systemd[1]: systemd-rfkill.service: Deactivated successfully.
dec 25 10:47:27 think3 wpa_supplicant[494]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=SE
dec 25 10:47:27 think3 NetworkManager[461]: <info> [1735120047.3478] manager: startup complete
dec 25 10:47:27 think3 systemd[1]: Finished Network Manager Wait Online.
dec 25 10:47:30 think3 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
dec 25 10:47:43 think3 wpa_supplicant[494]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
dec 25 10:47:43 think3 wpa_supplicant[494]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
dec 25 10:47:43 think3 wpa_supplicant[494]: dbus: Failed to construct signal
dec 25 10:47:43 think3 wpa_supplicant[494]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.BSS dbus_property=RSN getter failed
dec 25 10:47:50 think3 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
dec 25 10:49:19 think3 systemd-networkd-wait-online[382]: Timeout occurred while waiting for network connectivity.
dec 25 10:49:19 think3 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
dec 25 10:49:19 think3 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
dec 25 10:49:19 think3 systemd[1]: Failed to start Wait for Network to be Configured.
dec 25 10:49:19 think3 systemd[1]: Reached target Network is Online.
dec 25 10:49:19 think3 systemd[1]: Mounting /mnt/oxygen...
dec 25 10:49:19 think3 systemd[1]: Starting Docker Application Container Engine...
dec 25 10:49:19 think3 mount[534]: mount.nfs: Network is unreachable for oxygen://home/public on /mnt/oxygen
dec 25 10:49:19 think3 systemd[1]: mnt-oxygen.mount: Mount process exited, code=exited, status=32/n/a
dec 25 10:49:19 think3 systemd[1]: mnt-oxygen.mount: Failed with result 'exit-code'.
dec 25 10:49:19 think3 systemd[1]: Failed to mount /mnt/oxygen.
dec 25 10:49:19 think3 systemd[1]: Dependency failed for Remote File Systems.
dec 25 10:49:19 think3 systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
dec 25 10:49:19 think3 systemd[1]: Starting Permit User Sessions...
dec 25 10:49:19 think3 systemd[1]: Finished Permit User Sessions.
dec 25 10:49:19 think3 systemd[1]: Started Simple Desktop Display Manager.
|
And this is how my fstab looks like;
| Code: | oxygen://home/public /mnt/oxygen nfs _netdev,auto,defaults,noatime 0 0
|
I tried first without _netdev, but I'm not sure that made any significant difference.
The way I see this, is that it might be either bad configuration of network manager (the log seems to suggest this), or something systemd (normally, my computers has systemV).
I don't remember how I configured Wifi on this machine, since it was some time ago, but it works fine after I have kde up, and then I can manually mount the nfs share. |
|
Networking & Security
