This is my first time I had problems with a parity check it just keeps increasing in errors on a disk.... and it's going really slow on parity.... please help what should I do next? BTW I just switched everything to a new case. Disk 1 works perfect when I get in it. 

 

Here is a pic....  and the log. Thank you.

syslogbeer.zip

Post a SMART report for disk1.

Post a SMART report for disk1.

 

 

Here you go.... thanx.

sdb_disk_1.txt

Follow these instructions: http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F

 

Treat disk1 like it has a red ball.

So do a short smart test or a long test? From what you see what do you think is wrong? I am going to turn it off and replace the sata cable before I do it.

I'd replace the drive with a spare and then run pre-clear on the current drive. If the current_pending_sector RAW_VALUE goes to zero the the drive will become the spare. Or you can re-enable the drive and rebuild on to itself. The current_pending_sector RAW_VALUE must go to zero or the drive must be replaced.

Ok I will now have to buy a new 2tb....  so I can pre-clear it and replace disk 1 with it. Then I will pre-clear that drive and hope the pending sectors go back to 0 so I can have that as a spare or add it to the array. Funny next month that drive will be 2 years since I bought it... I could maybe still get an RMA from WD (just checked yes I can)

would you just get a replacement or still do a parity check?

 

Now you think I should buy a WD Red 2TB or a WD20EZRX ..... thank you so much for the help... I would of been lost... well I am. 

 

Leaning towards the RED because they have one more year on warranty.... on the red's still should i specify the -A option when preclearing?

Yes use -A to pre-clear every future drive. Although the -A is not required as it will be applied by default.

I'd replace the drive with a spare and then run pre-clear on the current drive. If the current_pending_sector RAW_VALUE goes to zero the the drive will become the spare. Or you can re-enable the drive and rebuild on to itself. The current_pending_sector RAW_VALUE must go to zero or the drive must be replaced.

 

 

This is the best way to go.

 

Depending on how close it is to warranty end, I might go as far as using the vendor's drive diagnostic software first.

Then if it reports the drive is bad, get it rma'ed

I'd replace the drive with a spare and then run pre-clear on the current drive. If the current_pending_sector RAW_VALUE goes to zero the the drive will become the spare. Or you can re-enable the drive and rebuild on to itself. The current_pending_sector RAW_VALUE must go to zero or the drive must be replaced.

 

 

This is the best way to go.

 

Depending on how close it is to warranty end, I might go as far as using the vendor's drive diagnostic software first.

Then if it reports the drive is bad, get it rma'ed

 

Thank you guys....  I am about to place an order for a new drive.

 

The vendors diagnostic software is this:  Data Lifeguard Diagnostic for Windows and do the EXTENDED TEST?

http://support.wdc.com/product/download.asp?groupid=608&sid=3〈=en

 

I will pre-clear the bad drive and hope they go to 0 and get back to you guys....

 

What I am confused if it does go to 0 does it still mean the hard drive is still bad and have to look out for it? 

So I just got my 2TB RED and it did not wan't to pre-clear, it is stuck on 0.....

 

Looked at it and it started to click and make noises.....    DOA

 

Ok now I do not trust RED drives.... what should I get? Please help.

I'd replace the drive with a spare and then run pre-clear on the current drive. If the current_pending_sector RAW_VALUE goes to zero the the drive will become the spare. Or you can re-enable the drive and rebuild on to itself. The current_pending_sector RAW_VALUE must go to zero or the drive must be replaced.

 

 

This is the best way to go.

 

Depending on how close it is to warranty end, I might go as far as using the vendor's drive diagnostic software first.

Then if it reports the drive is bad, get it rma'ed

 

Thank you guys....  I am about to place an order for a new drive.

 

The vendors diagnostic software is this:  Data Lifeguard Diagnostic for Windows and do the EXTENDED TEST?

http://support.wdc.com/product/download.asp?groupid=608&sid=3〈=en

 

I will pre-clear the bad drive and hope they go to 0 and get back to you guys....

 

What I am confused if it does go to 0 does it still mean the hard drive is still bad and have to look out for it?

 

If the count goes to zero then use the drive. Rebuild the drive  on to itself. That should clear the pending sector.

So I just got my 2TB RED and it did not wan't to pre-clear, it is stuck on 0.....

 

Looked at it and it started to click and make noises.....    DOA

 

Ok now I do not trust RED drives.... what should I get? Please help.

I think you need to put the drive in another system and run diagnostics. Your series of problems may not be the drives, it may possibly be the power distribution, which includes every cable and connection from the drives back to the PSU.

Sorry I meant that I just received a NEW 2tb wd red.... and I started the pre-clear on it and on pre-clear it was at progress 0 for about 30 minutes. I tried again and same thing then the drive started clicking. Got it to my windows machine and same thing click and bad sounds (did not even let windows boot). So this new red drive is DOA.....  should I get a replacement or get something else. First red drive I bought now I don't know what to trust.

 

Now I am thinking of going with a WD20EZRX....   

 

There is not much info on the Seagate NAS ST2000VN000 but maybe and it's on sale at Tiger...  http://www.tigerdirect.com/applications/searchtools/item-Details.asp?EdpNo=8198958&sku=TSD-2000NAS

 

A good review on the Seagate NAS  http://www.amazon.com/review/RUJQ466W04514/ref=cm_srch_res_rtr_alt_1

 

Going to try that seagate NAS drive.... Ordered..... 

This is why I suggested rebuilding the drive onto itself.

 

Un-assign the drive and start the array.

Stop the array and assign the drive. Start the array and the rebuild will begin.

 

After the drive is rebuilt check the pending sector count. It should be zero.

This is why I suggested rebuilding the drive onto itself.

 

Un-assign the drive and start the array.

Stop the array and assign the drive. Start the array and the rebuild will begin.

 

After the drive is rebuilt check the pending sector count. It should be zero.

 

Ok I will do this and get back to you....     

So this is what happened just after one hour.... it stopped rebuilding and red ball.

 

Jul 17 22:27:19 SERVER kernel: md: disk1 write error

Jul 17 22:27:19 SERVER kernel: handle_stripe write error: 109829232/1, count: 1

Jul 17 22:27:19 SERVER kernel: md: md_do_sync: got signal, exit...

Jul 17 22:27:19 SERVER kernel: md: recovery thread sync completion status: -4

Jul 17 22:27:19 SERVER kernel: md: recovery thread woken up ...

Jul 17 22:27:19 SERVER kernel: md: recovery thread has nothing to resync

 

 

1 Raw_Read_Error_Rate    0x002f  199  199  051    Pre-fail  Always      -      1133

  3 Spin_Up_Time            0x0027  222  163  021    Pre-fail  Always      -      3866

  4 Start_Stop_Count        0x0032  099  099  000    Old_age  Always      -      1211

  5 Reallocated_Sector_Ct  0x0033  170  170  140    Pre-fail  Always      -      582

  7 Seek_Error_Rate        0x002e  197  197  000    Old_age  Always      -      253

  9 Power_On_Hours          0x0032  086  086  000    Old_age  Always      -      10726

10 Spin_Retry_Count        0x0032  100  100  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  100  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      206

192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      34

193 Load_Cycle_Count        0x0032  195  195  000    Old_age  Always      -      17050

194 Temperature_Celsius    0x0022  120  105  000    Old_age  Always      -      30

196 Reallocated_Event_Count 0x0032  195  195  000    Old_age  Always      -      5

197 Current_Pending_Sector  0x0032  001  001  000    Old_age  Always      -      65535

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      311

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  199  199  000    Old_age  Offline      -      312

 

 

 

Ouch that's allot of current and pending relocation sectors.

 

 

I'm no expert but would say return drive if you can if not, pre clear it see if you can get the pending to zero, I could be total wrong as still fairly new to this myself, just me 2 pence hehe.

 

Have you got another drive to pre clear and put into its place and rebuild onto?

197 Current_Pending_Sector  0x0032  001  001  000    Old_age  Always      -      65535

I think the drive is probably toast. 65535 is a special value. I don't think smart is responding with a literally accurate value here.

197 Current_Pending_Sector  0x0032  001  001  000    Old_age  Always      -      65535

I think the drive is probably toast. 65535 is a special value. I don't think smart is responding with a literally accurate value here.

 

you learn something new everyday, thanks for that I was talking the value at face value

Ouch that's allot of current and pending relocation sectors.

 

 

I'm no expert but would say return drive if you can if not, pre clear it see if you can get the pending to zero, I could be total wrong as still fairly new to this myself, just me 2 pence hehe.

 

Have you got another drive to pre clear and put into its place and rebuild onto?

 

Yes. Try to RMA or pre-clear.

Ouch that's allot of current and pending relocation sectors.

 

 

I'm no expert but would say return drive if you can if not, pre clear it see if you can get the pending to zero, I could be total wrong as still fairly new to this myself, just me 2 pence hehe.

 

Have you got another drive to pre clear and put into its place and rebuild onto?

 

Yes. Try to RMA or pre-clear.

 

 

Ok I am going to RMA....  so finally got a drive to replace this one.

 

So I tried WD Diagnose and it fails to do.

 

code = 07 Failed read test element, failure 97

 

READ ELEMENT FAILURE

 

I don't trust it anymore....