Preclear.sh results - Questions about your results? Post them here.


2840 posts in this topic Last Reply

Recommended Posts

syslog and short smart test log attached.  to my uneducated eye, it doesn't look good...

 

Yeah, lots of bad sectors.  I would start a Preclear but skip the Pre-read (use preclear_disk.sh -W), since you already know there are issues.  The write-zeroes phase should force the drive to deal with every sector, remapping them if necessary.  It will probably be slow.  Then the Post-read will test the drive, provide a final SMART report, with hopefully all Pending sectors fixed.  From the last report and the Preclear report, you should be able to decide what to do with the drive.

 

I do apologize for my tone above, somewhat myopic, only looked at the one post.

Link to post
  • Replies 2.8k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I have only found 4 SMART reports from either 8TB or 10TB Ironwolfs with enough working hours to get stable normalized values for (1)RRER (7)SER and (195)HER. It is still an small sample to make gener

Good observations again, I agree with yours.  I have to apologize for not responding to your first report!  I spent a fair amount of time on it, a lot of data!  You had some interesting observations,

if your talking at the raw read error rate and  seek error rate then i agree:- http://sgros.blogspot.co.uk/2013/01/seagate-disk-smart-values.html   in short your drive looks healthy to me.

Posted Images

Thanks, I'll re-run the pre-clear (have to find the skip pre-read option again), and will post back if I have any more questions.

 

No problem about your tone.  Sometimes I'm 'the one that broke the camels' back', and I get the brunt of pent up frustration.  I didn't take it personal.  I do appreciate the help.

 

Thanks again.

Link to post

RobJ gave you the option to skip Pre-read ;)

 

I didn't see that until you mentioned it.  It doesn't look like he edited his post, so I must be blind.  I only found the -n option, which skips pre and post read it seems.  Once it finishes, if it still looks like it might work, I'll run it again with the -W option, as one more test.

 

thanks for pointing it out for me.  :-\

Link to post

My parity drive was failing and as I'm running out of capacity I bought 2 Toshiba DT01AC drives. Here is the report of the first drive that finished the preclear process - I do believe that it's looking great. What do the experts say?

 

P.S. I have no clue why the temperature is showing such crazy data ..... the drive wasn't running hot AT ALL.

Link to post

My parity drive was failing and as I'm running out of capacity I bought 2 Toshiba DT01AC drives. Here is the report of the first drive that finished the preclear process - I do believe that it's looking great. What do the experts say?

 

P.S. I have no clue why the temperature is showing such crazy data ..... the drive wasn't running hot AT ALL.

 

Drive is fine.  Final temp is 33, nothing wrong with that.

Link to post

I'm trying to preclear a drive that had red-balled on my, but I suspect it was just due to a cabling issue.  I've since replaced that drive with a larger one, and am now trying to preclear the drive that 'failed' to confirm I can add it back to the array....

 

syslog and short smart test log attached.  to my uneducated eye, it doesn't look good...

I would start a Preclear but skip the Pre-read (use preclear_disk.sh -W)

 

It took 48 hours to finish...

 

========================================================================1.15
== invoked as: ./preclear_disk.sh -A -W /dev/sdc
== WDCWD20EARS-00MVWB0   WD-WCAZA2130725
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Last Cycle's Zeroing time   : 28:50:44 (19 MB/s)
== Last Cycle's Total Time     : 47:41:53
==
== Total Elapsed Time 47:41:53
==
== Disk Start Temperature: 35C
==
== Current Disk Temperature: 39C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   189     200           51        ok          21640
    Reallocated_Sector_Ct =   142     184          140        near_thresh 1108
          Seek_Error_Rate =   100     200            0        ok          0
      Temperature_Celsius =   111     115            0        ok          39
  Reallocated_Event_Count =     1       1            0        near_thresh 1108
   Current_Pending_Sector =     3       1            0        near_thresh 64234
No SMART attributes are FAILING_NOW

65021 sectors were pending re-allocation before the start of the preclear.
64230 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
64234 sectors are pending re-allocation at the end of the preclear,
    a change of -787 in the number of sectors pending re-allocation.
317 sectors had been re-allocated before the start of the preclear.
1108 sectors are re-allocated at the end of the preclear,
    a change of 791 in the number of sectors re-allocated. 
============================================================================

 

Looks like I've got myself a paperweight now, no?

Link to post

Wow...so many reallocated sectors...ah, wait it's WD...  ;)

At least it did not totally black-out like mine was doing.

 

Reallocated sector count is "near threshold".

Spare sectors will soon be out - as far as I understand the SMART philosophy.

 

While I tend to keep even those drives with low reallocated counts, in this

case I would scrap it.

 

 

Link to post

Looks like I've got myself a paperweight now, no?

 

I was going to suggest a wheel chock, but it's too low.

 

Another possibility, more practical, use it as a decoy for thieves.  Set it on an appropriate shelf, visible, with a label indicating "All my financial info", and underneath that the word "(hidden)" to totally interest any hacker.  Load it with gigabytes of trash videos (any kind) and other garbage, and that should give you a big laugh if it is ever taken.  It is really really time-consuming and frustrating trying to recover data from a bad drive, especially if it is getting worse while you work on it.  Or for the less technical thief, label it as "Very private videos, hidden on here".  Should waste a lot of their time.

Link to post

Hi All,

 

New Seagate NAS 2Tb drive. Preclear looks 'ok' to me, but I'd appreciate confirmation from someone more knowledgeable.

 

Thanks.

Keep an eye on the high-fly-writes.  The normalized value has dropped quite a bit and is getting closer to its affiliated failure threshold.

It has not failed SMART, but it will be something for you to watch on that drive.

Link to post

Hi All,

 

New Seagate NAS 2Tb drive. Preclear looks 'ok' to me, but I'd appreciate confirmation from someone more knowledgeable.

 

Thanks.

Keep an eye on the high-fly-writes.  The normalized value has dropped quite a bit and is getting closer to its affiliated failure threshold.

It has not failed SMART, but it will be something for you to watch on that drive.

Thanks.

 

I've just read up on "high-fly-writes" and it does seem opinion is divided on if this actually means anything or not. If given the option, would you advise putting data on the drive and simply monitoring it, or perhaps running another couple of preclears?

Link to post

High-fly-writes don't have a threshold or valid scaling routine.  The RAW is an actual count of how many high-fly-writes have occurred, but VALUE is just 100 minus the count in RAW until it hits one where it will stay.  It never reaches zero, but the RAW count will continue to increase.  The THRESH number is zero, which basically means it is not used, since it cannot be reached, which also means this attribute can never FAIL a SMART test.

 

Joe's point is good though.  77 high-fly-writes already (only 50 operational hours) is rather unusual, so probably something to monitor.  However, I do not know of a single case where a drive failed with a very high or growing high-fly-writes count, so it does not seem to be a significant item.  It was added several drive generations ago to the SMART attribute tables of many drives, but always with the same dummy scaling routine, and always with a THRESH of zero.  I prefer to call it an experimental attribute, perhaps one they wanted to monitor to see if there was any association with drives failing.  So far, I haven't seen one, and the fact the handling of it hasn't changed seems to indicate it's not an important factor to them either.

 

I would use the drive without any concerns.  There are no other indications of issues at all.

Link to post

Agree that high-fly writes should be considered an "experimental" parameter.    WD doesn't bother to report these, and I've seen numbers all over the charts on Seagate drives ... with NO issues as a result.  I suspect they can simply be ignored altogether, but it won't hurt to monitor them to see if the behavior starts to change over time.

 

Link to post

Nothing too spectacular, but I wanted to provide the results of one of of my 6TB WD Reds preclear as another datapoint. I have 3 more reports of the same model, but they are a bit off because I adjusted the timezone halfway through the process. But the times were very comparable to this one:

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdg
== WDCWD60EFRX-68MYMN1   WD-WX11D7
== Disk /dev/sdg has been successfully precleared
== with a starting sector of 1
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 15:19:46 (108 MB/s)
== Last Cycle's Zeroing time   : 12:44:48 (130 MB/s)
== Last Cycle's Post Read Time : 28:27:21 (58 MB/s)
== Last Cycle's Total Time     : 56:32:54
==
== Total Elapsed Time 56:32:54
==
== Disk Start Temperature: 27C
==
== Current Disk Temperature: 36C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdg  /tmp/smart_finish_sdg
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   116     125            0        ok          36
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================

 

Disk: /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.16.3-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD60EFRX-68MYMN1
Serial Number:    WD-WX11D7
LU WWN Device Id: 5 0014ee 
Firmware Version: 82.00A82
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5700 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Oct  3 20:46:07 2014 PDT
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                ( 7184) 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:        ( 725) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control 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   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       56
10 Spin_Retry_Count        0x0032   100   253   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       -       1
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   116   115   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

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.

 

Actually now that I'm looking at it, I'm surprised that the POWER_ON_HOURS change isn't reported in the report. Does the script ignore that now?

Link to post

Two more WD60EFRX data points

 

 preclear_report_sdg
========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdg
== WDCWD60EFRX-68MYMN1   WD-WXCxxxxxxx33
== Disk /dev/sdg has been successfully precleared
== with a starting sector of 1
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 15:15:10 (109 MB/s)
== Last Cycle's Zeroing time   : 12:28:00 (133 MB/s)
== Last Cycle's Post Read Time : 27:52:22 (59 MB/s)
== Last Cycle's Total Time     : 55:36:32
==
== Total Elapsed Time 55:36:32
==
== Disk Start Temperature: 35C
==
== Current Disk Temperature: 39C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdg  /tmp/smart_finish_sdg
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   113     117            0        ok          39
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================

# cat preclear_report_sdh
========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdh
== WDCWD60EFRX-68MYMN1   WD-WX2xxxxxx73
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 1
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 14:57:55 (111 MB/s)
== Last Cycle's Zeroing time   : 12:10:29 (136 MB/s)
== Last Cycle's Post Read Time : 27:19:53 (60 MB/s)
== Last Cycle's Total Time     : 54:29:16
==
== Total Elapsed Time 54:29:16
==
== Disk Start Temperature: 35C
==
== Current Disk Temperature: 39C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   113     117            0        ok          39
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================



cat smart_finish_sdg
Disk: /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.16.3-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD60EFRX-68MYMN1
Serial Number:    WD-WXCxxxxxxx33
LU WWN Device Id: 5 0014ee 260398076
Firmware Version: 82.00A82
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5700 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Oct  9 22:21:00 2014 PDT
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                ( 5384) 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:        ( 707) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control 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   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       55
10 Spin_Retry_Count        0x0032   100   253   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       -       3
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   113   108   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

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.

# cat smart_finish_sdh
Disk: /dev/sdh
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.16.3-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD60EFRX-68MYMN1
Serial Number:    WD-WX2xxxxxxx73
LU WWN Device Id: 5 0014ee 2b58f5391
Firmware Version: 82.00A82
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5700 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Oct  9 21:14:13 2014 PDT
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                ( 3824) 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:        ( 692) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control 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   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       54
10 Spin_Retry_Count        0x0032   100   253   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       -       3
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   113   107   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

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.

Link to post

Hi,

 

I'm about to add an old 500GB WD drive to my array.  Although preclear passes and indicates no re-allocated sectors, there are some SMART errors reported that I'm not sure how to interpret.  Can anyone suggest if the drive is "safe" to use?

 

I've attached the full report and finish logs, but here are some of the lines of concern:

 

SMART Error Log Version: 1
ATA Error Count: 89 (device log contains only the most recent five errors)

Error 89 occurred at disk power-on lifetime: 2254 hours (93 days + 22 hours)
Error: UNC 8 sectors at LBA = 0x00deaa87 = 14592647

Error 88 occurred at disk power-on lifetime: 2254 hours (93 days + 22 hours)
Error: UNC 128 sectors at LBA = 0x00deaa77 = 14592631

 

I can't even work out if 2254 hours was a long time ago or recently...

 

Thanks for looking

preclear_rpt_WD-WCAPW4617091_2014-10-12.txt

preclear_finish_WD-WCAPW4617091_2014-10-12.txt

Link to post

Do I have to be worried about this?

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   006    Pre-fail  Always       -       24720
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       41

 

Those two attributes seem not ok to me - it is a drive that came back from RMA. Other than that: No Errors Logged

 

I have attached a zip file with all three files that were produced during preclear.

Link to post

Do I have to be worried about this?

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   006    Pre-fail  Always       -       24720
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       41

 

Those two attributes seem not ok to me - it is a drive that came back from RMA. Other than that: No Errors Logged

It takes time to understand SMART reports, and the inconsistencies within them.  For the error rate attributes, the important number is the VALUE, which for both is perfect at 100.  Their RAW numbers are internal use only, ignore them.  For other attributes, the RAW numbers are sometimes useful, but you have to understand how each attribute is used.  They are all different.

Link to post

I just picked up a couple of refurb 300GB 10000RPM drives that I intend to use as system drives in my Windows machines, but since they're refurb & only have a 90 day warranty, I want to use preclear to give them a good workout. I've searched this thread, and it appears that preclear will work just fine on a drive mounted via a SATA->USB dock, but I'm getting an error

 

root@NAS:/boot/Scripts# preclear_disk.sh -l
====================================1.15
Disks not assigned to the unRAID array
  (potential candidates for clearing)
========================================
     /dev/sdn = usb-JMicron_USB_to_ATA_ATAPI_Bridge_152D203380B6-0:0

So the drive is recognized with no issues

root@NAS:/boot/Scripts# preclear_disk.sh -c 10 /dev/sdn
Sorry: Device /dev/sdn is not responding to an fdisk -l /dev/sdn command.
You might try power-cycling it to see if it will start responding.

 

This is an older 'dock' that I borrowed from a buddy. it's a Rosewill brand (from Newegg) and is actually just a power brick & connector and a USB-SATA cable, so there's nothing 'dockey' about it. I've got the drive sitting on its anti-static bag on top of the case, and it's recognized by unRAID as soon as I power it on, but preclear doesn't seem to like it.

 

Any thoughts or suggestions?

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.