2nd drive failed during a rebuild

[JDBall]

Hi all,

 

Hoping that you can help.

 

I was replacing a good 6TB drive with a 12TB drive (Disk 5) and during the rebuild I noticed that read errors we're rapidly increasing for Disk 6.  I cancelled the rebuild as I've been having errors from time to time on a new HBA that I recently installed and reconnected Disk 6 to a SATA port on the motherboard.

 

After restarting my server Disk 6 could not be detected at all.  I've tried connecting it to another PC and it can't be found in BIOS and doesn't appear to powering on.

 

The Data on the old Disk 5 should be vaild.

 

I have set the new unassigned disk to the slot for Disk 6 and the old disk to the slot for Disk 5.  Next to the Start button the UI says "Too many wrong and/or missing disks!".

 

Hoping that you can give me some guidance on how to make Disk 5 active and hopefully rebuild Disk 6 from parity.  Diags attached.

 

James

 

 

unraid-diagnostics-20211109-1229.zip

Edited November 9, 2021 by JDBall

[JorgeB]

You can try this but it will only work if parity is still valid:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, including the new disk you want to rebuild, replacement disk should be same size or larger than the old one
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk6
-Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk
-If the emulated disk mounts and contents look correct stop the array
-Re-assign disk6 and start array to begin.

[JDBall]

Unfortunately the emulated disk does not mount.  it say unassigned - I guess this means that my parity is no longer valid?

[JorgeB]

Parity would be still be (mostly) valid if there weren't any writes to the array after you started rebuilding disk5.

[JDBall]

There shouldn't have been any at all as I had shutdown all containers that could potentially write to the array.

 

Anything else I can try?

[JorgeB]

3 hours ago, JDBall said:

Unfortunately the emulated disk does not mount.  it say unassigned

Not quite sure what you mean here, if it just doesn't mount you should run a filesystem check like mentioned above, what do you mean by unassigned? Or post diags after arrays start.