Hello,

I've noticed that ever since I had to remove a bad RAM stick earlier in September due to BTRFS errors, I've noticed that the server has started to freeze/hang like once a month now. This can be resolved by doing a hard reboot but with the increase in server freezing i'm starting to get worried. I'm hopeful that the server is just being starved out of memory and all I need to do is buy a RAM stick (hopefully prices get better lol).

I've also done a quick and dirty live memory testing with the plugin, but it did not error out right away. Obviously I will need to do a proper testing with memtest86, but I will do that once I get the chance.

Any other things I could also check? I've also done VM/Docker CPU pinning to ensure that it doesn't lock up the CPU.

bigboi-diagnostics-20251201-1254.zip

Enable the syslog server and post that after the next crash.

On 12/1/2025 at 2:00 PM, JorgeB said:

Enable the syslog server and post that after the next crash.

Well that didn't take long, as it just crashed again, I don't even think it was running anything intensive anyway.

I am running a proper memtest, but was able to grab remote Syslogs, and grabbed a snippet on when it crashed.

Based on what I can decipher, it appears to be hardware issue. I did just double check, and XMP is off, and everything else in BIOS is auto.

Still, I really hope it's not the RAM, but let's see what Memtest86 says.

crash.log

39 minutes ago, sp33dy905 said:

Still, I really hope it's not the RAM, but let's see what Memtest86 says.

Note that memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

14 minutes ago, JorgeB said:

Note that memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

Huh, that's a troubleshooting step i've not heard before, but if it comes to that I'll try it, will probably have to stop half of my containers though. Lowkey wished i spent the money for a workstation motherboard for ECC support but that's for a future upgrade.

I believe that my BIOS is also not on the latest, so will also try that first if memtest doesn't come up with something. Might as well try all troubleshooting steps.

Thanks for your suggestions so far, really appreaciate.

Edited December 4, 2025Dec 4 by sp33dy905
change though to 'so far'

It might be 7.2? Try rolling back the version. I had a similar issue with 7.2.2

https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

1 hour ago, Tristankin said:

It might be 7.2? Try rolling back the version. I had a similar issue with 7.2.2

https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

This was happening before 7.2, and it's not really happening every day for me, so I don't think it would be an OS issue.

I did do some memory tweakings, I set the speed to 2933mhz, as my memory setup is kinda weird right now (1x32GB, and 2x16), memtest86 had no errors on 1 pass, and updated the bios as well. The best probable cause is to most likely just remove the other 32gb, but with the current market not being the greatest, i dont want to spend $200+ for a single stick of 32gb, and want to keep the "64gb of RAM" setup right now.

Right now it's just to wait and see. If there's another crash, ill try just removing the lone 32gb stick.

Yeah, good idea to check hardware. I have been through the ram replacement route myself (and PSU, and sata card). My system seems particularly sensitive to crashes which forced me to stick to 6.8.3 for 5 years. 7.0.1 was the first new release that seems stable. Crashes occurred as soon as I went to 7.2.2 but I haven't tried the versions between yet.

The other things that I tried were to move the transcode directory from /dev/shm to a tmpfs mount in the go file and pining all services off CPU 0 to leave that for unraid itself.

Edited December 5, 2025Dec 5 by Tristankin

Update:

It crashed again, so I removed the lone 32GB stick, and right now just running the x2 16gb sticks. So far stable, time will tell.

It did perform a parity check and found a few errors, I would assume its the unclean shutdowns that's been happening. I will probably run another one to ensure it's all good.