dragoby

SOLVED!

I can confirm that replacing the drive that was marked by the diskspeed docker did the trick Cheers! Josh

Hey Johnnie that seemed to do the trick, There was one drive that was only writing at 1mb/s which is what was triggering the limit. I have replaced it and its now doing the data re-build so once its complete ill do the parity check again but I believe this should be done. I will update the thread when I know for sure Thanks! Josh

Hello I have been having a long running issue with my parity check where it is processing at less than 1mb/s. The parity is currently only 1tb and specifies it will take at least 11 days to complete which is ridiculous I would think. I have the parity running in safe mode with no plugins or anything and that is the speed which is currently being recorded. If anyone can provide any assistance that would be appreciated. Please find the attached diagnostics package Hardware: Motherboard: Supermicro x8DTU-LN4+, Version 2.0 CPU: Dual Xeon X5550 Memory: 141.7gib Cheers Josh auxillium-diagnostics-20201026-1523.zip