systemd: failed to mount NFS share: mount.nfs: Network is unreachable until later in boot process
up vote
4
down vote
favorite
My laptop has a USB Ethernet adapter. Apparently the network doesn't come up until later in the boot process than normal. My NFS shares are not mounting at boot. However, as soon as the laptop is booted up, I can mount all shares with this command:
mount -a -t nfs,nfs4
There are no errors and everything is fine at that point. However, I would like the shares to mount at boot time automatically. Therefore, this is not an NFS configuration question. I believe this issue is related to systemd, the boot process and maybe the timing of the USB Ethernet adapter availability.
Here is everything I know to check including the relevant parts of the journal showing that the network comes up after the NFS shares have given up trying to mount. I included the relevant config files, but they have not been changed from the defaults (as far as I know).
Jul 31 21:22:32 host systemd[1]: Mounted /var/log.
...
Jul 31 21:22:33 host mount[898]: mount.nfs: Network is unreachable
...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host autossh[896]: starting ssh (count 9)
Jul 31 21:22:34 host autossh[896]: ssh child pid is 1033
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
...
Jul 31 21:22:37 host autossh[899]: ssh: connect to host 10.10.0.201 port 22: Network is unreachable
Jul 31 21:22:37 host autossh[899]: ssh exited with error status 255; restarting ssh
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3237] manager: NetworkManager state is now CONNECTING
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3487] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3492] manager: NetworkManager state is now CONNECTED_SITE
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3493] policy: set 'Wired connection 1' (eth1) as default for IPv4 routing and DNS
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3497] device (eth1): Activation: successful, device activated.
Jul 31 21:22:38 host nm-dispatcher[1017]: req:3 'up' [eth1]: new request (0 scripts)
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Tue 2018-07-31 21:22:33 EDT; 42min ago
Docs: man:NetworkManager(8)
Main PID: 792 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 33.4M
CGroup: /system.slice/NetworkManager.service
└─792 /usr/bin/NetworkManager --no-daemon
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6259] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6334] dhcp4 (eth1): state changed bound -> bound
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7755] dhcp4 (eth1): address 192.168.0.237
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): plen 24
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): expires in 300 seconds
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7757] dhcp4 (eth1): nameserver '192.168.0.1'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): domain name 'oaks'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): hostname 'host'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7759] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7769] dhcp4 (eth1): state changed bound -> bound
# systemctl status share1.mount
● share1.mount - /share1
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Tue 2018-07-31 21:22:34 EDT; 25min ago
Where: /share1
What: server:/share1/
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Jul 31 21:22:33 host systemd[1]: Mounting /share1...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
# cat /usr/lib/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Documentation=man:NetworkManager(8)
Wants=network.target
After=network-pre.target dbus.service
Before=network.target
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0
#ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/NetworkManager --no-daemon
Restart=on-failure
# NM doesn't want systemd to kill its children for it
KillMode=process
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_MODULE CAP_AUDIT_WRITE CAP_KILL CAP_SYS_CHROOT
# ibft settings plugin calls iscsiadm which needs CAP_SYS_ADMIN
#CapabilityBoundingSet=CAP_SYS_ADMIN
ProtectSystem=true
ProtectHome=read-only
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
# We want to enable NetworkManager-wait-online.service whenever this service
# is enabled. NetworkManager-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=NetworkManager-wait-online.service
# cat /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf
[Unit]
After=openvswitch.service
# cat /etc/NetworkManager/NetworkManager.conf
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
# tree /etc/NetworkManager/conf.d/
/etc/NetworkManager/conf.d/
0 directories, 0 files
# cat /usr/lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30
RemainAfterExit=yes
[Install]
WantedBy=network-online.target
Arch Linux 4.17.11-arch1 #1 SMP PREEMPT Sun Jul 29 10:11:16 UTC 2018 x86_64 GNU/Linux
KDE
UPDATE: here is the requested info regarding fstab:
All nfs mounts have these options:
nfs _netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp 0 0
I am indeed using _netdev along with systemd. After reading Filipe Brandenburger's comment, I'm not sure whether this option is meaningless under systemd or harmful.
systemctl cat share1.mount
# /run/systemd/generator/share1.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
Where=/share1
What=server:/share1/
Type=nfs
Options=_netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp
# systemctl show -p Wants network-online.target
Wants=NetworkManager-wait-online.service
(In regard to my controversial use of the soft mount option, the decision to use it was made after years of problems with the hard option. With the hard option, any loss of connectivity freezes the system and forces a hard restart. I'm running BTRFS and I do not wish to risk that. I have decided that my soft is a better fit for my situation. However, along with soft I tweaked the retrans,timeo,and retry options. I'm not sure I have them optimized, but overall the experience has been much better than with the hard option.)
networking boot systemd nfs usb-device
asked Aug 1 at 2:20
MountainX
4,9482472130
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
up vote
4
down vote
favorite
My laptop has a USB Ethernet adapter. Apparently the network doesn't come up until later in the boot process than normal. My NFS shares are not mounting at boot. However, as soon as the laptop is booted up, I can mount all shares with this command:
mount -a -t nfs,nfs4
There are no errors and everything is fine at that point. However, I would like the shares to mount at boot time automatically. Therefore, this is not an NFS configuration question. I believe this issue is related to systemd, the boot process and maybe the timing of the USB Ethernet adapter availability.
Here is everything I know to check including the relevant parts of the journal showing that the network comes up after the NFS shares have given up trying to mount. I included the relevant config files, but they have not been changed from the defaults (as far as I know).
Jul 31 21:22:32 host systemd[1]: Mounted /var/log.
...
Jul 31 21:22:33 host mount[898]: mount.nfs: Network is unreachable
...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host autossh[896]: starting ssh (count 9)
Jul 31 21:22:34 host autossh[896]: ssh child pid is 1033
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
...
Jul 31 21:22:37 host autossh[899]: ssh: connect to host 10.10.0.201 port 22: Network is unreachable
Jul 31 21:22:37 host autossh[899]: ssh exited with error status 255; restarting ssh
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3237] manager: NetworkManager state is now CONNECTING
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3487] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3492] manager: NetworkManager state is now CONNECTED_SITE
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3493] policy: set 'Wired connection 1' (eth1) as default for IPv4 routing and DNS
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3497] device (eth1): Activation: successful, device activated.
Jul 31 21:22:38 host nm-dispatcher[1017]: req:3 'up' [eth1]: new request (0 scripts)
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Tue 2018-07-31 21:22:33 EDT; 42min ago
Docs: man:NetworkManager(8)
Main PID: 792 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 33.4M
CGroup: /system.slice/NetworkManager.service
└─792 /usr/bin/NetworkManager --no-daemon
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6259] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6334] dhcp4 (eth1): state changed bound -> bound
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7755] dhcp4 (eth1): address 192.168.0.237
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): plen 24
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): expires in 300 seconds
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7757] dhcp4 (eth1): nameserver '192.168.0.1'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): domain name 'oaks'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): hostname 'host'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7759] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7769] dhcp4 (eth1): state changed bound -> bound
# systemctl status share1.mount
● share1.mount - /share1
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Tue 2018-07-31 21:22:34 EDT; 25min ago
Where: /share1
What: server:/share1/
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Jul 31 21:22:33 host systemd[1]: Mounting /share1...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
# cat /usr/lib/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Documentation=man:NetworkManager(8)
Wants=network.target
After=network-pre.target dbus.service
Before=network.target
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0
#ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/NetworkManager --no-daemon
Restart=on-failure
# NM doesn't want systemd to kill its children for it
KillMode=process
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_MODULE CAP_AUDIT_WRITE CAP_KILL CAP_SYS_CHROOT
# ibft settings plugin calls iscsiadm which needs CAP_SYS_ADMIN
#CapabilityBoundingSet=CAP_SYS_ADMIN
ProtectSystem=true
ProtectHome=read-only
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
# We want to enable NetworkManager-wait-online.service whenever this service
# is enabled. NetworkManager-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=NetworkManager-wait-online.service
# cat /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf
[Unit]
After=openvswitch.service
# cat /etc/NetworkManager/NetworkManager.conf
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
# tree /etc/NetworkManager/conf.d/
/etc/NetworkManager/conf.d/
0 directories, 0 files
# cat /usr/lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30
RemainAfterExit=yes
[Install]
WantedBy=network-online.target
Arch Linux 4.17.11-arch1 #1 SMP PREEMPT Sun Jul 29 10:11:16 UTC 2018 x86_64 GNU/Linux
KDE
UPDATE: here is the requested info regarding fstab:
All nfs mounts have these options:
nfs _netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp 0 0
I am indeed using _netdev along with systemd. After reading Filipe Brandenburger's comment, I'm not sure whether this option is meaningless under systemd or harmful.
systemctl cat share1.mount
# /run/systemd/generator/share1.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
Where=/share1
What=server:/share1/
Type=nfs
Options=_netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp
# systemctl show -p Wants network-online.target
Wants=NetworkManager-wait-online.service
(In regard to my controversial use of the soft mount option, the decision to use it was made after years of problems with the hard option. With the hard option, any loss of connectivity freezes the system and forces a hard restart. I'm running BTRFS and I do not wish to risk that. I have decided that my soft is a better fit for my situation. However, along with soft I tweaked the retrans,timeo,and retry options. I'm not sure I have them optimized, but overall the experience has been much better than with the hard option.)
networking boot systemd nfs usb-device
asked Aug 1 at 2:20
MountainX
4,9482472130
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What does your/etc/fstablook like? Are you using_netdevas a mount option?
– ErikF
Aug 1 at 2:23
2
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you runsystemctl cat share1.mount? Also,systemctl show -p Wants network-online.target(to confirm it's pulling NetworkManager and not systemd-networkd)?
– Filipe Brandenburger
Aug 1 at 3:38
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
1
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08
|
show 1 more comment
up vote
4
down vote
favorite
up vote
4
down vote
favorite
My laptop has a USB Ethernet adapter. Apparently the network doesn't come up until later in the boot process than normal. My NFS shares are not mounting at boot. However, as soon as the laptop is booted up, I can mount all shares with this command:
mount -a -t nfs,nfs4
There are no errors and everything is fine at that point. However, I would like the shares to mount at boot time automatically. Therefore, this is not an NFS configuration question. I believe this issue is related to systemd, the boot process and maybe the timing of the USB Ethernet adapter availability.
Here is everything I know to check including the relevant parts of the journal showing that the network comes up after the NFS shares have given up trying to mount. I included the relevant config files, but they have not been changed from the defaults (as far as I know).
Jul 31 21:22:32 host systemd[1]: Mounted /var/log.
...
Jul 31 21:22:33 host mount[898]: mount.nfs: Network is unreachable
...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host autossh[896]: starting ssh (count 9)
Jul 31 21:22:34 host autossh[896]: ssh child pid is 1033
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
...
Jul 31 21:22:37 host autossh[899]: ssh: connect to host 10.10.0.201 port 22: Network is unreachable
Jul 31 21:22:37 host autossh[899]: ssh exited with error status 255; restarting ssh
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3237] manager: NetworkManager state is now CONNECTING
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3487] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3492] manager: NetworkManager state is now CONNECTED_SITE
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3493] policy: set 'Wired connection 1' (eth1) as default for IPv4 routing and DNS
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3497] device (eth1): Activation: successful, device activated.
Jul 31 21:22:38 host nm-dispatcher[1017]: req:3 'up' [eth1]: new request (0 scripts)
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Tue 2018-07-31 21:22:33 EDT; 42min ago
Docs: man:NetworkManager(8)
Main PID: 792 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 33.4M
CGroup: /system.slice/NetworkManager.service
└─792 /usr/bin/NetworkManager --no-daemon
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6259] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6334] dhcp4 (eth1): state changed bound -> bound
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7755] dhcp4 (eth1): address 192.168.0.237
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): plen 24
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): expires in 300 seconds
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7757] dhcp4 (eth1): nameserver '192.168.0.1'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): domain name 'oaks'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): hostname 'host'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7759] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7769] dhcp4 (eth1): state changed bound -> bound
# systemctl status share1.mount
● share1.mount - /share1
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Tue 2018-07-31 21:22:34 EDT; 25min ago
Where: /share1
What: server:/share1/
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Jul 31 21:22:33 host systemd[1]: Mounting /share1...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
# cat /usr/lib/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Documentation=man:NetworkManager(8)
Wants=network.target
After=network-pre.target dbus.service
Before=network.target
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0
#ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/NetworkManager --no-daemon
Restart=on-failure
# NM doesn't want systemd to kill its children for it
KillMode=process
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_MODULE CAP_AUDIT_WRITE CAP_KILL CAP_SYS_CHROOT
# ibft settings plugin calls iscsiadm which needs CAP_SYS_ADMIN
#CapabilityBoundingSet=CAP_SYS_ADMIN
ProtectSystem=true
ProtectHome=read-only
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
# We want to enable NetworkManager-wait-online.service whenever this service
# is enabled. NetworkManager-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=NetworkManager-wait-online.service
# cat /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf
[Unit]
After=openvswitch.service
# cat /etc/NetworkManager/NetworkManager.conf
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
# tree /etc/NetworkManager/conf.d/
/etc/NetworkManager/conf.d/
0 directories, 0 files
# cat /usr/lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30
RemainAfterExit=yes
[Install]
WantedBy=network-online.target
Arch Linux 4.17.11-arch1 #1 SMP PREEMPT Sun Jul 29 10:11:16 UTC 2018 x86_64 GNU/Linux
KDE
UPDATE: here is the requested info regarding fstab:
All nfs mounts have these options:
nfs _netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp 0 0
I am indeed using _netdev along with systemd. After reading Filipe Brandenburger's comment, I'm not sure whether this option is meaningless under systemd or harmful.
systemctl cat share1.mount
# /run/systemd/generator/share1.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
Where=/share1
What=server:/share1/
Type=nfs
Options=_netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp
# systemctl show -p Wants network-online.target
Wants=NetworkManager-wait-online.service
(In regard to my controversial use of the soft mount option, the decision to use it was made after years of problems with the hard option. With the hard option, any loss of connectivity freezes the system and forces a hard restart. I'm running BTRFS and I do not wish to risk that. I have decided that my soft is a better fit for my situation. However, along with soft I tweaked the retrans,timeo,and retry options. I'm not sure I have them optimized, but overall the experience has been much better than with the hard option.)
networking boot systemd nfs usb-device
asked Aug 1 at 2:20
MountainX
4,9482472130
My laptop has a USB Ethernet adapter. Apparently the network doesn't come up until later in the boot process than normal. My NFS shares are not mounting at boot. However, as soon as the laptop is booted up, I can mount all shares with this command:
mount -a -t nfs,nfs4
There are no errors and everything is fine at that point. However, I would like the shares to mount at boot time automatically. Therefore, this is not an NFS configuration question. I believe this issue is related to systemd, the boot process and maybe the timing of the USB Ethernet adapter availability.
Here is everything I know to check including the relevant parts of the journal showing that the network comes up after the NFS shares have given up trying to mount. I included the relevant config files, but they have not been changed from the defaults (as far as I know).
Jul 31 21:22:32 host systemd[1]: Mounted /var/log.
...
Jul 31 21:22:33 host mount[898]: mount.nfs: Network is unreachable
...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host autossh[896]: starting ssh (count 9)
Jul 31 21:22:34 host autossh[896]: ssh child pid is 1033
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
...
Jul 31 21:22:37 host autossh[899]: ssh: connect to host 10.10.0.201 port 22: Network is unreachable
Jul 31 21:22:37 host autossh[899]: ssh exited with error status 255; restarting ssh
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3237] manager: NetworkManager state is now CONNECTING
...
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3487] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3492] manager: NetworkManager state is now CONNECTED_SITE
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3493] policy: set 'Wired connection 1' (eth1) as default for IPv4 routing and DNS
Jul 31 21:22:38 host NetworkManager[792]: <info> [1533086558.3497] device (eth1): Activation: successful, device activated.
Jul 31 21:22:38 host nm-dispatcher[1017]: req:3 'up' [eth1]: new request (0 scripts)
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: active (running) since Tue 2018-07-31 21:22:33 EDT; 42min ago
Docs: man:NetworkManager(8)
Main PID: 792 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 33.4M
CGroup: /system.slice/NetworkManager.service
└─792 /usr/bin/NetworkManager --no-daemon
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6259] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:00:59 host NetworkManager[792]: <info> [1533088859.6334] dhcp4 (eth1): state changed bound -> bound
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7755] dhcp4 (eth1): address 192.168.0.237
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): plen 24
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7756] dhcp4 (eth1): expires in 300 seconds
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7757] dhcp4 (eth1): nameserver '192.168.0.1'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): domain name 'oaks'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7758] dhcp4 (eth1): hostname 'host'
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7759] dhcp4 (eth1): gateway 192.168.0.1
Jul 31 22:03:12 host NetworkManager[792]: <info> [1533088992.7769] dhcp4 (eth1): state changed bound -> bound
# systemctl status share1.mount
● share1.mount - /share1
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Tue 2018-07-31 21:22:34 EDT; 25min ago
Where: /share1
What: server:/share1/
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Jul 31 21:22:33 host systemd[1]: Mounting /share1...
Jul 31 21:22:34 host mount[880]: mount.nfs: Resource temporarily unavailable
Jul 31 21:22:34 host systemd[1]: share1.mount: Mount process exited, code=exited status=32
Jul 31 21:22:34 host systemd[1]: share1.mount: Failed with result 'exit-code'.
Jul 31 21:22:34 host systemd[1]: Failed to mount /share1.
# cat /usr/lib/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Documentation=man:NetworkManager(8)
Wants=network.target
After=network-pre.target dbus.service
Before=network.target
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0
#ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/NetworkManager --no-daemon
Restart=on-failure
# NM doesn't want systemd to kill its children for it
KillMode=process
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_MODULE CAP_AUDIT_WRITE CAP_KILL CAP_SYS_CHROOT
# ibft settings plugin calls iscsiadm which needs CAP_SYS_ADMIN
#CapabilityBoundingSet=CAP_SYS_ADMIN
ProtectSystem=true
ProtectHome=read-only
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
# We want to enable NetworkManager-wait-online.service whenever this service
# is enabled. NetworkManager-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=NetworkManager-wait-online.service
# cat /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf
[Unit]
After=openvswitch.service
# cat /etc/NetworkManager/NetworkManager.conf
# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
# tree /etc/NetworkManager/conf.d/
/etc/NetworkManager/conf.d/
0 directories, 0 files
# cat /usr/lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30
RemainAfterExit=yes
[Install]
WantedBy=network-online.target
Arch Linux 4.17.11-arch1 #1 SMP PREEMPT Sun Jul 29 10:11:16 UTC 2018 x86_64 GNU/Linux
KDE
UPDATE: here is the requested info regarding fstab:
All nfs mounts have these options:
nfs _netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp 0 0
I am indeed using _netdev along with systemd. After reading Filipe Brandenburger's comment, I'm not sure whether this option is meaningless under systemd or harmful.
systemctl cat share1.mount
# /run/systemd/generator/share1.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=remote-fs.target
[Mount]
Where=/share1
What=server:/share1/
Type=nfs
Options=_netdev,defaults,noatime,nodiratime,soft,retrans=6,timeo=20,retry=0,rsize=32768,wsize=32768,proto=tcp
# systemctl show -p Wants network-online.target
Wants=NetworkManager-wait-online.service
(In regard to my controversial use of the soft mount option, the decision to use it was made after years of problems with the hard option. With the hard option, any loss of connectivity freezes the system and forces a hard restart. I'm running BTRFS and I do not wish to risk that. I have decided that my soft is a better fit for my situation. However, along with soft I tweaked the retrans,timeo,and retry options. I'm not sure I have them optimized, but overall the experience has been much better than with the hard option.)
networking boot systemd nfs usb-device
networking boot systemd nfs usb-device
asked Aug 1 at 2:20
MountainX
4,9482472130
asked Aug 1 at 2:20
MountainX
4,9482472130
edited Aug 1 at 5:17
asked Aug 1 at 2:20
MountainX
4,9482472130
asked Aug 1 at 2:20
MountainX
4,9482472130
asked Aug 1 at 2:20
MountainX
4,9482472130
4,9482472130
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What does your/etc/fstablook like? Are you using_netdevas a mount option?
– ErikF
Aug 1 at 2:23
2
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you runsystemctl cat share1.mount? Also,systemctl show -p Wants network-online.target(to confirm it's pulling NetworkManager and not systemd-networkd)?
– Filipe Brandenburger
Aug 1 at 3:38
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
1
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08
|
show 1 more comment
What does your/etc/fstablook like? Are you using_netdevas a mount option?
– ErikF
Aug 1 at 2:23
2
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you runsystemctl cat share1.mount? Also,systemctl show -p Wants network-online.target(to confirm it's pulling NetworkManager and not systemd-networkd)?
– Filipe Brandenburger
Aug 1 at 3:38
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
1
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08
What does your
/etc/fstab look like? Are you using _netdev as a mount option?– ErikF
Aug 1 at 2:23
What does your
/etc/fstab look like? Are you using _netdev as a mount option?– ErikF
Aug 1 at 2:23
2
2
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you run
systemctl cat share1.mount? Also, systemctl show -p Wants network-online.target (to confirm it's pulling NetworkManager and not systemd-networkd)?– Filipe Brandenburger
Aug 1 at 3:38
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you run
systemctl cat share1.mount? Also, systemctl show -p Wants network-online.target (to confirm it's pulling NetworkManager and not systemd-networkd)?– Filipe Brandenburger
Aug 1 at 3:38
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
1
1
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
If the network service is not started before mounting the file system present in /etc/fstab, the NFS mount point present in the file will fail to mount. For this reason it is recommended to add “_netdev” option for NFS file system in /etc/fstab
I would try following
mount -a -t nfs,nfs4 -O no_netdev
In addition to this, you may want to checkout this answer from "unix.stackexchange.com"
How does _netdev mount option in /etc/fstab work?
answered Aug 1 at 2:48
Nur
214
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459731%2fsystemd-failed-to-mount-nfs-share-mount-nfs-network-is-unreachable-until-late%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
If the network service is not started before mounting the file system present in /etc/fstab, the NFS mount point present in the file will fail to mount. For this reason it is recommended to add “_netdev” option for NFS file system in /etc/fstab
I would try following
mount -a -t nfs,nfs4 -O no_netdev
In addition to this, you may want to checkout this answer from "unix.stackexchange.com"
How does _netdev mount option in /etc/fstab work?
answered Aug 1 at 2:48
Nur
214
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
add a comment |
up vote
0
down vote
If the network service is not started before mounting the file system present in /etc/fstab, the NFS mount point present in the file will fail to mount. For this reason it is recommended to add “_netdev” option for NFS file system in /etc/fstab
I would try following
mount -a -t nfs,nfs4 -O no_netdev
In addition to this, you may want to checkout this answer from "unix.stackexchange.com"
How does _netdev mount option in /etc/fstab work?
answered Aug 1 at 2:48
Nur
214
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
add a comment |
up vote
0
down vote
up vote
0
down vote
If the network service is not started before mounting the file system present in /etc/fstab, the NFS mount point present in the file will fail to mount. For this reason it is recommended to add “_netdev” option for NFS file system in /etc/fstab
I would try following
mount -a -t nfs,nfs4 -O no_netdev
In addition to this, you may want to checkout this answer from "unix.stackexchange.com"
How does _netdev mount option in /etc/fstab work?
answered Aug 1 at 2:48
Nur
214
If the network service is not started before mounting the file system present in /etc/fstab, the NFS mount point present in the file will fail to mount. For this reason it is recommended to add “_netdev” option for NFS file system in /etc/fstab
I would try following
mount -a -t nfs,nfs4 -O no_netdev
In addition to this, you may want to checkout this answer from "unix.stackexchange.com"
How does _netdev mount option in /etc/fstab work?
answered Aug 1 at 2:48
Nur
214
answered Aug 1 at 2:48
Nur
214
answered Aug 1 at 2:48
Nur
214
answered Aug 1 at 2:48
Nur
214
214
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
add a comment |
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
You could also check this link, which might help you to find a solution ervikrant06.wordpress.com/2014/09/30/…
– Nur
Aug 1 at 2:50
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
Sorry, I should have mentioned in my question that I am already using _netdev in /etc/fstab. I added that mount option to all NFS shares from the beginning. Any idea why it would not have expected effect?
– MountainX
Aug 1 at 5:08
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
thanks for the link, but I'm running systemd and I don't see anything in there that applies to systemd.
– MountainX
Aug 1 at 5:10
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459731%2fsystemd-failed-to-mount-nfs-share-mount-nfs-network-is-unreachable-until-late%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What does your
/etc/fstablook like? Are you using_netdevas a mount option?– ErikF
Aug 1 at 2:23
2
According to systemd.mount(5), systemd will detect network filesystems automatically, not requiring _netdev on those. It also explains what it does for network filesystems. Can you run
systemctl cat share1.mount? Also,systemctl show -p Wants network-online.target(to confirm it's pulling NetworkManager and not systemd-networkd)?– Filipe Brandenburger
Aug 1 at 3:38
question updated with the info requested. Thanks for your interest in my question.
– MountainX
Aug 1 at 5:20
This might help askubuntu.com/a/1069863/117559
– sergej
Aug 28 at 18:56
1
systemd auto mount causes big problems on laptops which are sometimes not connected to the network where the shares are located. For example, in that situation, if you click on a mount point in the file browser, your whole system will hang. Users may not know it is a mount point, or you may click by accident, but the result is disastrous. So I don't use systemd auto mount.
– MountainX
Aug 28 at 19:08