January 17Jan 17 So I started by pulling both Parity drives to replace with new and larger parities.About 12 hours in there was reported errors in Disk 3 with write errors. So my thought is to put one of the original parity drives back into where I have assigned the parity drives and just build 1 parity. But as for disk 3 throwing errors...... would it work if I threw in the other original parity in place of where Disk 3 sits?
January 20Jan 20 Author This is the diagnostics for the array.The drive didn't unmount (yet). Unraid detects errors but it's still building. tower-diagnostics-20260119-1910.zip
January 20Jan 20 Community Expert Solution Drive has disconnected.Shutdown, check connections, restart, post new diagnostics
January 20Jan 20 Author 13 minutes ago, trurl said:Drive has disconnected.Shutdown, check connections, restart, post new diagnosticsThe odd thing is. It's not disconnected but still reading. Could it be the SAS breakout cable is bad at some section?
January 20Jan 20 Author The last time this happened it was flagging Disk 3 with issues right around the 57% parity sync point. This time with it now shows Disk 4 with errors. But now that it's gotten me thinking.... 1~4 is on the same 8087 to SATA breakout. So it could be somewhere along that set of cables is bad on that stack?
January 20Jan 20 Author This is the new diagnostics after I had shut it down. re-seated the SATA break-out cables from the HBA and started the array again. Parity has restarted. The first log message that popped up indicated there's no issues with the array.tower-diagnostics-20260119-2038.zipI also ordered a new set of SFF-8087 to SATA break out cables in case the set that's connected is hot garbage causing all these weird issues when there might not actually be issues with any of my drives. Edited January 20Jan 20 by IonNuke
January 20Jan 20 Community Expert SMART for disk4 looks OK, didn't have a report for that disk before. Diagnostics taken just after reboot, parity rebuild started again but that's the end of the log so far.
January 20Jan 20 Author I'm guessing if the array build up to 57% again and the cable for whatever reason drops the connection to the drive then it might be the cable ? I know cables aren't always perfect and sometimes they just go bad without any rhyme or reason. But new set of cables are on the way.
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.