commanding-barbarian8014

OK, just figured out what that issue was. Teslamate was crashing due to MQTT issues which I wasn't using. Disabled MQTT for that container and its running fine now. My mover is running now which has interupted the parity, I'll report back when its steady again.

Thanks. I disabled docker about 30 minutes ago to see if activity there was causing any issue but its still the same. I'll re-enable it now and take a look at that as it may be a side issue.

I had a 3 disk array (2 x data [3TB +4TB] and a 4TB parity) and was low on space so got a new 14TB EXOS drive to future proof any further storage upgrades. I tested the new drive and precleared as it was used but all looked good and the preclear was running at approx 250MB/s. I thought it would be safest to add the new drive as a 2nd parity disk and once rebuilt I'd move the old parity to the array. Maybe this is where I've gone wrong. Anyway approx 36 hours later and I'm still only at 20% rebuild and the speeds seem to max at about 25MB/s but often drop to 3 or 4MB/s. I had a look at the syslogs and don't see any SATA errors or anything, is that where they'd show? Should I have done this differently? Should I restart using another method? Appreciate any help. Diagnostics attached if someone could take a look.tower-diagnostics-20251130-1249.zip

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!

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

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

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.

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