OMV 5 no network connection after reboot

    • OMV 5.x (beta)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OMV 5 no network connection after reboot

      I've recently setup a new OMV5 installation to replace my OMV3 server that's been running now for several years. However, I am having trouble setting the IP address. I set a static address of 192.168.1.85 using the GUI, but after a reboot, there is no network connection. I have to login to the console and use omv-firstaid to reset the network connection. The system will be fine then up until a reboot.

      I've checked /etc/sytemd/network folder for the adapter entry, it looks correct:

      Source Code: /etc/systemd/network/10-openmediavault-eno1.network

      1. root@lord-yu:/etc/systemd/network# cat 10-openmediavault-eno1.network
      2. [Match]
      3. Name=eno1
      4. [Network]
      5. Address=192.168.1.85/24
      6. Gateway=192.168.1.1
      7. IPv6AcceptRA=no
      8. LinkLocalAddressing=no
      9. DNS=8.8.8.8
      10. Domains=bartserver.com
      11. [Link]
      12. [IPv6Prefix]
      Display All
      results of ip addr after reboot:

      Source Code

      1. root@lord-yu:~# ip addr
      2. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      3. link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      4. inet 127.0.0.1/8 scope host lo
      5. valid_lft forever preferred_lft forever
      6. inet6 ::1/128 scope host
      7. valid_lft forever preferred_lft forever
      8. 2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      9. link/ether fc:aa:14:2b:e4:f0 brd ff:ff:ff:ff:ff:ff
      10. 3: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      11. link/ether fc:aa:14:2b:e4:f2 brd ff:ff:ff:ff:ff:ff
      12. 4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
      13. link/ether 02:42:de:fc:d7:3b brd ff:ff:ff:ff:ff:ff
      14. inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      15. valid_lft forever preferred_lft forever
      16. 6: vethb091296@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
      17. link/ether 9a:01:07:ce:e2:1d brd ff:ff:ff:ff:ff:ff link-netnsid 0
      Display All

      results of ip addr after omv-firstaid:

      Source Code

      1. root@lord-yu:~# ip addr
      2. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      3. link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      4. inet 127.0.0.1/8 scope host lo
      5. valid_lft forever preferred_lft forever
      6. inet6 ::1/128 scope host
      7. valid_lft forever preferred_lft forever
      8. 2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      9. link/ether fc:aa:14:2b:e4:f0 brd ff:ff:ff:ff:ff:ff
      10. 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      11. link/ether fc:aa:14:2b:e4:f2 brd ff:ff:ff:ff:ff:ff
      12. inet 192.168.1.85/24 brd 192.168.1.255 scope global eno1
      13. valid_lft forever preferred_lft forever
      14. 4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
      15. link/ether 02:42:28:16:bd:fa brd ff:ff:ff:ff:ff:ff
      16. inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      17. valid_lft forever preferred_lft forever
      18. 6: vethdbc5309@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
      19. link/ether 8a:5e:23:22:45:5a brd ff:ff:ff:ff:ff:ff link-netnsid 0
      Display All

      As you can see, eno1 ip address is not set until after running omv-firsaid. Can anyone give me suggestions on what else to check?


      Thanks,

      Pete
    • Some more Diagnostics today:

      There are two network adapters on the MOBO. I tried the other one, with the same results, no network connection after reboot.

      After a reboot, running "systemctl status systemd-networkd" command results in the following output:

      Source Code

      1. root@lord-yu:~# systemctl status systemd-networkd
      2. â systemd-networkd.service - Network Service
      3. Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
      4. Active: failed (Result: exit-code) since Sat 2020-02-08 17:18:44 EST; 2min 43s ago
      5. Docs: man:systemd-networkd.service(8)
      6. Process: 466 ExecStart=/lib/systemd/systemd-networkd (code=exited, status=1/FAILURE)
      7. Main PID: 466 (code=exited, status=1/FAILURE)
      8. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Service has no hold-off time (Res
      9. tartSec=0), scheduling restart.
      10. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Scheduled restart job, restart co
      11. unter is at 5.
      12. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: Stopped Network Service.
      13. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Start request repeated too quickl
      14. y.
      15. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
      16. Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: Failed to start Network Service.
      Display All

      After running omv-firstaid and setting a static ip address to 192.168.1.85, output is:

      Source Code

      1. root@lord-yu:~# systemctl status systemd-networkd
      2. â systemd-networkd.service - Network Service
      3. Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
      4. Active: active (running) since Sat 2020-02-08 17:22:57 EST; 3min 50s ago
      5. Docs: man:systemd-networkd.service(8)
      6. Main PID: 2133 (systemd-network)
      7. Status: "Processing requests..."
      8. Tasks: 1 (limit: 4915)
      9. Memory: 2.0M
      10. CGroup: /system.slice/systemd-networkd.service
      11. ââ2133 /lib/systemd/systemd-networkd
      12. Feb 08 17:22:57 lord-yu.bartserver.com systemd[1]: Starting Network Service...
      13. Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: Enumeration completed
      14. Feb 08 17:22:57 lord-yu.bartserver.com systemd[1]: Started Network Service.
      15. Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: enp2s0: Gained carrier
      16. Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: enp2s0: Configured
      Display All
      Question is, why is it failing at startup but runs after using omv-firstaid?

      Any help is much appreciated!

      Thanks,

      Pete

      The post was edited 1 time, last by pbartko ().