IDontBelongHere

Thanks again for the help guys. Everything is working back as it should, and my parity sync finished successfully the other night. Didn't realize writing to the drive would slow down the parity sync that significantly. Is it because it was doing a fresh sync? I've never had a parity sync go that slowly previously even with the array being heavily used.

I was trying to write to my "Data" share. I've fixed that issue by updating my docker which was trying to write to it, and doing another reboot. Most of the issues seem to have resolved following a reboot and updating/reinstalling of dockers. However, I am still having issues with my parity sync and extremely high CPU usage (95%). The sync starts off fine going about 90MB/s, but it's at 15.4% and has slowed down to a range of about 300KB/s to 1.5 MB/s. I've tried disabling the docker service to se if it speeds up, but it doesn't seem to help at all. Thanks again for all of y'alls help thus far. tower-diagnostics-20250427-0824.zip

Hi Thanks for the help so far. I'm also getting errors that the cache is full, and it's not. Nothing at all can be written to the array, even outside of those mentioned disks. I cleared the old config files, but the issues persist.

Migrated to a new server and all of the disks were recognized fine, but I can't write to any disk it seems, and it says the cache is full when it's not. I tried a new config to see if that would help, but it did nothing useful. tower-diagnostics-20250422-2309.zip