Ive had this issue for a while now where my eth0 keeps going offline. theres no set time it does it, sometimes its after a few minutes, sometimes its after a day, sometimes its after a week. Unplugging and replugging cable kicks it back online sometimes, and sometimes doing so doesnt help. The system eventually goes into full deadlock where it isn't even possible to log into via terminal so I could dump the diagnostics... See pictures and following log (luckily i have syslog written to drive).20240109_095526.heic20240109_095432.heic20240109_095413.heic20240109_095328.heic

syslog-192.168.200.8(5).log

The only fool proof fix is to restart the entire system.

 

 

My system

unraid 6.12.6 
cpu: 3900x

mem: 64GB 3200 corsair vengence

mb: gigabyte x570 master

eth0: ConnectX-3 10GBE SFP

eth2: 2.5ghz onboard Ethernet (backup line so i can access unraid in event eth0 goes down.)



 

Jan  8 00:03:15 Megavault rc.inet1: ip link add name br0 type bridge stp_state 0 forward_delay 0
Jan  8 00:03:15 Megavault rc.inet1: ip link set br0 up
Jan  8 00:03:15 Megavault rc.inet1: ip link set eth0 master br0 up
Jan  8 00:03:15 Megavault kernel: br0: port 1(eth0) entered blocking state
Jan  8 00:03:15 Megavault kernel: br0: port 1(eth0) entered disabled state
Jan  8 00:03:15 Megavault kernel: br0: port 1(eth0) entered blocking state
Jan  8 00:03:15 Megavault kernel: br0: port 1(eth0) entered forwarding state
Jan  8 00:03:16 Megavault rc.inet1: polling up to 60 sec for DHCP server on interface br0
Jan  8 00:03:16 Megavault rc.inet1: timeout 60 dhcpcd -w -q -n -p -t 10 -h Megavault -4 br0
Jan  8 00:03:16 Megavault dhcpcd[1808]: br0: soliciting a DHCP lease
Jan  8 00:03:16 Megavault dhcpcd[1808]: br0: offered 192.168.200.8 from 192.168.200.1
Jan  8 00:03:16 Megavault dhcpcd[1808]: br0: probing address 192.168.200.8/24
Jan  8 00:03:21 Megavault dhcpcd[1808]: br0: leased 192.168.200.8 for 7200 seconds
Jan  8 00:03:21 Megavault dhcpcd[1808]: br0: adding route to 192.168.200.0/24
Jan  8 00:03:21 Megavault dhcpcd[1808]: br0: adding default route via 192.168.200.1
Jan  8 00:03:21 Megavault network: hook services: interface=br0, reason=BOUND, protocol=dhcp
Jan  8 00:03:21 Megavault rc.inet1: ip link set br0 up
Jan  8 00:04:53 Megavault root: Interface "br0" added with 10000 Mbit bandwidth limit.
Jan  8 00:04:53 Megavault vnstatd[5329]: Monitoring (7): tunl0 (no limit) eth2 (2500 Mbit) eth1 (no limit) eth0 (10000 Mbit) br2 (2500 Mbit) br1 (no limit) br0 (10000 Mbit) 
Jan  8 00:05:10 Megavault avahi-daemon[9981]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.200.8.
Jan  8 00:05:10 Megavault avahi-daemon[9981]: New relevant interface br0.IPv4 for mDNS.
Jan  8 00:05:10 Megavault avahi-daemon[9981]: Registering new address record for 192.168.200.8 on br0.IPv4.
Jan  8 00:05:32 Megavault avahi-daemon[16671]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.200.8.
Jan  8 00:05:32 Megavault avahi-daemon[16671]: New relevant interface br0.IPv4 for mDNS.
Jan  8 00:05:32 Megavault avahi-daemon[16671]: Registering new address record for 192.168.200.8 on br0.IPv4.
Jan  8 00:05:42 Megavault root: Error response from daemon: network with name br0 already exists
Jan  8 00:05:42 Megavault rc.docker: connecting pihole to network br0
Jan  8 00:05:42 Megavault rc.docker: connecting NginxProxyManager to network br0
Jan  8 00:05:42 Megavault rc.docker: connecting Nextcloud to network br0
Jan  8 00:05:42 Megavault rc.docker: connecting RustDeskServer-AiO to network br0
Jan  8 00:05:43 Megavault dnsmasq-dhcp[19788]: DHCP, sockets bound exclusively to interface virbr0
Jan  8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered blocking state
Jan  8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered disabled state
Jan  8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered blocking state
Jan  8 00:05:44 Megavault kernel: br0: port 2(vnet0) entered forwarding state
Jan  8 00:06:19 Megavault kernel: br0: port 1(eth0) entered disabled state
Jan  8 00:10:00 Megavault vnstatd[5329]: Detected bandwidth limit for "br0" changed from 10000 Mbit to 10 Mbit.
Jan  8 01:48:21 Megavault dhcpcd[1808]: br0: failed to renew DHCP, rebinding
Jan  8 02:03:21 Megavault dhcpcd[1808]: br0: DHCP lease expired
Jan  8 02:03:21 Megavault dhcpcd[1808]: br0: deleting route to 192.168.200.0/24
Jan  8 02:03:21 Megavault dhcpcd[1808]: br0: deleting default route via 192.168.200.1
Jan  8 02:03:21 Megavault dhcpcd[1808]: br0: soliciting a DHCP lease
Jan  8 02:03:26 Megavault dhcpcd[1808]: br0: probing for an IPv4LL address
Jan  8 02:03:32 Megavault dhcpcd[1808]: br0: using IPv4LL address 169.254.208.156
Jan  8 02:03:32 Megavault dhcpcd[1808]: br0: adding route to 169.XXX.XXX.0/16
Jan  8 02:03:32 Megavault dhcpcd[1808]: br0: adding default route
Jan  8 02:03:32 Megavault network: hook services: interface=br0, reason=IPV4LL, protocol=ipv4ll
Jan  9 06:28:15 Megavault kernel: br0: port 1(eth0) entered blocking state
Jan  9 06:28:15 Megavault kernel: br0: port 1(eth0) entered forwarding state
Jan  9 06:28:32 Megavault dhcpcd[1808]: br0: offered 192.168.200.8 from 192.168.200.1
Jan  9 06:28:32 Megavault dhcpcd[1808]: br0: probing address 192.168.200.8/24
Jan  9 06:28:37 Megavault dhcpcd[1808]: br0: leased 192.168.200.8 for 7200 seconds
Jan  9 06:28:37 Megavault dhcpcd[1808]: br0: adding route to 192.168.200.0/24
Jan  9 06:28:37 Megavault dhcpcd[1808]: br0: changing default route via 192.168.200.1
Jan  9 06:28:37 Megavault network: hook services: interface=br0, reason=BOUND, protocol=dhcp
Jan  9 06:28:37 Megavault dhcpcd[1808]: br0: deleting route to 169.XXX.XXX.0/16
Jan  9 06:28:37 Megavault network: hook services: interface=br0, reason=IPV4LL, protocol=ipv4ll
Jan  9 06:30:30 Megavault vnstatd[5329]: Detected bandwidth limit for "br0" changed from 10 Mbit to 10000 Mbit.

 

megavault-diagnostics-20240109-0644.zip

Edited January 9, 20242 yr by acoop133

this effect may happen if flow control does not work correctly. Usually a transmission problem. The card gets the "Shut up!" packet but the "You may continue!" order is lost in transmission somehow. The port is blocked this way, usually until the cows come home.

 

Un-/Replugging resets the state usally. But if the line is bad, it will happen again sooner or later.

 

So in general: CHECK YOUR CABLES!!!

(hint: even Direct Attached lines can fail!)

 

On 1/9/2024 at 7:25 AM, MAM59 said:

this effect may happen if flow control does not work correctly. Usually a transmission problem. The card gets the "Shut up!" packet but the "You may continue!" order is lost in transmission somehow. The port is blocked this way, usually until the cows come home.

 

Un-/Replugging resets the state usally. But if the line is bad, it will happen again sooner or later.

 

So in general: CHECK YOUR CABLES!!!

(hint: even Direct Attached lines can fail!)

 

so i disabled transmission container and yeah, it seems to stopped the issue.

shouldnt that mean the cable is fine and its transmission being sucky?

Sep 15 16:10:00 unRAIDTower vnstatd[4586]: Detected bandwidth limit for "br0" changed from 10 Mbit to 1000 Mbit.

 

Got the same today...any progress with it?

anyone?

Try replacing the cable and/or using a different switch port.