January 28Jan 28 New to Unraid, my server keeps shutting down about once a week and I have no idea why. Diags attached tower-diagnostics-20260128-1642.zip
February 3Feb 3 Author Whelp, it crashed again after I enabled syslog server. However no log files were saved in appdata like I had configured. Do they live somewhere else?
February 3Feb 3 Author I found it on the flash. My mistake. But I cannot see from the logs why it crashed previously. Attached. syslog-previous.zip
February 3Feb 3 Community Expert 56 minutes ago, alonm15 said:However no log files were saved in appdata like I had configured............For best results and to ensure all syslog data (including boot events) is captured, set the Remote syslog server field to your server's own IP address (the "Loopback method"), or the syslog will not be saved to the set share.This ensures syslog events are both stored locally and persist across reboots, without writing to the flash drive.
February 3Feb 3 Author Just updated! Are the logs I provided in the previous post able to tell what the crash issue was?
February 4Feb 4 Community Expert Nothing relevant logged; suggesting more of a hardware issue, but try again one more time.
February 7Feb 7 Community Expert I'm afraid still nothing, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.
February 7Feb 7 Community Expert The next suspects would be, in no particular order, board, CPU and PSU.
February 7Feb 7 Author It seems to also come right back up. So it crashes, but then the server reboots itself. Does that point to anything in particular?
February 10Feb 10 Author syslog-previous.zipI haven't done a mem test but can do that. It crashed again at some point last night/this morning. Any chance these logs have anything useful? If not I'll start swapping out hardware.
February 10Feb 10 Community Expert There are some nginx related errors, but that should not hang the server. Still, it may be worth retesting in safe mode to see if they still happen.
February 13Feb 13 Author Should I reboot and leave it in safe mode for a few days and see if it crashes? Or did you mean retest in safe mode due to the nginx errors
February 14Feb 14 Community Expert 11 hours ago, alonm15 said:Should I reboot and leave it in safe mode for a few days and see if it crashes?Worth a try
February 14Feb 14 Author Rebooted in safe mode and so far no restarts but I am now getting the same nginx error still. Error occurred over 16,000 times all with the same timestampFeb 14 00:22:53 Tower nginx: 2026/02/14 00:22:53 [error] 4653#4653: MEMSTORE:01: force-reaping msg with refcount 1
February 15Feb 15 Author Server completely froze tonight and had to be force shut down and rebooted. I do not understand what the hell is going on. This is becoming infuriating. Nothing is working. Nothing is helping. This feels like it has become an enormous waste of time and money. How is there not a single log file that shows anything helpful. How is Unraid not providing technical support. What is going on here. This exact same set of hardware has worked flawlessly for years and the minute I convert to unraid, not a single thing goes right. I am beyond frustrated. I appreciate the help of the community it trying to solve this but how the hell can this be a viable product when I can't keep a sever up for more than 48 hours.
February 15Feb 15 Community Expert 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, including the individual docker containers. Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.
February 22Feb 22 Author Another crash today. Though for whatever reason, the previous sys log did not show anything from prior to the actual crash. It just shows it starting up. So I have no idea if there were more nginx errors or not. Double checked my Syslog server and it seems setup correctly but still no logs from prior to the crash. just the crash itself. The strange part is, the server comes RIGHT back online. I don't have to go power it up. It crashes, then automatically restarts itself which seems to rule out a hardware issue. The PSU is now brand new and still the same issue.
February 22Feb 22 Community Expert 21 minutes ago, alonm15 said:Syslog server and it seems setup correctlyPost a screenshot of those settings
February 22Feb 22 Community Expert 22 minutes ago, alonm15 said:It crashes, then automatically restarts itself which seems to rule out a hardware issue.Don't know why you would think that.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.