GazaIan

Yeah, I'm going through all my shares now and for whatever reason all of my minimum free space values are missing for every single share. Not sure why but given all the random troubleshooting I've had to do in general, I'm sure it just got caught up in the mix. Thank you for the help!

Hello! Appreciate the response. I went to double check that Unbalance or even the Mover didn't break the Docker image and I found the solution was silly and simple... the drive that the Docker image is stored on had run out space entirely. Thought I had a 10GB free space buffer but apparently not, I only had a few kilobytes free and starting Docker was throwing I/O errors on disk3, the drive the image is on. After freeing up several gigs, were back in action. Appreciate the help!

After a healthy fight getting my 3900X to behave in Unraid and get the parity back to a valid state, I went ahead and updated to Unraid 7.0 in hopes that it would solve some of the stability issues with the new CPU. It has! However, while updating my containers, I started getting errors installing any update where it immediately failed claiming there is already a container with the same name (didn't catch the exact error unfortunately). Gave the server a restart, and now Docker is dead entirely, showing the error "The Docker service failed to start." I've attached a diagnostic pull. Any help is appreciated. Thanks! mnemosyne-diagnostics-20250120-1941.zip

Seems disabling Global C States did the trick; parity sync just finished and the array is back in action. Unfortunately probably going to mean I'm going to need to change the 3900X back if I can't get it to behave in Unraid.

I've actually got one saved but I'm not 100% sure if this was post crash, Unraid seems to have generated this one on its own. Definitely had a crash this day so hopefully this has what's needed. In case it's needed, I pulled a fresh one too and attached that as well. Appended the filename with (no crash yet). mnemosyne-diagnostics-20250118-2238.zip mnemosyne-diagnostics-20250115-2107 (no crash yet).zip

I've got an Unraid machine that I'm now battling system instability after upgrading. I've posted the specs at the end of this post. The system needs to complete a data rebuild, but every single time the process locks up at random and all drive activity stops, and then a few hours later the WebUI becomes completely unresponsive. It's been hard to wager whether or not each change worked, since it typically means waiting up to 18 hours before the system crashes (the longest I've managed so far). To add to this, formatting the drive was also an odd nightmare, as formatting as xfs would cause the entire system to lock up within minutes. It took multiple reboots and switching to zfs, formatting, and back to xfs to get the drive formatted without the system giving up. 1 On the hardware front, I've temporarily reverted back to 1 stick of the old RAM to no avail, system still crashes anywhere between 1 to 18ish hours. I've changed the Power Idle Control to Typical in the BIOS, no change. I've now disabled C states entirely, and also disabled AMD Core Performance Boost and I'm giving it another shot, but I'm hoping someone smarter than me can take a look at the log I saved and let me know what I should be trying out to fix these issues. I've attached the most recent syslog below. Any help is super duper appreciated! CPU: Ryzen 3600 to 3900X RAM: 16GB to 64GB Motherboard: ASUS Strix X370-F (updated to the latest stable BIOS) Storage: 80TB to 88TB (removed 1x 8TB, installed 1x 16TB) syslog.txt