IonNuke

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.

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.zip I 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.

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?

The odd thing is. It's not disconnected but still reading. Could it be the SAS breakout cable is bad at some section?

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

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?

So the next time unmountable disk shows up just repair it and check the whole array again? And after that if it fixes it the unmountable will effective mount again?

I've only come across that once. And in that situation I pulled the drive and swapped with a new one and the rebuild took another 19 hours before it was up and running. Oh as a side note..... have you ever used any of the high capacity hard drives that utilize CMR with ePMR writing technologies as a parity drive? Also want to thank you so much for answering my questions and concerns helping move towards a better direction XD

Careful with connections? I'm not sure I follow. As an overview I have 12TB x6 for the data and x2 for parity. I thought maybe since I had two parity I can build both parity at the same time with two new larger drives. I read for this method the parity drives have to be first on the upgrade for obvious reasons. And then data array drives for rebuild can be done after that. I think the "risk" that lives in my head is what if something goes wrong during the rebuild. It's all feeding through a Perc H310i HBA. Part of me also thought maybe I can swap out the HBA to a Perc H710i during the rebuild steps but I figured probably not mess with the hardware altogether. Maybe hardware swap would be after I stabilize the array first. Thoughts?

Hi all, I've read and watched various guides and videos in regards to data array expansion with parity. All the guides really talk about starting the replacement of the parity drives with a much larger drive than the data drives first. After the parity rebuilds then rebuilding the data drives with the larger drives is possible. But in my current case I have two parity drives. So if I rebuilt the parity drives 1 by 1 (of course it would take way more time) I can ultimately upgrade the whole array and just do the swaps one by one until the entire array and parities are all up to the new capacity? But then part b of the question is being that I have two parities...... could I in theory just pull both parity drives and swap with the larger capacity to start the parity rebuild on both parity drives with the larger drives before moving onto the data array instead of one at a time? Or is doing this method 1 at a time generally safer?