OMV sometimes does not connect to network after reboot

vgS83ggMyY · 24. Februar 2024

Sometimes upon restart, OMV does not connect to the local network. Typically if I restart once or twice, it will connect correctly. However, occasionally it will not be able to connect even after many restarts so I must hook up a monitor & keyboard and run omv-firstaid, reconfiguring eno1. This is a minor annoyance if I'm home, but obviously very frustrating when it occurs while I'm traveling with no physical access to my server.

This has occurred with both OMV5 and after upgrading to OMV6. I have a hardwired connection to a router.

If I run journalctl -b | grep Ethernet, I see lots of messages about eth0 renamed from vethXXXXX. I think I remember seeing a thread with a similar issue suggesting that it was caused by docker, but I don't think there was a resolution.

Can anyone suggest a solution or how to debug this? I'm pretty out of my element when it comes to networking.

Here is the output of ip addr from the last time I experienced this issue.

Code

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:25:90:ad:11:07 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
3: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:25:90:ad:11:06 brd ff:ff:ff:ff:ff:ff
4: br-b402fcb47f08: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:da:1f:63:78 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-b402fcb47f08
       valid_lft forever preferred_lft forever
    inet6 fe80::42:daff:fe1f:6378/64 scope link 
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:c9:69:81:95 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:c9ff:fe69:8195/64 scope link 
       valid_lft forever preferred_lft forever
6: br-3a6de31a5899: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:52:ab:08:8e brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-3a6de31a5899
       valid_lft forever preferred_lft forever
8: veth8352685@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether e2:29:9f:17:86:69 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::e029:9fff:fe17:8669/64 scope link 
       valid_lft forever preferred_lft forever
10: vethb4241a8@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b402fcb47f08 state UP group default 
    link/ether 56:4d:92:f5:86:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 6
    inet6 fe80::544d:92ff:fef5:86c5/64 scope link 
       valid_lft forever preferred_lft forever
12: veth20591ec@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether 0a:86:eb:b3:63:19 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::886:ebff:feb3:6319/64 scope link 
       valid_lft forever preferred_lft forever
14: veth4b92ce4@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether 12:62:b1:ad:4e:4a brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::1062:b1ff:fead:4e4a/64 scope link 
       valid_lft forever preferred_lft forever
16: veth30c641d@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b402fcb47f08 state UP group default 
    link/ether 62:fa:74:f6:2d:e4 brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::60fa:74ff:fef6:2de4/64 scope link 
       valid_lft forever preferred_lft forever
18: veth2da946c@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether 52:97:4c:f5:87:2f brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::5097:4cff:fef5:872f/64 scope link 
       valid_lft forever preferred_lft forever
20: veth46540a3@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether 7e:7a:c8:1b:7d:c7 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::7c7a:c8ff:fe1b:7dc7/64 scope link 
       valid_lft forever preferred_lft forever

Alles anzeigen

And here is the output of journalctl -b | grep Ethernet

Code

Feb 21 08:04:40 raekwon kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:25:90:ad:11:07
Feb 21 08:04:40 raekwon kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Feb 21 08:04:40 raekwon kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Feb 21 08:04:40 raekwon kernel: e1000e 0000:00:19.0 eno1: renamed from eth0
Feb 21 08:06:43 raekwon kernel: eth0: renamed from vethb317d86
Feb 21 08:06:43 raekwon kernel: eth0: renamed from veth579fc1b
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered blocking state
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered disabled state
Feb 21 08:06:43 raekwon kernel: device veth02a855d entered promiscuous mode
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered blocking state
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered forwarding state
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered disabled state
Feb 21 08:06:43 raekwon systemd-networkd[420]: veth02a855d: Link UP
Feb 21 08:06:43 raekwon kernel: eth0: renamed from vethd557915
Feb 21 08:06:43 raekwon kernel: eth0: renamed from veth4335570
Feb 21 08:06:43 raekwon kernel: eth0: renamed from vethd507f40
Feb 21 08:06:43 raekwon kernel: eth0: renamed from vethbd7a85a
Feb 21 08:06:43 raekwon systemd-networkd[420]: veth02a855d: Gained carrier
Feb 21 08:06:43 raekwon kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth02a855d: link becomes ready
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered blocking state
Feb 21 08:06:43 raekwon kernel: docker0: port 5(veth02a855d) entered forwarding state
Feb 21 08:06:43 raekwon kernel: eth0: renamed from vethc699ee8
Feb 21 08:06:45 raekwon systemd-networkd[420]: veth02a855d: Gained IPv6LL

Alles anzeigen

Barney · 24. Februar 2024

Yep, I am running into this too on my OMV7 install. Had to reconfigure three times this morning. Trying to understand why.

Barney · 24. Februar 2024

OK I figured out my issue but I don't know the cause or solution.

Whenever I have to reboot OMV7 for a plugin, the network dongle may not always be acknowledged. I have to unplug/replug the dongle and then it's back. It seems like some reset or init is missing after a reboot for the dongle.

vgS83ggMyY · 9. März 2024

Unfortunately for me, unplugging/replugging has no effect. Only omv-firstaid seems to work.

chente · 9. März 2024

Zitat von vgS83ggMyY

This has occurred with both OMV5 and after upgrading to OMV6

Sometimes updates between OMV versions can cause problems. If no one else gives you a better solution I suggest using omv-regen to get a clean installation of OMV already configured. That may help.

Thema

[How to] Migrate/Restore OMV Settings to Another System with omv-regen

UTILITY TO MIGRATE OMV CONFIGURATION TO ANOTHER SYSTEM OR
DO A NEW OMV INSTALLATION AND KEEP THE SETTINGS

Si quieres leer todo esto en español puedes hacerlo en github

omv-regen

INSTALLATION:

Copy and paste the following line into a terminal and run it as root or with sudo.
sudo wget -O - https://raw.githubusercontent.com/xhente/omv-regen/master/omv-regen.sh | sudo bash

STEP 1. Create a backup of the original system with omv-regen.
STEP 2. Do a fresh installation of OMV on the disk you want and

…

chente

29. April 2023

omv-regen

INSTALLATION:

Jetzt mitmachen!