Hello, i ran a long overdue parity sync and i got a red ball waiting on me as i got home.

 

I would generally do this

 

 

1) Get a new drive run 1 preclear cycle.

2) Replace disk1 with the new precleared drive.

3) Once the array is rebuild and operational, run preclear on the red ball drive 1 cycle to see what happen. then run a smart test to comfirm that it have heath issue.

4) if it is a health issue then try to RMA from WD.

 

Im not sure if i need to de-assign the faulty drive, then put the new pre-cleared in its place and assign it to the appropriate slot ... pls advise.

 

additionally after reviewing the log, i found a lot of these errors

 

Feb 13 20:54:24 hal kernel: ata4: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Feb 13 20:54:24 hal kernel: ata4: status=0x51 { DriveReady SeekComplete Error }

Feb 13 20:54:24 hal kernel: ata4: error=0x04 { DriveStatusError }

 

i seem to remember this could be fixed somehow ....

 

i'm attaching the log (minus about 170k repeated lines), hoping to hear from more knowledgeable guys

syslog-20120213-210131.txt.zip

Replace faulty drive.

You can get a smart report before replacing the drive to see whats happening.

Otherwise your plan is good.

Shutdown your system, insert new drive and remove old (i prefer to preclear on another machine)

Assing new drive to olds slot in unraid menu and let it rebuild.

 

Sent from my SGH-I727R using Tapatalk

 

Try a new sata cable as well - cheaper then a drive.

 

whiteatom

thanks for all the replies ... i basically followed instructions on this wiki page

 

i plan to preclear the failed drive again and see what happens ... not much hope though.

 

the drive is attached to a norco sas backplane so couldnt switch cables