Hi everyone,

 

I’m experiencing an issue where my Unraid server’s network keeps going down and back up intermittently. It happened just now around 8:50 PM on 29/03/2025. This has been occurring randomly, and I’m trying to figure out what’s causing it.

 

Some details about my setup:

• Unraid version: 7.0.1

• Network setup: using unifi flex 2.5gb switch but all other clients remain online when this happens.

• Any recent changes: i did change the ram models but is this something that could cause this? I would have thought bad ram would cause it to crash completely.tower-diagnostics-20250329-2055.zip

 

I’ve attached diagnostics from the time of the issue. If anyone can help analyze the logs or point me in the right direction, I’d really appreciate it!

 

Thanks in advance.

Please make sure that you post in the proper subforum.

This :

 

is for issues with the translations of Unraid.

I moved your thread to the proper 'General' subforum.

1 minute ago, ChatNoir said:

Please make sure that you post in the proper subforum.

This :

 

is for issues with the translations of Unraid.

I moved your thread to the proper 'General' subforum.

Apologies and thank you for moving it.

 

- removed powertop

- removed second NIC from config file.

 

will restart and continue to monitor.

Diags are after rebooting, does the server just lose the network or hang? i.e., can you still access it with a keyboard monitor when that happens?

Yes can access it using keyboard and mouse. 
It appears to sort of restart its array (VM/Docker servers also) but itself and comes back up.

 

I also uninstalled the SR-IOV plugin for more testing

Post new diags when it happens again, before rebooting.

On 3/29/2025 at 11:15 PM, JorgeB said:

Post new diags when it happens again, before rebooting.

Here you go.
It went down just now at 9.48AM 1/4/2024 (First of April 2025)

The parity check that was going on got cancelled too.tower-diagnostics-20250401-0951.zip

I couldn't access the server via network but console with keyboard and mouse I could.
 

Appears that the logs only go back to the time the server came back online.

I assume I now need to enable syslog to USB Flash so that I can capture the logs for when it happens next in a place that is persistent. 

So it just crashed again. And this is all the syslog shows right before the crash..

 

@JorgeB - Are you able to assist?

 

Apr  1 17:08:11 Tower kernel: eth0: renamed from veth77bbdde
Apr  1 17:08:11 Tower kernel: docker0: port 21(vethac00eb9) entered blocking state
Apr  1 17:08:11 Tower kernel: docker0: port 21(vethac00eb9) entered forwarding state
Apr  1 17:08:13 Tower kernel: docker0: port 21(vethac00eb9) entered disabled state
Apr  1 17:08:13 Tower kernel: veth77bbdde: renamed from eth0
Apr  1 17:08:13 Tower kernel: docker0: port 21(vethac00eb9) entered disabled state
Apr  1 17:08:13 Tower kernel: vethac00eb9 (unregistering): left allmulticast mode
Apr  1 17:08:13 Tower kernel: vethac00eb9 (unregistering): left promiscuous mode
Apr  1 17:08:13 Tower kernel: docker0: port 21(vethac00eb9) entered disabled state
Apr  1 17:09:13 Tower kernel: docker0: port 21(veth53a2953) entered blocking state
Apr  1 17:09:13 Tower kernel: docker0: port 21(veth53a2953) entered disabled state
Apr  1 17:09:13 Tower kernel: veth53a2953: entered allmulticast mode
Apr  1 17:09:13 Tower kernel: veth53a2953: entered promiscuous mode
Apr  1 17:09:14 Tower kernel: eth0: renamed from vethafb4327
Apr  1 17:09:14 Tower kernel: docker0: port 21(veth53a2953) entered blocking state
Apr  1 17:09:14 Tower kernel: docker0: port 21(veth53a2953) entered forwarding state
Apr  1 17:09:16 Tower kernel: docker0: port 21(veth53a2953) entered disabled state
Apr  1 17:09:16 Tower kernel: vethafb4327: renamed from eth0
Apr  1 17:09:16 Tower kernel: docker0: port 21(veth53a2953) entered disabled state
Apr  1 17:09:16 Tower kernel: veth53a2953 (unregistering): left allmulticast mode
Apr  1 17:09:16 Tower kernel: veth53a2953 (unregistering): left promiscuous mode
Apr  1 17:09:16 Tower kernel: docker0: port 21(veth53a2953) entered disabled state

 

3 hours ago, snz said:

Are you able to assist?

Some patience please, we are not all in the same timezone.

 

11 hours ago, snz said:

Here you go.

Those diags are after rebooting, so not much to see.

 

On 3/29/2025 at 10:15 AM, JorgeB said:

Post new diags when it happens again, before rebooting.

 

What I’ve found is the machine reboots. That’s why there is a network connectivity drop.

 

i will send you some syslog files if that helps? 
 

these are the ones written to the usb flash drive

7 minutes ago, snz said:

What I’ve found is the machine reboots.

Server rebooting by itself is almost always a hardware issue, but enable the syslog server and post that after a crash, just in case it catches something.

27 minutes ago, JorgeB said:

Server rebooting by itself is almost always a hardware issue, but enable the syslog server and post that after a crash, just in case it catches something.

Have sent the output of previous syslog file after enabling it to write to flash.

 

running memtest currently

 

I'm wondering if its its the XMP profile being enabled?

1 hour ago, snz said:

I'm wondering if its its the XMP profile being enabled?

It could be, try disabling and retest, can also be the PSU for example.

It was the psu.

replaced it.

has been up for 24 with no drops.

thanks for your support once again.