Hello,

 

I am having an issue where my Unraid server crashes consistently after roughly seven days of uptime, and it then requires a hard reset. The server GUI won't show up, it won't respond to pings, and nothing appears on screen on my PiKVM. I posted about this issue on Reddit, and it was suggested I post about my issue here.

 

I have been running Unraid for eight months, and this behavior started in the last couple of months.

 

I am running the latest BIOS on my ASUS B760-I motherboard, the latest version of Unraid, have run memory tests, swapped my USB thumb drive, reseated my memory and SATA cables, and tried running Unraid with Docker disabled. I have enabled and mirrored my syslog to my flash drive, but it doesn't seem to show any problem in the logs. My last line items in my syslog is always from Fix Common Problems alerting me at 4:40am that my "Syslog mirrored to flash".

 

Yesterday, after my server had been running for six and a half days, I started pinging the server from my computer, hoping that maybe I'd identify that the server dies after exactly seven days. However, it looks like my crash from yesterday evening happened at 7:02pm, which meant the server had been running for about seven days and a few hours.

 

I have not yet tried to run Unraid in Safe Mode, nor have I tried rolling back my BIOS to a version from a few months ago. Since running Unraid, I have updated my BIOS multiple times, but I believe I've made any necessary changes Unraid needs me to make.

 

As far as I can tell, there is no weekly recurring task that is causing this, and I'm not running macvlan. I've seen and read through lots of posts about people who have recurring crashes, and I've followed many of the tips I've seen. But, my problem persists, and there's something about my duration lasting about seven days that is making me wonder if that might be some kind of lead here.

 

Does anyone have any ideas here? I'm uploading my diagnostics.

 

Thanks!

 

 

node304-diagnostics-20241009-1146.zip

Enable the syslog server and post that after a crash.

2 hours ago, JorgeB said:

Enable the syslog server and post that after a crash.

 

Attaching my current and previous syslogs here.

 

I have had the syslog server running for the last many weeks, and as far as I can tell, it doesn't seem to catch anything–at least not before the server crashes. The last activity I normally see is Fix Common Problems sending me an email at 4:40am to let me know I'm mirroring my syslog to flash.

syslog syslog-previous

11 hours ago, Mitch Connir said:

and as far as I can tell, it doesn't seem to catch anything

Post a screenshot showing the settings.

7 hours ago, JorgeB said:

Post a screenshot showing the settings.

You are missing the remote syslog server, use the local server IP.

Got it. I just put the IP in and now see the syslog appearing in my "Files" folder. That said, will this syslog show different things than what was already showing on my flash drive due to having "Mirror syslog to flash" enabled?

Possibly not, but worth a try, post that one after the next crash.