February 25Feb 25 Good afternoon All,I recently upgraded to 7.2.4 and my Unraid server keeps crashing. I had a BTRFS issue and fixed that when I was on 7.2.3 and since I did that there were no crashes. Now it crashes on 7.2.4. I have posted the support logs. Can someone please help me figure out why. I have plenty of ram and CPU cores available. I have docker service only and the applications have pinned cpu cores. Any help is greatly appreciated.Thank you. tower-diagnostics-20260225-1610.zip
February 25Feb 25 Author 3 minutes ago, trurl said:I already have the c-states disabled and also not over clocking anything, you can see it also on the go file. This was not happening before on 7.2.3. Also, the motherboard has not been touch since I got Unraid on the v6. Never had an issue on locking up till now. Did you see something on the logs that would point you that it could be a ryzen issue? Edited February 25Feb 25 by Tucubanito07
February 25Feb 25 Community Expert 7 minutes ago, Tucubanito07 said:Did you see something on the logs that would point you that it could be a ryzen issue?no
February 26Feb 26 Community Expert 4 hours ago, Tucubanito07 said:I had a BTRFS issue and fixed that when I was on 7.2.3 and since I did that there were no crashes.Now it crashes on 7.2.4.What happens if you rollback?
February 26Feb 26 Author If it freezes again, I will roll back to see if that helps. I’ll let you know once I roll back. I’ll grab a before rolling back and the an after roll back in case that helps.
February 26Feb 26 Community Expert Nothing changed in the upgrade that would explain that, the kernel is exactly the same; it could be a new hardware issue
February 26Feb 26 Author It froze again. Also, I saw that I was able to see the Tower Login and place the root user but didn't let me place the password. I hit the power button on the server and now waiting to shutdown gracefully. I see that is stopping Unraid-api... and then stopping Unraid API service... and so far nothing else. Hopefully, by the time I come back it is done and something shows up on the logs. Ill upload a support file right after I get back up and running.
February 26Feb 26 Community Expert 4 minutes ago, Tucubanito07 said:I see that is stopping Unraid-api... and then stopping Unraid API service...OK, so not a total server hang, you can enable the syslog server and post that after it happens next to see if there's something there.
February 26Feb 26 Author 19 minutes ago, JorgeB said:OK, so not a total server hang, you can enable the syslog server and post that after it happens next to see if there's something there.I had already enabled syslog to go to the USB flash drive. Here is the new support file. The old one did not have the syslog server enabled. I did do it and should be on this support file. tower-diagnostics-20260226-0723.zip
February 26Feb 26 Community Expert It would be best to set the persistent syslog to save to a share, but assuming the syslog-previous covers a crash, there's nothing relevant logged there.You can try to downgrade to 7.2.3 just to confirm if it's really related to the upgrade, which I doubt.
February 26Feb 26 Author It just crashed again. Here is the before downgrading to 7.2.3. I also included the syslog that is on the share. I took off mirroring to the flash drive so it does not kill the USB and add it to a share. tower-diagnostics-20260226-1110.zip syslog-share.zip
February 26Feb 26 Community Expert I assume the crash was between these 2 lines, if so, there's nothing logged, suggesting more of a hardware issue.Feb 26 10:15:51 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 47 (18% @ 2504rpm) to: 79 (30% @ 2481rpm)Feb 26 10:46:47 Tower rc.rsyslogd: Syslog server daemon... Started.
February 26Feb 26 Author I am guessing that is when it crashed. I just downgraded and will see if it happens again.
February 26Feb 26 Author 18 minutes ago, JorgeB said:I assume the crash was between these 2 lines, if so, there's nothing logged, suggesting more of a hardware issue.Feb 26 10:15:51 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 47 (18% @ 2504rpm) to: 79 (30% @ 2481rpm)Feb 26 10:46:47 Tower rc.rsyslogd: Syslog server daemon... Started.Would you happen to know where I can look to see if is a hardware issue?
February 26Feb 26 Community Expert 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.
March 1Mar 1 Author On 2/26/2026 at 12:23 PM, JorgeB said: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.I just finished testing all 4 RAM sticks and the server keeps crashing. I bought an intel 7 265x and hopefully it stops happening. A little upgrade from my current setup. Since I am switching from one platform to another, do I need to do anything in unraid since I am going to a different platform? Edited March 1Mar 1 by Tucubanito07
March 2Mar 2 Community Expert Assuming no RAID controllers are involved, it should be plug and play, if you are passing through any PCI devices, they will likely need to be adjusted.
March 2Mar 2 Same experience, no hardware changes, since the update Unriad freezes, no problems before with 7.2.3.As soon as I find the time, i try a downgrade. Edited March 2Mar 2 by krasty
March 2Mar 2 Author I am on 7.2.3 and still freezes. So I am going intel for other reasons and see if it’s better than AMD. I have always heard Unraid works better with Intel. Let’s see if that’s the case.
March 2Mar 2 Author 3 minutes ago, krasty said:I am on Intel, Intel N100.Ohh man. Now I am not as excited for the freezing stopping. Do you have Linux server/nextcloud and upgraded to the latest version of nextcloud?
March 2Mar 2 Nope, on this hardware I only have plex and sonarr, radarr, overseerr (now seerr), which is basically my media unraid. No heavy load.
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.