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


Recommended Posts

Hi, I was looking through the last couple of pages and it seems like this new drive I just did a 1 round preclear on, is pretty similar to axeman's, but the seek error rate and raw read error rate seem really, really high.  I know the important reallocated markers are 0.  Should I just consider this a healthy drive and use it as normal?  It is a Seagate removed from an enclosure.  I also did a preclear on a 2TB refurb WD drive that has way better looking numbers.

 

As has been often said, don't look at the RAW numbers, especially for the error rate attributes.  Only Seagate reports the raw numbers, the other manufacturers keep them hidden.  Just look at the VALUE, and how it compares with the Threshhold number.  Your drives look near perfect.

Link to comment

Hi

Bit of a silly question and a little off topic sorry, I have a feeling I know the answer to but hey, I love the pre clear script and love the fact that I know once I've ran a 3x pass on a new drive I have confidence the drives not going to die on me straight away (touch wood not happened yet).

 

Now the question, does the pre clear script only run on unraid as I would love to be able to pre clear / stress test a drive on my ubuntu box.

 

If its only an Unraid tool do you know of any other tools / scripts that do the same for ubuntu, I'm still very much a Linux noob but enjoying my ubuntu experience.

 

 

Link to comment

Hi

Bit of a silly question and a little off topic sorry, I have a feeling I know the answer to but hey, I love the pre clear script and love the fact that I know once I've ran a 3x pass on a new drive I have confidence the drives not going to die on me straight away (touch wood not happened yet).

 

Now the question, does the pre clear script only run on unraid as I would love to be able to pre clear / stress test a drive on my ubuntu box.

 

If its only an Unraid tool do you know of any other tools / scripts that do the same for ubuntu, I'm still very much a Linux noob but enjoying my ubuntu experience.

You can use the free version of unRAID to pre-clear drives.  I have two boxes I regularly pre-clear drives on.  I've done up to 5 drives at a time and they were all from the free version of unRAID.  When not pre-clearing drives they are Windows Desktop PCs.
Link to comment

Yeah I've done the same just with my media centre and a free unraid, was more interested to see if the script would work on another platform. Its a great burn in / stress test tool.

I've never tried it on another Linux distro but I suspect it will not work.

It may work, HOWEVER when you list drives eligible for clearing it will not be able to read any of the normal unRAID config files, and therefore will may list all the drives.   

 

It is especially important to know the model/serial number of the drive you wish cleared, and its affiliated /dev/sdX device name, since you'll feel pretty darned dumb/stupid/careless if you answer "Yes" to zeroing a disk holding your ubuntu installation.

Link to comment
  • 2 weeks later...

Joe, in some of the doco, it mentions fro drives over 2.2TB that GPT/4K alignment is forced and the -a and -A options are ignored.

 

I just started a pre-clear on some 3TB drives, and found that I still needed to use the "-A", and that it wasn't ignored. When I first ran pre-clear, it said that it would not 4k-align the drive. It was only after I added "-A" that it said it would.

 

Using pre-clear 1.13 with command like so:

 

./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -M 4 /dev/sdc

 

on a clean, brand new unRAID 5.0-rc15a (spun it up initially just to clear these new drives)

Link to comment

Precleared 3 4TB drives. 40:56:21, 41:13:52 were good. Then had this ugly monster 52.5 hrs. Going to run it thru a couple more passes to see if it improves or if I should return it.

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sdc
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 25C, Elapsed Time:  52:31:17
========================================================================1.13
==  ST4000DM000-1F2168    Z300FHCT
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
============================================================================
** 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 =   118     100            6        ok          182836184
    Reallocated_Sector_Ct =    72     100           10        ok          35928
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =     1     100            0        near_thresh 7983
      Temperature_Celsius =    25      25            0        near_thresh 25
   Current_Pending_Sector =    91     100            0        ok          1600
    Offline_Uncorrectable =    91     100            0        ok          1600
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
1448 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.
1600 sectors are pending re-allocation at the end of the preclear,
    a change of 1600 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
35928 sectors are re-allocated at the end of the preclear,
    a change of 35928 in the number of sectors re-allocated.

Link to comment

Looks like you should RMA this drive.

I agree.  RMA it. 

You DO win the "drive with the most reallocated sectors" I've ever seen reported contest (if it is any consolation).

Reallocated_Sector_Ct =    72    100          10        ok          35928

Current_Pending_Sector =    91    100            0        ok          1600

 

Link to comment

The results of my three drives came back as Pass (Yayy!) but I want to know why they passed. What numbers in the report should I be looking for? Also, would the report that gets emailed ever say Pass when there are possibly questionable things or vice versa?

 

I'll bet you don't like pass/fail idiot lights in cars!  You probably prefer gauges and reports that provide much more technical info, but also require much more learning to interpret!  The problem here is that SMART reports contain a LOT of info, presented in unusual ways, with a definite learning curve, and most users aren't that interested.  They just want to know if the drive is good, or needs to be replaced.

 

For now, I'm going to suggest reading back a ways through this thread, and you will find a number of scattered posts that explain various numbers.  Joe has often answered specific questions about various SMART numbers.  I've begun a wiki page called Understanding SMART Reports that should help, but it is far from complete.

Link to comment

I pre-cleared three 3TB disks all at the same time, using screen. Worked a treat.

 

Here's the results. Which, I believe are good based on what I've read.

 

Intending to use the Seagate as my Parity drive and the WD-RED's for data. Going to get some more WD-RED's as well, just want to get a different batch.

 

Interesting to see the difference in SMART values between the Seagate and the WD RED drives. Also the difference in timing. I started all three of these drives within about 3-5 minutes of each other.

 

==  ST3000DM001-9YN166
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 7:00:56 (118 MB/s)
== Last Cycle's Zeroing time   : 5:16:14 (158 MB/s)
== Last Cycle's Post Read Time : 13:35:56 (61 MB/s)
== Last Cycle's Total Time     : 25:54:07
==
== Total Elapsed Time 25:54:07
==
== Disk Start Temperature: 31C
==
== Current Disk Temperature: 32C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   116     102            6        ok          104832976
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    99     100            0        ok          1
  Airflow_Temperature_Cel =    68      69           45        near_thresh 32
      Temperature_Celsius =    32      31            0        ok          32
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. 

 

==  WDC WD30EFRX-68AX9N0
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 8:48:12 (94 MB/s)
== Last Cycle's Zeroing time   : 7:39:59 (108 MB/s)
== Last Cycle's Post Read Time : 16:22:01 (50 MB/s)
== Last Cycle's Total Time     : 32:51:13
==
== Total Elapsed Time 32:51:14
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 29C, 
==
============================================================================
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. 

 

==  WDC WD30EFRX-68AX9N0
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 9:03:15 (92 MB/s)
== Last Cycle's Zeroing time   : 7:53:56 (105 MB/s)
== Last Cycle's Post Read Time : 16:48:33 (49 MB/s)
== Last Cycle's Total Time     : 33:46:46
==
== Total Elapsed Time 33:46:46
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 27C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   123     122            0        ok          27
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. 

Link to comment

Looks like you should RMA this drive.

I agree.  RMA it. 

You DO win the "drive with the most reallocated sectors" I've ever seen reported contest (if it is any consolation).

Reallocated_Sector_Ct =    72    100          10        ok          35928

Current_Pending_Sector =    91    100            0        ok          1600

 

definitely will RMA the drive later this week. 2nd cycle bad also

 

** 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 =   117     118            6        ok          120952088
    Reallocated_Sector_Ct =    71      72           10        ok          38328
          Seek_Error_Rate =    60     100           30        ok          1254718
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =     1       1            0        near_thresh 14635
  Airflow_Temperature_Cel =    73      74           45        ok          27
      Temperature_Celsius =    27      26            0        ok          27
   Current_Pending_Sector =    94      91            0        ok          1112
    Offline_Uncorrectable =    94      91            0        ok          1112
No SMART attributes are FAILING_NOW

1632 sectors were pending re-allocation before the start of the preclear.
1624 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.
1112 sectors are pending re-allocation at the end of the preclear,
    a change of -520 in the number of sectors pending re-allocation.
36072 sectors had been re-allocated before the start of the preclear.
38328 sectors are re-allocated at the end of the preclear,
    a change of 2256 in the number of sectors re-allocated.

Link to comment

If you've been following my posts, I'm new to unRAID. I don't have it installed yet even, but I am going through the process of preclearing all of my drives on my newest server.

 

I have 24 HDD's that I'm going through the preclear process and am on my 3rd batch of 6. I can only run 6 drives at a time as my multiple controller cards are not recognized by version 4.7. And I'm not interested in testing out the development series yet. I will wait until I have run through all my preclear checks.

 

I am running each drive 6 times through preclear, as I do not want to worry much about having a failure. It takes a lot of time to recover from one, and I currently have one of my servers sitting around waiting until I have time to correct/replace one of it's faulty drives. It takes a lot to get into my servers as they are all crammed into a storage closet, at the very back. I have to move full shelving units and my deep freezer out of the way to wheel out the server rack.....then disconnect LOADS of cables. The last time I took it out of the storage room, I took some photos. Attached is one to show you what I'm talking about.

 

I'm not sure what to look for in the results, so I'm posting one of them here. I tried to post 6 in this thread (1 batch), but it exceeded the maximum allowed characters by more than 4 times!!! So if someone could point out which areas to look at, and what types of numbers to watch out for it would be greatly appreciated.

 

1st disk to finish

========================================================================1.13
== invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 6 -m [email protected] /dev/sdc
==  ST3000DM001-1CH166    W1F1GJDG
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
== Ran 6 cycles
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 6:35:04 (126 MB/s)
== Last Cycle's Zeroing time   : 5:33:50 (149 MB/s)
== Last Cycle's Post Read Time : 11:55:20 (69 MB/s)
== Last Cycle's Total Time     : 17:30:15
==
== Total Elapsed Time 112:42:31
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 31C,
==
============================================================================
** 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 =   117     100            6        ok          131179216
           Seek_Error_Rate =    63     100           30        ok          2312779
          Spin_Retry_Count =   100     100           97        near_thresh 0
          End-to-End_Error =   100     100           99        near_thresh 0
           High_Fly_Writes =    94     100            0        ok          6
   Airflow_Temperature_Cel =    69      71           45        near_thresh 31
       Temperature_Celsius =    31      29            0        ok          31
  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 6.
  0 sectors were pending re-allocation after zero of disk in cycle 1 of 6.
  0 sectors were pending re-allocation after post-read in cycle 1 of 6.
  0 sectors were pending re-allocation after zero of disk in cycle 2 of 6.
  0 sectors were pending re-allocation after post-read in cycle 2 of 6.
  0 sectors were pending re-allocation after zero of disk in cycle 3 of 6.
  0 sectors were pending re-allocation after post-read in cycle 3 of 6.
  0 sectors were pending re-allocation after zero of disk in cycle 4 of 6.
  0 sectors were pending re-allocation after post-read in cycle 4 of 6.
  0 sectors were pending re-allocation after zero of disk in cycle 5 of 6.
  0 sectors were pending re-allocation after post-read in cycle 5 of 6.
  0 sectors were pending re-allocation after zero of disk in cycle 6 of 6.
  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.
============================================================================
============================================================================
==
== S.M.A.R.T Initial Report for /dev/sdc
==
Disk: /dev/sdc
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F1GJDG
Firmware Version: CC24
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Thu Jun  6 22:32:51 2013 MDT
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:                 (  89) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                         Auto Offline data collection on/off support.
                                         Suspend Offline collection upon new
                                         command.
                                         No 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
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       -       949336
   3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
   4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       42
   5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
   7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       908
   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       5
  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
  12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       42
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   069   045    Old_age   Always       -       29 (Lifetime Min/Max 26/29)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       40
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       87
194 Temperature_Celsius     0x0022   029   040   000    Old_age   Always       -       29 (0 23 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       39058432589824
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       66
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       14474

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/sdc
==
Disk: /dev/sdc
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F1GJDG
Firmware Version: CC24
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Tue Jun 11 15:15:21 2013 MDT
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:                 (  89) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                         Auto Offline data collection on/off support.
                                         Suspend Offline collection upon new
                                         command.
                                         No 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       131179216
   3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
   4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       42
   5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
   7 Seek_Error_Rate         0x000f   063   060   030    Pre-fail  Always       -       2312779
   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       118
  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
  12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       42
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   094   094   000    Old_age   Always       -       6
190 Airflow_Temperature_Cel 0x0022   069   068   045    Old_age   Always       -       31 (Lifetime Min/Max 26/32)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       40
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       87
194 Temperature_Celsius     0x0022   031   040   000    Old_age   Always       -       31 (0 23 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       64029372448881
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       35163223210
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       76403288396

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.
==
============================================================================

Server_Rack_Full.jpg.c3410b67de3644578695b86236eff813.jpg

Link to comment

The figure that tends to be most important is whether the count of Reallocated sectors are steady (ideally 0), and also that the Pending Sectors value is 0 after a pre-clear (uRAID cannot work error free with sectors Pending Reallocation).

 

You mention using unRAID 4.7.    However that cannot handle disks larger than 2TB so you need the 5.0 release if you have any of those.  The 5.0 release is very close to going final so should be safe to use.

Link to comment

The figure that tends to be most important is whether the count of Reallocated sectors are steady (ideally 0), and also that the Pending Sectors value is 0 after a pre-clear (uRAID cannot work error free with sectors Pending Reallocation).

Thanks for the information. Ok, I think the drives I have run are good so far. The 3rd batch of 6 drives has finished since my last post. When I get home tonight, I'll be running my 4th and final batch of drives on this server through preclear.

 

You mention using unRAID 4.7.    However that cannot handle disks larger than 2TB so you need the 5.0 release if you have any of those.  The 5.0 release is very close to going final so should be safe to use.

Preclear actually does recognize my 3TB HDD's (as you can see from the detailed report I attached in my previous post). It's just unRAID that doesn't.

 

I'm hoping that the stable 5.0 release will be ready by the time I run my final set of HDD's through preclear. And when it is ready, I'll find out if it can recognize my multiple controller cards.

Link to comment

When I left for work on Friday the preclear on my 4TB hard drive was almost finished - 92% on the reading of the disk post clearing.

 

I was out of town for the weekend - just got back and found I had lost power to my apartment as my unraid server was off.

 

Is there a way to check my results - ensure that the preclear completed before losing power and that everything was OK? I used a spare computer and a free version of unraid to preclear this drive. Unraid v4.7

Link to comment

If it completed it would have logged the results in the /boot/preclear_reports directory.

Ah-ha!

========================================================================1.13
== invoked as: ./preclear_disk.sh -A /dev/sdb
==  ST4000DM000-1F2168    W3009TM3
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 9:32:25 (116 MB/s)
== Last Cycle's Zeroing time   : 8:22:56 (132 MB/s)
== Last Cycle's Post Read Time : 19:03:40 (58 MB/s)
== Last Cycle's Total Time     : 37:00:07
==
== Total Elapsed Time 37:00:07
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 36C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     100            6        ok          182808288
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    64      71           45        near_thresh 36
      Temperature_Celsius =    36      29            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. 
============================================================================

Link to comment

If it completed it would have logged the results in the /boot/preclear_reports directory.

Ah-ha!

========================================================================1.13
== invoked as: ./preclear_disk.sh -A /dev/sdb
==  ST4000DM000-1F2168    W3009TM3
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 9:32:25 (116 MB/s)
== Last Cycle's Zeroing time   : 8:22:56 (132 MB/s)
== Last Cycle's Post Read Time : 19:03:40 (58 MB/s)
== Last Cycle's Total Time     : 37:00:07
==
== Total Elapsed Time 37:00:07
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 36C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     100            6        ok          182808288
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    64      71           45        near_thresh 36
      Temperature_Celsius =    36      29            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. 
============================================================================

Looks great!!!

 

Joe L.

Link to comment

Hi All,

 

Just had a slightly suspect pre-clear report (my first, thankfully) and I'd really appreciate an opinion on this particular disk.

I was planning to run another pre-clear to see if I get the same result, but haven't done this yet.

 

My concern is around some UNC reads and writes that are logged on the drive.

 

I've included the pre and post SMART results, as well as the pre-clear report.

The thing that I'm concerning about is that the sectors pending re-allocation have gone down following pre-clear.

I was sort of expecting that these sectors would have been re-allocated.

 

pre-clear report

========================================================================1.13
== invoked as: ./preclear_disk.sh -A /dev/sdc
==  WDC WD30EZRX-00MMMB0    WD-WMAWZXXXXXXX
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 9:16:43 (89 MB/s)
== Last Cycle's Zeroing time   : 9:02:10 (92 MB/s)
== Last Cycle's Post Read Time : 21:30:38 (38 MB/s)
== Last Cycle's Total Time     : 39:50:31
==
== Total Elapsed Time 39:50:31
==
== Disk Start Temperature: 24C
==
== Current Disk Temperature: 32C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Seek_Error_Rate =   100     200            0        ok          0
      Temperature_Celsius =   120     128            0        ok          32
No SMART attributes are FAILING_NOW

7 sectors were pending re-allocation before the start of the preclear.
7 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,
    a change of -7 in the number of sectors pending re-allocation.
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. 
============================================================================

 

 

I've attached the SMART reports, as they were too large to be posted as part of the message content.

 

Any thoughts on this would be much appreciated.

 

Andy.

preclear_finish.txt

preclear_start.txt

Link to comment

Those results look good.

 

It is not at all unusual for sectors that were flagged as pending re-allocation actually turn out to be OK when they are next written.  As long as they do not keep re-appearing I would not worry.  The original failure that resulted in them could have been due to some outside factor.  However it is worth keeping an eye on them.

Link to comment

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.