sterofuse

Diagnostics File Attached jarvis3-diagnostics-20230612-2106.zip

Hello, I am running Unraid V 6.11.5 and recently have been having an intermittent issue where my server stays powered on but loses network connections. When browsing the syslog I see the ethernet port entering a blocked and disabled state, see below: Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered blocking state Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered disabled state Jun 11 19:19:14 Jarvis3 kernel: device veth2d3ccfe entered promiscuous mode Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered blocking state Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered forwarding state Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered disabled state Jun 11 19:19:14 Jarvis3 kernel: eth0: renamed from veth749f267 Jun 11 19:19:14 Jarvis3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2d3ccfe: link becomes ready Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered blocking state Jun 11 19:19:14 Jarvis3 kernel: docker0: port 12(veth2d3ccfe) entered forwarding state Jun 11 19:19:16 Jarvis3 avahi-daemon[8377]: Joining mDNS multicast group on interface veth2d3ccfe.IPv6 with address XXXX::XXXX:XXXX:XXXX:XXXX. Jun 11 19:19:16 Jarvis3 avahi-daemon[8377]: New relevant interface veth2d3ccfe.IPv6 for mDNS. Jun 11 19:19:16 Jarvis3 avahi-daemon[8377]: Registering new address record for XXXX::XXXX:XXXX:XXXX:XXXX on veth2d3ccfe.*. IPV6 address obscured with "XXXX". This seems to happen frequently after docker updates but also happens randomly, about 2-4 times a week over the past month. My media server has a single NIC on the motherboard, my network is flat and simple and has IPV6 disabled. The server seems to stay running just fine but is completely inaccessible to the outside world after this happens. I have to use a remote smart plug to hard-shut down the server, wait a few seconds and then restore power for it to come back up in IPV4 and work like normal. Another snippet from syslog: Jun 11 19:15:20 Jarvis3 kernel: vethb050b50: renamed from eth0 Jun 11 19:15:20 Jarvis3 kernel: docker0: port 4(veth3b2b273) entered disabled state Jun 11 19:15:20 Jarvis3 avahi-daemon[8377]: Interface veth3b2b273.IPv6 no longer relevant for mDNS. Jun 11 19:15:20 Jarvis3 avahi-daemon[8377]: Leaving mDNS multicast group on interface veth3b2b273.IPv6 with address XXXX::XXXX:XXXX:XXXX:XXXX. Jun 11 19:15:20 Jarvis3 kernel: docker0: port 4(veth3b2b273) entered disabled state Jun 11 19:15:20 Jarvis3 kernel: device veth3b2b273 left promiscuous mode Jun 11 19:15:20 Jarvis3 kernel: docker0: port 4(veth3b2b273) entered disabled state Jun 11 19:15:20 Jarvis3 avahi-daemon[8377]: Withdrawing address record for XXXX::XXXX:XXXX:XXXX:XXXX on veth3b2b273. Jun 11 19:15:22 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered blocking state Jun 11 19:15:22 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered disabled state Jun 11 19:15:22 Jarvis3 kernel: device veth4204b7f entered promiscuous mode Jun 11 19:15:22 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered blocking state Jun 11 19:15:22 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered forwarding state Jun 11 19:15:22 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered disabled state Jun 11 19:15:23 Jarvis3 kernel: eth0: renamed from vethe02ded4 Jun 11 19:15:23 Jarvis3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4204b7f: link becomes ready Jun 11 19:15:23 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered blocking state Jun 11 19:15:23 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered forwarding state Jun 11 19:15:23 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered disabled state Jun 11 19:15:23 Jarvis3 kernel: vethe02ded4: renamed from eth0 Jun 11 19:15:23 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered disabled state Jun 11 19:15:23 Jarvis3 kernel: device veth4204b7f left promiscuous mode Jun 11 19:15:23 Jarvis3 kernel: docker0: port 4(veth4204b7f) entered disabled state Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered blocking state Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered disabled state Jun 11 19:15:33 Jarvis3 kernel: device veth1fb97d7 entered promiscuous mode Jun 11 19:15:33 Jarvis3 kernel: eth0: renamed from vethef0b993 Jun 11 19:15:33 Jarvis3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1fb97d7: link becomes ready Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered blocking state Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered forwarding state Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered disabled state Jun 11 19:15:33 Jarvis3 kernel: vethef0b993: renamed from eth0 Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered disabled state Jun 11 19:15:33 Jarvis3 kernel: device veth1fb97d7 left promiscuous mode Jun 11 19:15:33 Jarvis3 kernel: docker0: port 4(veth1fb97d7) entered disabled state Jun 11 19:15:45 Jarvis3 kernel: docker0: port 4(veth0243352) entered blocking state Jun 11 19:15:45 Jarvis3 kernel: docker0: port 4(veth0243352) entered disabled state Jun 11 19:15:45 Jarvis3 kernel: device veth0243352 entered promiscuous mode Jun 11 19:15:46 Jarvis3 kernel: eth0: renamed from veth2ad5914 Jun 11 19:15:46 Jarvis3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0243352: link becomes ready Jun 11 19:15:46 Jarvis3 kernel: docker0: port 4(veth0243352) entered blocking state Jun 11 19:15:46 Jarvis3 kernel: docker0: port 4(veth0243352) entered forwarding state Jun 11 19:15:47 Jarvis3 avahi-daemon[8377]: Joining mDNS multicast group on interface veth0243352.IPv6 with address XXXX::XXXX:XXXX:XXXX:XXXX. Jun 11 19:15:47 Jarvis3 avahi-daemon[8377]: New relevant interface veth0243352.IPv6 for mDNS. Jun 11 19:15:47 Jarvis3 avahi-daemon[8377]: Registering new address record for XXXX::XXXX:XXXX:XXXX:XXXX on veth0243352.*. Screenshot of my Unraid/Settings/Network Settings Attached Any help is greatly appreciated, happy to provide additional info/files, let me know what I need to provide.

Nvidia 2021-03-10 Plugin Update and reboot fixed it for me, thank you!

Welp, I need the nvidia driver so I guess I'm going to deal with a blinking cursor for a while lol.

Same issue here, I have Nerd Pack and an Nvidia 1660 Super GPU. Was working fine on 6.8.X, now with 6.9.0 all I get is blinking cursor on local monitor. Diagnostics attached. jarvis3-diagnostics-20210309-2346.zip