Homerr Posted December 26, 2019 Author Share Posted December 26, 2019 On 12/1/2019 at 1:30 AM, johnnie.black said: ... P.S: parity2 needs a new SATA cable. Thanks so much johnnie for noting this. I think this was the real culprit all along. In 25 years of computer building I've never had a standard SATA go bad. Everything is back in the array and a parity check showed no errors and it's been running a week now. Quote Link to comment
JonathanM Posted December 26, 2019 Share Posted December 26, 2019 42 minutes ago, Homerr said: In 25 years of computer building I've never had a standard SATA go bad. Probably not the cable itself, most likely the connectors. Same end result though. Also, microsoft is very unhelpful, they will continue to let you use a bad cable until the connection fails completely. Ever wonder why some machines just seem to be REALLY slow for no reason even after a clean install and passing drive tests? Linux at least tells you there may be an issue that you could troubleshoot. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.