Same probleme with the modification you suggest.

root@bowser:~# cat /etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network-online.target

[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto

[Install]
WantedBy=multi-user.target
root@bowser:~# systemctl status mnt-nas.mount

● mnt-nas.mount - NAS devices
     Loaded: loaded (/etc/systemd/system/mnt-nas.mount; enabled; vendor preset: 
enabled)
     Active: failed (Result: exit-code) since Wed 2020-05-06 17:35:46 CEST; 
4min 59s ago
      Where: /mnt/nas
       What: 192.168.1.20:/volume2/media

May 06 17:35:45 bowser systemd[1]: Mounting NAS devices...
May 06 17:35:46 bowser mount[751]: mount.nfs: Network is unreachable
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Mount process exited, 
code=exited, status=32/n/a
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Failed with result 
'exit-code'.
May 06 17:35:46 bowser systemd[1]: Failed to mount NAS devices.

I also have done some more test. I only have this problem on a bare
metal installation (Lenovo M720q). If I do the same configuration on a
virtual machine, I do not have the problem. I do not have the problem
with a fedora server installation on bare metal.

I do not have enough knowledge to troubleshoot this problem but I am
fully available if you have some commands you want me to try.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876670

Title:
  nfs does not mount at boot with bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to