Jump to content
We're Hiring! Full Stack Developer ×

Pre-Clear Failing


Recommended Posts

I'm running Unraid version 4.7. One of my Drives generated tons of errors during updating the Parity disk and red balled. So I replaced it with another disk in the same slot but pre-cleared failed. I know it might be down to the cables etc.. but is there anything in the log file that can help see where the issue is?

 

 

========================================================================1.4

== invoked as: ./preclear_disk.sh -m [email protected] /dev/sde

==

== Disk /dev/sde has NOT been successfully precleared

== Postread detected un-expected non-zero bytes on disk==

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 7:19:39 (75 MB/s)

== Last Cycle's Zeroing time  : 6:28:40 (85 MB/s)

== Last Cycle's Post Read Time :  ( MB/s)

== Last Cycle's Total Time    :

==

== Total Elapsed Time

==

== Disk Start Temperature: 33C

==

== Current

==

============================================================================

 

============================================================================

============================================================================

==

== S.M.A.R.T Initial Report for /dev/sde

==

Disk: /dev/sde

smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model:    WDC WD2002FYPS-01U1B0

Serial Number:    WD-WCAVY0941964

Firmware Version: 04.05G05

User Capacity:    2,000,398,934,016 bytes

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:  8

ATA Standard is:  Exact ATA specification draft version not indicated

Local Time is:    Wed Aug 17 22:45:50 2011 BST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x82) Offline data collection activity

was completed without error.

Auto Offline Data Collection: Enabled.

Self-test execution status:      (  0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: (40260) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: (  2) minutes.

Extended self-test routine

recommended polling time: ( 255) minutes.

Conveyance self-test routine

recommended polling time: (  5) minutes.

SCT capabilities:      (0x303f) SCT Status supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

3 Spin_Up_Time            0x0027  148  145  021    Pre-fail  Always      -      9575

4 Start_Stop_Count        0x0032  099  099  000    Old_age  Always      -      1748

5 Reallocated_Sector_Ct  0x0033  200  200  140    Pre-fail  Always      -      0

7 Seek_Error_Rate        0x002e  200  200  000    Old_age  Always      -      0

9 Power_On_Hours          0x0032  082  082  000    Old_age  Always      -      13372

10 Spin_Retry_Count        0x0032  100  100  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  253  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      89

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

193 Load_Cycle_Count        0x0032  154  154  000    Old_age  Always      -      139352

194 Temperature_Celsius    0x0022  119  098  000    Old_age  Always      -      33

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      1

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  195  167  000    Old_age  Offline      -      1030

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

No self-tests have been logged.  [To run self-tests, use: smartctl -t]

 

 

SMART Selective self-test log data structure revision number 1

SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

  1        0        0  Not_testing

  2        0        0  Not_testing

  3        0        0  Not_testing

  4        0        0  Not_testing

  5        0        0  Not_testing

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

==

============================================================================

 

 

 

============================================================================

==

== S.M.A.R.T Final Report for /dev/sde

==

Disk: /dev/sde

smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

 

Probable ATA device behind a SAT layer

Try an additional '-d ata' or '-d sat' argument.

==

============================================================================

 

 

Link to comment

First, update your preclear script.  It is up to version 1.12, and you are 8 versions behind.

Find the latest version here: http://lime-technology.com/forum/index.php?topic=2817.0

 

It might be the only issue, as it had an problem with newer versions of Linux and shell evaluation of numbers.

 

Then, if it does not work, perform a memory test, preferably overnight.  Other than that, it could be anything. (disk, power supply, motherboard, disk controller)

 

Joe L.

 

Link to comment

First, update your preclear script.  It is up to version 1.12, and you are 8 versions behind.

Find the latest version here: http://lime-technology.com/forum/index.php?topic=2817.0

 

It might be the only issue, as it had an problem with newer versions of Linux and shell evaluation of numbers.

 

Then, if it does not work, perform a memory test, preferably overnight.   Other than that, it could be anything. (disk, power supply, motherboard, disk controller)

 

Joe L.

 

 

Many thanks. I'll give the memory test a try tonight plus I can also boot my main machine up as Unraid using the trial version and will run   a Pre-Clear on the same disk and see what it comes back with.... Such a pain having all these variables but at least the disk it first failed as having Errors on was able to be read on another machine and the data extracted... You don't get that with a propitiatory RAID system, and the fact that the disk was readable on another machine may also point to the hardware on the first.....

 

Joe L - I just followed the link you gave and can only see preclear for up to version 1.11  ?

Link to comment

First, update your preclear script.  It is up to version 1.12, and you are 8 versions behind.

Find the latest version here: http://lime-technology.com/forum/index.php?topic=2817.0

 

It might be the only issue, as it had an problem with newer versions of Linux and shell evaluation of numbers.

 

Then, if it does not work, perform a memory test, preferably overnight.   Other than that, it could be anything. (disk, power supply, motherboard, disk controller)

 

Joe L.

 

Many thanks. I'll give the memory test a try tonight plus I can also boot my main machine up as Unraid using the trial version and will run   a Pre-Clear on the same disk and see what it comes back with.... Such a pain having all these variables but at least the disk it first failed as having Errors on was able to be read on another machine and the data extracted... You don't get that with a propitiatory RAID system, and the fact that the disk was readable on another machine may also point to the hardware on the first.....

 

Joe L - I just followed the link you gave and can only see preclear for up to version 1.11  ?

Sorry.  I attached the wrong zip file. Try it now.

Link to comment

Sounds like your new drive might be bad, the last line in your SMART report:

 

200 Multi_Zone_Error_Rate   0x0008   195   167   000    Old_age   Offline      -       1030

 

is rather unusual, most of the posted SMART reports for these WD 2TB drives you see here will only have a raw value of 0 or maybe 1, but yours is 1030.  Now I know this is one of the SMART fields that we don't know what the meaning of the raw value actually is, but your drive has a very strange value.  I would suggest you put the drive in a Windows PC and install and run Western Digital's "Data Lifeguard Diagnostics for Windows" on it to see if it passes their tests.  See this posting for some background:

 

http://lime-technology.com/forum/index.php?topic=12789.msg121545#msg121545

 

I've had a few of these drives fail the preclear and in those cases the WD diagnostic tool declared them as bad even though the SMART report still said they were good.

 

Regards,

 

Stephen

Link to comment

Cheers Guys.

 

I'm running a pre clear first using version 1.12 of the script on another box to see if the problem has gone away, if it fails again I'll use the WD diagnostic tool and report back ;-)

 

In the mean time i've been running a Memtest on my main box, i've attached the screen dump but all looks fine to me, please advise if I'm wrong.

IMG_3511.jpg.ed7e030dbc767f112eec7fe18bac01ac.jpg

Link to comment

Well Pre-clear was taking such a long time on this drive >37 Hours!!! A non-enterprise WD 2TB drive had finished the preclear in 34 Hrs. So I started thinking maybe this drive is a bit on the slow side  and decided to to try the WD Diag tool. This passed with flying colours.. so maybe it was a glitch, after all, just a slow drive?

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...