Twice now I have lost all network access to my Unraid web interface, ssh & all VMs/Containers. The network switch shows the interface is physically connected when plugged in (and unconnected when I unplug the ethernet cable) but the only way I can recover is with a hard reset, which of course causes the array to run a parity check. I'm very new to Unraid, I can't find any error or warning other then the array parity check after booting back up. This has happened now twice within 4 days. How can/should I dig into the cause?

@Matt Elias I moved the thread to General Support where you have more chance to get actual support than in Lounge.

Please attach your diagnostics to your next post in the thread.

I have no access to any logs without doing a hard reset. I read that the diagnostic logs are reset at boot.

Edited June 27, 20242 yr by Matt Elias

Here's my main log after reboot.

main log.txt

Setup the Syslog Server to capture the file to the Flash/boot drive.  Get that after you have a lockup.

 

The request is for the diagnostics file which contains the syslog.  (Note that the underline text in forum posts usually contain a link to Unraid Documentation about the topic.)  Upload that at any time.

Edited June 27, 20242 yr by Frank1940

I am reading through the diagnostics link, I have enabled syslog now.

Reading the last paragraph in this screenshot leads me to believe that any helpful diagnostic data is lost after I reboot, which I have to do to get local or remote access to Unraid after it locks up.

tower-diagnostics-20240627-1018.zip

This is now via the web GUI after a hard reboot.

Edited June 27, 20242 yr by Matt Elias

1 minute ago, Matt Elias said:

Reading the last paragraph in this screenshot leads me to believe that any helpful diagnostic data is lost after I reboot, which I have to do to get local or remote access to Unraid after it locks up.

That is the whole point of the syslog server - it allows for the syslog entries leading up to a crash to be captured.   The paragraph refers to cases where you have a problem that has NOT caused a lockup/crash

Okay, so then I wait now until it happens again, and hopefully I can retrieve the logs. Thanks everyone for the help.

Unfortunately, I have the exact same issue. I had it just 30 minutes ago. If I get the logs, I will share them as well. Maybe it helps.

Edited June 27, 20242 yr by codingtomato

I went away for the weekend, when I came back my Unraid server was unresponsive. I powered it down by holding in the power button until it turned off. Then plugged the usb drive into my desktop. Here is the newest diagnosticstower-diagnostics-20240703-1258.zip and the syslogfile in my usb logs folder.

 

Can I immediately boot it back up?

Edited July 8, 20241 yr by Matt Elias

Here's the generated diagnostics right after booting up again.

tower-diagnostics-20240708-0828.zip

There are Macvlan call traces logged, and they will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

14 hours ago, JorgeB said:

There are Macvlan call traces logged, and they will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

I don't recall changing that, is it the default? I've changed it to ipvlan now, thanks.

It was in the past, not for some time.

On 7/8/2024 at 8:54 AM, JorgeB said:

There are Macvlan call traces logged, and they will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

So far so good after 22 days uptime.

I seem to be having the same issue, but I don't see the same "Macvlan call traces" cause within my logs. 

 

Hoping someone may be able to check my logs and give me some insight?

 

Thanks so much!

syslog-192.168.100.121.log

6 hours ago, Dunhio said:

Hoping someone may be able to check my logs and give me some insight?

Do you now the approximate time it last crashed?

Yes, July 31 at some point before 16:35 when I hard reset the server. 

My server seemed to fail again at some point before I did a hard restart at 16:04 on Aug 1, 2024.

 

New sys log attached.

syslog-192.168.100.121.log

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Ok, thanks for that insight Jorge!