Hi All

 

Hoping for some help here. I've been running unraid for a couple of years pretty much stable.

I upgraded the system board, processor, and memory and everything has gone completely unstable. Unraid just locks up after 10 to 30 minutes and if I have a monitor attached I can see the GUI frozen at the time it happened but no interaction is possible. Server is unpingable and a hard shutdown is needed.

 

The hardware has been in use in a gaming machine for 2 years without issue but to recheck I have run Memtest86 for half a day with no errors reported, and I booted into a ubuntu live OS for half a day and ran prime95 without any issue. So the hw seems fine.

I have disabled all C states power saving in the bios, no change.

 

I deleted my docker image and started again with a couple docker apps but still the same. Have disabled my one VM (HASSOS), no change.

 

Booted into Unraid safe mode and it still crashes.

 

Downgraded to 6.11.5...no change.

 

Enabled syslog server but it doesn't update the flash drive or share so not sure if I'm missing something. https://tinypic.host/image/Cqqje

 

Attaching diagnostics file in the hope someone can help. Its a finicky little case I'm using so its a pain to have to go back to the original hardware but that might be the next step.

tower-diagnostics-20230801-0957.zip

29 minutes ago, commanding-barbarian8014 said:

Enabled syslog server but it doesn't update the flash drive or share so not sure if I'm missing something.

Remote syslog server needs to be set, same IP/port as your server, though mirror to flash should still work.

Thanks JorgeB. I actually found that just after I posted and have it set up.
Strangely it has been for almost 2 hours now. I started bringing docker container online and will see how it goes. Will have the syslog this time if and when it crashes.

OK, it was up to 2 and a half hours which was a new best so I tried to think what has been different. I noticed the parity check was paused so I started that and shortly after it crashed again. Attaching syslog (nothing there?) and fresh diagnostics.
Will try leave it online now with the parity paused to see if thats the root cause. Any ideas if so? Gonna reseat sata cables just in case.

syslog-192.168.0.2.log tower-diagnostics-20230801-1320.zip

That fact that there's nothing relevant logged and that the server crashes mostly during a parity check suggest more a hardware issue. like for example a weak PSU.

I have a spare PSU.....will try it out. Think the current one is 450w and I have a 550w spare so fingers crossed.

9 hours ago, JorgeB said:

That fact that there's nothing relevant logged and that the server crashes mostly during a parity check suggest more a hardware issue. like for example a weak PSU.

Thanks for helping me JorgeB. It was indeed the PSU. The fact that my cpu tdp hadn't changed made me discount it as it had worked fine before I swapped the rest of the parts.

Appreciate your time!