Does this sound like a cable error

[DJRon]

Had a drive red X yesterday. A search of the syslog turns up this error: 
blk_update_request: I/O error

 

I have been in the case lately to install a new drive for pre-clearing.

 

Full Diagnostics are attached.

Thanks in advance.

 

epcot-diagnostics-20170818-2126.zip

[JorgeB]

Disk dropped offline, reboot and post new diags.

[DJRon]

Here are the latest diagnostics. That drive is rebuilding; but, incredibly slow. Rebuild has been going for 16hr 40min and it only 70% complete. Speed is around 52.3Mbs Earlier today is was only 22Mbs.

 

Thanks,

epcot-diagnostics-20170819-1459.zip

[JorgeB]

SMART is OK and there's nothing showing in the logs about the disk, so let the rebuild finish, there are a lot of errors about your flash drive, it's possibly failing or corrupt.

[DJRon]

Is there a way to determine which it is? And if it is just corrupt can it be repaired?

 

Thanks again for your help.

[JorgeB]

Run chkdsk on it on your desktop.

[DJRon]

chkdsk on the flash drive came back fine

 

[Squid]

Not surprised.  The flash drive got disconnect.  Your best bet is to put it into a different USB controller on your board  (IE: USB 2 <--> USB 3), and possibly change your boot order accordingly.

[DJRon]

Ran ChkDsk and on the USB and found no issue with the flash drive.

I replaced the controller card which I was Leary of.

Upon boot I am now showing 2 drives redballing. Both of these drives have never had issues with; SMART histories look good and they are both passing SMART History testing. I have attached the tests results for Disk1 and Disk2 respectively and the latest diagnostics.

Thanks in advance for any assistance.

 

 

epcot-diagnostics-20170831-1538.zip

epcot-smart-20170831-1546_Disk1.zip

epcot-smart-20170831-1546_Disk2.zip

[JorgeB]

Disks were already disable at boot time, whatever happened, happened before this boot, did the previous rebuild complete OK?

[DJRon]

The rebuild did complete successfully. I started a parity check after the rebuild to run overnight. The next day it reported parity check as having failed with errors (indicating it was user-aborted; which it definitely was not). This was the first time I saw both drives had red balled.

Edited August 31, 2017 by DJRon

[JorgeB]

Then go to Tools -> New Config -> Retain current configuration: All -> Apply

 

Check all disks are correctly assigned, if not assign any missing, before starting the array check "parity is already valid" (though it's likely not completely valid), then start the array and run a parity check, some sync errors are expected, if there are any more issues grab the diagnostics before rebooting.

[DJRon]

When I follow these Steps 
Then go to Tools -> New Config -> Retain current configuration: All -> Apply
And go to the Main page it tells me all data on both my parity drives will be erased. 

Do I still bring up the array?

[JorgeB]

Yes, that's normal, but don't forget to check the parity is already valid checkbox before starting.

[DJRon]

Thanks. Parity Check is running. Will check back the morning.

[DJRon]

OK Parity check completed

Quote

Last check completed on Fri 01 Sep 2017 02:12:39 AM EDT (today), finding 1371 errors. 
Duration: 9 hours, 29 minutes, 35 seconds. Average speed: 117.1 MB/sec

What are the next steps to make sure everything is still ok?

I still have a new drive I need to preclear to replace a drive (not one of the previously red balled ones) that is reporting bad sectors.

Thanks.

[JorgeB]

14 minutes ago, DJRon said:

What are the next steps to make sure everything is still ok?

 

Run another check, there shouldn't be any more sync errors now.

[DJRon]

Running second parity check