My parity drive says disabled and I need to rebuild disk 6 in my array because i replaced the drive. I do have two parity drives but one is disabled due to some udma arc errors that popped up but I replaced the cable and smart test works fine. How should I proceed?

Attach Diagnostics ZIP to your NEXT post in this thread.

Here are diagnostics and I am on version 7.2.3.

puffinbytes-diagnostics-20260111-2218.zip

Do you still have the original disk6?

Might as well check to make sure emulated disk6 is mountable.

Set disk6 to not assigned, start the array in normal (not maintenance) mode, and post new diagnostics

I do not have disk6 any more, it was showing signs of early failure so I RMA'd it and they just refunded me so I bought a 24tb to upgrade. Previously it was a 12tb. Here are the diagnostics with disk6 not assigned.

puffinbytes-diagnostics-20260111-2237.zip

Emulated disk6 is mounted. No I/O errors logged yet. I didn't check SMART reports for each of your disks. Do any show SMART warnings (👎) on the DASHBOARD page?

Just now, trurl said:

Emulated disk6 is mounted. No I/O errors logged yet. I didn't check SMART reports for each of your disks. Do any show SMART warnings (👎) on the DASHBOARD page?

Not anymore. For full context, I did have a non ideal setup where my graphics card was pretty taut on some of my sata cables. When I went and replaced that drive, note it was working for 5~ months this way, but when i replaced the drive I must've accidentally pulled parity drive 1s too tight and it gave it those UDMA CRC errors. From there I went disaster recovery mode and invested in a full HBA the 9305-16i instead of making out my motherboard and a cheap Chinese 8 port sata extender. The new HBA has right angle longer sata cables and there should be no more cable issues ever. This is where I am at now. Parity drive 1 should not be disabled

1 minute ago, budman789 said:

Parity drive 1 should not be disabled

It wouldn't be if it shouldn't be.

If you have fixed your connection problems, since you have dual parity, you can rebuild parity and disk6 at the same time.

Stop the array, set parity to not assigned, leave disk6 not assigned, start the array.

Stop the array, assign parity and disk6, start the array to begin rebuilding both.

Just now, trurl said:

It wouldn't be if it shouldn't be.

If you have fixed your connection problems, since you have dual parity, you can rebuild parity and disk6 at the same time.

Stop the array, set parity to not assigned, leave disk6 not assigned, start the array.

Stop the array, assign parity and disk6, start the array to begin rebuilding both.

Would it be highly recommended to leave my VMs and Docker off while rebuilding both?

4 minutes ago, budman789 said:

Would it be highly recommended to leave my VMs and Docker off while rebuilding both?

Rebuild will affect array access, and array access will affect rebuild. Won't cause errors, just slow things down.

And your appdata has files on the array. You should work on getting all that off the array after you finish rebuilding.

Just now, trurl said:

Rebuild will affect array access, and array access will affect rebuild. Won't cause errors, just slow things down.

And your appdata has files on the array. You should work on getting all that off the array after you finish rebuilding.

Thank you for your time and expertise. I am rebuilding both now. Estimated 3 days!

9 hours ago, budman789 said:

but one is disabled due to some udma arc errors that popped

CRC errors do not cause disk to be disabled - they just trigger retries. A disk only gets disabled when a write to it fails. The CRC error could, though, be indicating a cabling issue for the drive (either SATA or power).