I'm using Unraid 6.12.15 and from time to time, completely at a random interval which ranges from 24 hours to a whole week, I'm unable to access the server IP. I've tried restarting the router and replacing the Ethernet cable, but the only thing that works when that happens is a hard reboot.

Since I can't access the server until after rebooting, the only diagnosis file that I can attach is just after the restart.

 

On a side note, I've noticed that the connection is never lost when a VM is running. This does not mean that it can't happen, but for about a couple of months it never occurred while a VM was running.

 

This is becoming a huge problem and I would appreciate a lot if someone could point me in the right direction to fix this problem.

Thanks in advance for your help. 

impvault-diagnostics-20250403-0856.zip

Edited April 3, 20251 yr by impoftheperverse

Enable the syslog server and post that after it happens again.

On 4/3/2025 at 12:00 PM, JorgeB said:

Enable the syslog server and post that after it happens again.

 

Thanks, JorgeB. I'll do that and share the diagnostics when the error happens again.

After two months of random disconnections, ever since I enabled the syslog server (mirror to flash) it did not happen again (3 weeks and running). Does this make any sense? Should I disable syslog server and see what happens or it is 100% certain that it can't have anything to do with it and it's not worth the try?

Unlikely that the syslog server being enabled has any effect on that, but you can try disabling it.

After those marvelous 3 weeks that the random crash did not happened, it's going on again every couple of days.

I managed to gather some of the syslog-previous from just after the crash/unresponsive/unreachable status. Is there any information I should hide from the syslog files before posting here?

Thanks!

11 hours ago, impoftheperverse said:

Is there any information I should hide from the syslog files before posting here?

There shouldn't be.

Thanks, Jorge. Here are the 3 syslog files that were stored in the USB after each time the server became unreachable.

After the last time I posted I followed a post you wrote somewhere else about this problem happening with Raizen CPUs (which is my case). I changed the BIOS settings (as per your advice) and for now the server has been up and running without an issue. However, still I'd like to know if there's something in the log which can point at a different issue... just to close this chapter which has been going on for a long time. Thanks!

syslog-previous syslog-previous2 syslog-previous3

Nothing obvious that I can see.