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 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:

    results of ip addr after reboot:

    results of ip addr after omv-firstaid:

    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?



  • 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:

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

    Question is, why is it failing at startup but runs after using omv-firstaid?

    Any help is much appreciated!



  • Same thing here, after every huge update (like new kernel), OMV 5 lost network (no more interface available) and can only be set up back using omv-firstaid.

    Any idea?

    WebUI got good network configuration.

    No exotic hardware.

    Maybe it is related to docker install but no sure.

  • I didn´t solve this issue at my setup. sometimes wifi works sometimes not and this is not due to my router setup. As I don´t have mood at the moment to dive into linux stuff I chose the ethernet connection which works great out of the box... but wifi is the issue so far

  • I am still facing this issue and for me it is link to dhcpcd and docker.

    But unable to find root cause and to confirm, two majors impacts are:

    • omv lost network after any kernel or docker update and a reboot. Only omv-firsaid can solve it, sad for a headless server.
    • docker locates network configuration into containers in default bridge mode. It generates docker internal DNS issue.

    FYI docker issue 488

    Any idea on it? don't wanna run a new OMV5 full install with all configuration

    Config : OMV5 running headless on J5005 motherboard, dual HDD as storage and SDD with BOOT, OS and DATA partitions
    + behind router with static NAT/IP and duckdns/NO-IP

    + docker and portainer installed from OMV plugin with multiple docker compose stacks (bazarr, duckdns, duplicati, glances, heimdall, jackett, letsencrypt, ombi, openvpnas, plex, pyload, radarr, rdesktop, sonarr, tautulli, ..)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!