Hi,

 

I have the following situation, not sure on the next step:

 

1.  I received a notice that disk #6 (WCC4E5AYDP0C) was disabled.  I didn't collect the syslog and shut down the server.  I thought it might have been from bumping one of the SAS-to-SATA cables, since I had the cover open and was plugging in/unplugging on-board usb flash drives to upgrade my IBM M1015 device.  I re-seated the cables and hot-swap drive bays.

2.  I rebooted the server and ran smart tests on disk #6, everything reported fine, no reallocated sectors, read errors, etc.  I chalked it up to bumping one of the SAS-to-SATA cables while upgrading the IBM1015.

3.  I unassigned disk #6, started the array, stopped the array, reassigned disk #6 (WCC4E5AYDP0C) started the array and the array and disk #6 started automatically rebuilding the data.

4.  After a few minutes of rebuilding disk #6, disk #11 (1CH164_Z1E9G6AP) started reporting read errors.  I stopped the array and exported the attached diagnostics file.

5.  I re-seated the cables and hot-swap drive bay for disk #11, booted the unRAID server and ran a few short smart tests on disk #11 (passed).  Not sure if this was due to another loose cable/drive.

6.  I haven't started the array.  Not sure what to do for the next step.  I believe the contents of disk #6 might be corrupted since I previously started a rebuild of disk #6 and canceled.

 

What would be the next step to (hopefully) prevent data loss and get back to a healthy array?  Thank you.

diagnostics-20161023-2008.zip

Rebuild disk6. It will start the rebuild from the beginning so it doesn't matter what happened on the previous attempt.

Thank you!  The rebuild has managed to get past the point where disk #11 started having read errors, so perhaps it was the cabling and/or disk drive seating into the 5-in-3 cage.

 

Edit:  Disk #6 successfully rebuilt!