Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

Hi all. I'm a new member here and just getting my first unRAID server set up. I've been researching unRAID for years now, but just finally took the plunge to gather all my components and set everything up.

 

Anyways, I ran the preclear script on my first three drives. After talking with some other people, I think I know what to look for but thought I would run it by the members here to see what you thought. I know some say any sectors pending reallocation is bad, but is 2 in one instance cause enough not to use the drive? Any thoughts are appreciated!

 

I think the disk is fine, just false positives.  It's rather unusual to suddenly find them on a read pass, just after all sector media has been refreshed.  But on subsequent testing, they were fine and put back online.  The only thing I can think of is a possible power issue during the second post-read.  Any power outages or lightning strikes around then?

Share this post


Link to post

No, and I was preclearing two other drives at the same time that were both were 0's across the board. Think its worth running another preclear cycle or does the rest of the information pretty much guarantee its a false positive? Thanks for the help!

Share this post


Link to post

No, and I was preclearing two other drives at the same time that were both were 0's across the board. Think its worth running another preclear cycle or does the rest of the information pretty much guarantee its a false positive? Thanks for the help!

 

I'll leave that up to you.  You have already run another Preclear pass on it, as the 2 sectors showed up at the end of the second pass.  I suspect you'll feel more confident after one more pass.

Share this post


Link to post

I have a report I would like for you guys to look at (attached), I might be miss reading it, but it doesn't look very good. I picked this up used for $50, so I could pass it up. Please let me know.

Thanks!

The drive looks great!  Enjoy it.  (I'll bet you looked at those RAW numbers for the read and seek error rates?  Don't!  They mean nothing to us, only to the manufacturers, and they are typical of Seagates.  What's important for the error rates is the VALUE, and both are perfect!)

Share this post


Link to post

... I'll bet you looked at those RAW numbers for the read and seek error rates?  Don't!  They mean nothing to us, only to the manufacturers, and they are typical of Seagates.  What's important for the error rates is the VALUE, and both are perfect!

 

Agree.  Seagate reports several values that other manufacturers simply don't show -- these are among those (along with high fly writes).  You can ignore the raw values (ALL drives have errors that are corrected by ECC) ==> the only thing that matters is the "Value" ... if these are good, the drive's fine.

 

Share this post


Link to post

I have a report I would like for you guys to look at (attached), I might be miss reading it, but it doesn't look very good. I picked this up used for $50, so I could pass it up. Please let me know.

Thanks!

The drive looks great!  Enjoy it.  (I'll bet you looked at those RAW numbers for the read and seek error rates?  Don't!  They mean nothing to us, only to the manufacturers, and they are typical of Seagates.  What's important for the error rates is the VALUE, and both are perfect!)

 

... I'll bet you looked at those RAW numbers for the read and seek error rates?  Don't!  They mean nothing to us, only to the manufacturers, and they are typical of Seagates.  What's important for the error rates is the VALUE, and both are perfect!

 

Agree.  Seagate reports several values that other manufacturers simply don't show -- these are among those (along with high fly writes).  You can ignore the raw values (ALL drives have errors that are corrected by ECC) ==> the only thing that matters is the "Value" ... if these are good, the drive's fine.

 

 

Sweet! Your right, that's what I was looking at! Thank you both, for your help!

Share this post


Link to post

Hi guys. Just got myself an 8TB Seagate Archive drive and after a long preclear (136 hours!) I just wanted to double check my results were good before I stuck it in as my new parity drive. I think these look perfectly fine?

 

========================================================================1.15b
== invoked as: ./preclear_bjp.sh -f -A -c 3 /dev/sdd
== ST8000AS0002-1NA17Z   Z8405JVN
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 1 
== Ran 3 cycles
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 20:11:47 (110 MB/s)
== Last Cycle's Zeroing time   : 16:58:37 (130 MB/s)
== Last Cycle's Post Read Time : 21:38:49 (102 MB/s)
== Last Cycle's Total Time     : 38:42:39
==
== Total Elapsed Time 135:57:31
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 36C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   116     100            6        ok          103093464
          Seek_Error_Rate =    72     100           30        ok          8628490947
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    64      72           45        near_thresh 36
      Temperature_Celsius =    36      28            0        ok          36
   Hardware_ECC_Recovered =   116     100            0        ok          103093464
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 3.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
0 sectors were pending re-allocation after post-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
0 sectors were pending re-allocation after post-read in cycle 2 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
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. 
============================================================================

Share this post


Link to post

Hi guys. Just got myself an 8TB Seagate Archive drive and after a long preclear (136 hours!) I just wanted to double check my results were good before I stuck it in as my new parity drive. I think these look perfectly fine?

 

Drive looks great!

Share this post


Link to post

I decided to do a fresh install of unRAID.  I figured I would move my data off the server and preclear all the drives.  I was hoping for some input as to which drives I should consider retiring.  I did preclear most of these at the same time.  Any input wold be greatly appreciated.

 

Thanks,

Albin

 

1 sda
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sda
=               cycle 1 of 1, partition start on sector 63
= 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: 40C, Elapsed Time:  19:01:52
========================================================================1.15
== ST3750330NS   9QK0D9WY
== Disk /dev/sda has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     119            6        ok          120090706
         Spin_Retry_Count =   100     100           97        near_thresh 8
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    60      64           45        near_thresh 40
      Temperature_Celsius =    40      36            0        ok          40
   Hardware_ECC_Recovered =    45      34            0        ok          120090706
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.
1 sector had been re-allocated before the start of the preclear.
4 sectors are re-allocated at the end of the preclear,
    a change of 3 in the number of sectors re-allocated.
=======================================================================END sda
2 sdb
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdb
=               cycle 1 of 1, partition start on sector 63
= 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: 34C, Elapsed Time:  14:16:15
========================================================================1.15
== ST3500630NS   5QG1HKD0
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    66      68           45        near_thresh 34
      Temperature_Celsius =    34      32            0        ok          34
   Hardware_ECC_Recovered =    57      71            0        ok          8218259
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.
1 sector had been re-allocated before the start of the preclear.
1 sector is re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================END sdb
3 sdd
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdd
=               cycle 1 of 1, partition start on sector 63
= 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: 44C, Elapsed Time:  14:09:42
========================================================================1.15
== ST3500630AS   9QG0GA2R
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    56      62           45        near_thresh 44
      Temperature_Celsius =    44      38            0        ok          44
   Hardware_ECC_Recovered =    53      65            0        ok          7699123
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.
114 sectors had been re-allocated before the start of the preclear.
114 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================END sdd
4 sde
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sde
=               cycle 1 of 1, partition start on sector 63
= 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: 45C, Elapsed Time:  18:32:23
========================================================================1.15
== ST3750640NS   5QD0ELXR
== Disk /dev/sde has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    55      58           45        near_thresh 45
      Temperature_Celsius =    45      42            0        ok          45
   Hardware_ECC_Recovered =    62      65            0        ok          64838030
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.
=======================================================================END sde
5 sdf
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdf
=               cycle 1 of 1, partition start on sector 63
= 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: 39C, Elapsed Time:  22:37:55
========================================================================1.15
== ST31000340AS   9QJ1VHF6
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     110            6        ok          183656712
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    61      62           45        near_thresh 39
      Temperature_Celsius =    39      38            0        ok          39
   Hardware_ECC_Recovered =    50      36            0        ok          183656712
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.
=======================================================================END sdf
6 sdh
================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdh
=               cycle 1 of 1, partition start on sector 63
= 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: 26C, Elapsed Time:  16:30:41
========================================================================1.15
== SAMSUNGHD502IJ   S1PZJDWQ669795
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    74      77            0        ok          26
      Temperature_Celsius =    74      76            0        ok          26
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.
=======================================================================END sdh

drives_1_thru_6_.txt

Share this post


Link to post

I decided to do a fresh install of unRAID.  I figured I would move my data off the server and preclear all the drives.  I was hoping for some input as to which drives I should consider retiring.  I did preclear most of these at the same time.  Any input wold be greatly appreciated.

 

Thanks,

Albin

 

I took at look at your smart reports and you can see my comments below.

 

The drive sizes of the drives included are as follows:

sda - 750G

sdb - 500G

sdd - 500G

sde - 750G

sdf - 1T

sdh - 500G

 

Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.

 

But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.

 

Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.

 

reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.

 

pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.

 

temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.

 

The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.

 

If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.

 

Let me know if any questions on the information below:

 

1 sda

== ST3750330NS   9QK0D9WY
== Disk /dev/sda has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     119            6        ok          120090706
         Spin_Retry_Count =   100     100           97        near_thresh 8
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    60      64           45        near_thresh 40
      Temperature_Celsius =    40      36            0        ok          40
   Hardware_ECC_Recovered =    45      34            0        ok          120090706
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.
1 sector had been re-allocated before the start of the preclear.
4 sectors are re-allocated at the end of the preclear,
    a change of 3 in the number of sectors re-allocated.
=======================================================================

This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).

 

2 sdb

== ST3500630NS   5QG1HKD0
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    66      68           45        near_thresh 34
      Temperature_Celsius =    34      32            0        ok          34
   Hardware_ECC_Recovered =    57      71            0        ok          8218259
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.
1 sector had been re-allocated before the start of the preclear.
1 sector is re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.

 

3 sdd

== ST3500630AS   9QG0GA2R
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    56      62           45        near_thresh 44
      Temperature_Celsius =    44      38            0        ok          44
   Hardware_ECC_Recovered =    53      65            0        ok          7699123
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.
114 sectors had been re-allocated before the start of the preclear.
114 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.

 

4 sde

== ST3750640NS   5QD0ELXR
== Disk /dev/sde has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    55      58           45        near_thresh 45
      Temperature_Celsius =    45      42            0        ok          45
   Hardware_ECC_Recovered =    62      65            0        ok          64838030
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.
=======================================================================

No signs of failure.

 

5 sdf

== ST31000340AS   9QJ1VHF6
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     110            6        ok          183656712
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    61      62           45        near_thresh 39
      Temperature_Celsius =    39      38            0        ok          39
   Hardware_ECC_Recovered =    50      36            0        ok          183656712
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.
=======================================================================

No signs of failure.

 

6 sdh

== SAMSUNGHD502IJ   S1PZJDWQ669795
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    74      77            0        ok          26
      Temperature_Celsius =    74      76            0        ok          26
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.
=======================================================================

No signs of failure.

Share this post


Link to post

Thanks Bjp999

 

I appreciate you taking the time to reply.  The information you provided was very helpful. 

I am going to run more preclears on the drives you suggested.  I will let you know what happens.

 

Thanks,

 

Albin

 

 

I took at look at your smart reports and you can see my comments below.

 

The drive sizes of the drives included are as follows:

sda - 750G

sdb - 500G

sdd - 500G

sde - 750G

sdf - 1T

sdh - 500G

 

Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.

 

But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.

 

Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.

 

reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.

 

pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.

 

temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.

 

The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.

 

If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.

 

Let me know if any questions on the information below:

 

1 sda

== ST3750330NS   9QK0D9WY
== Disk /dev/sda has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     119            6        ok          120090706
         Spin_Retry_Count =   100     100           97        near_thresh 8
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    60      64           45        near_thresh 40
      Temperature_Celsius =    40      36            0        ok          40
   Hardware_ECC_Recovered =    45      34            0        ok          120090706
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.
1 sector had been re-allocated before the start of the preclear.
4 sectors are re-allocated at the end of the preclear,
    a change of 3 in the number of sectors re-allocated.
=======================================================================

This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).

 

2 sdb

== ST3500630NS   5QG1HKD0
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    66      68           45        near_thresh 34
      Temperature_Celsius =    34      32            0        ok          34
   Hardware_ECC_Recovered =    57      71            0        ok          8218259
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.
1 sector had been re-allocated before the start of the preclear.
1 sector is re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.

 

3 sdd

== ST3500630AS   9QG0GA2R
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    56      62           45        near_thresh 44
      Temperature_Celsius =    44      38            0        ok          44
   Hardware_ECC_Recovered =    53      65            0        ok          7699123
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.
114 sectors had been re-allocated before the start of the preclear.
114 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.

 

4 sde

== ST3750640NS   5QD0ELXR
== Disk /dev/sde has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    55      58           45        near_thresh 45
      Temperature_Celsius =    45      42            0        ok          45
   Hardware_ECC_Recovered =    62      65            0        ok          64838030
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.
=======================================================================

No signs of failure.

 

5 sdf

== ST31000340AS   9QJ1VHF6
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     110            6        ok          183656712
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    61      62           45        near_thresh 39
      Temperature_Celsius =    39      38            0        ok          39
   Hardware_ECC_Recovered =    50      36            0        ok          183656712
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.
=======================================================================

No signs of failure.

 

6 sdh

== SAMSUNGHD502IJ   S1PZJDWQ669795
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    74      77            0        ok          26
      Temperature_Celsius =    74      76            0        ok          26
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.
=======================================================================

No signs of failure.

Share this post


Link to post

I decided to do a fresh install of unRAID.  I figured I would move my data off the server and preclear all the drives.  I was hoping for some input as to which drives I should consider retiring.  I did preclear most of these at the same time.  Any input wold be greatly appreciated.

 

Thanks,

Albin

 

I took at look at your smart reports and you can see my comments below.

 

The drive sizes of the drives included are as follows:

sda - 750G

sdb - 500G

sdd - 500G

sde - 750G

sdf - 1T

sdh - 500G

 

Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.

 

But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.

 

Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.

 

reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.

 

pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.

 

temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.

 

The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.

 

If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.

 

Let me know if any questions on the information below:

 

1 sda

== ST3750330NS   9QK0D9WY
== Disk /dev/sda has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     119            6        ok          120090706
         Spin_Retry_Count =   100     100           97        near_thresh 8
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    60      64           45        near_thresh 40
      Temperature_Celsius =    40      36            0        ok          40
   Hardware_ECC_Recovered =    45      34            0        ok          120090706
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.
1 sector had been re-allocated before the start of the preclear.
4 sectors are re-allocated at the end of the preclear,
    a change of 3 in the number of sectors re-allocated.
=======================================================================

This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).

 

2 sdb

== ST3500630NS   5QG1HKD0
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    66      68           45        near_thresh 34
      Temperature_Celsius =    34      32            0        ok          34
   Hardware_ECC_Recovered =    57      71            0        ok          8218259
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.
1 sector had been re-allocated before the start of the preclear.
1 sector is re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.

 

3 sdd

== ST3500630AS   9QG0GA2R
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    56      62           45        near_thresh 44
      Temperature_Celsius =    44      38            0        ok          44
   Hardware_ECC_Recovered =    53      65            0        ok          7699123
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.
114 sectors had been re-allocated before the start of the preclear.
114 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
=======================================================================

Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.

 

4 sde

== ST3750640NS   5QD0ELXR
== Disk /dev/sde has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    55      58           45        near_thresh 45
      Temperature_Celsius =    45      42            0        ok          45
   Hardware_ECC_Recovered =    62      65            0        ok          64838030
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.
=======================================================================

No signs of failure.

 

5 sdf

== ST31000340AS   9QJ1VHF6
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     110            6        ok          183656712
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    61      62           45        near_thresh 39
      Temperature_Celsius =    39      38            0        ok          39
   Hardware_ECC_Recovered =    50      36            0        ok          183656712
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.
=======================================================================

No signs of failure.

 

6 sdh

== SAMSUNGHD502IJ   S1PZJDWQ669795
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 63
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    74      77            0        ok          26
      Temperature_Celsius =    74      76            0        ok          26
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.
=======================================================================

No signs of failure.

 

I ran 3 more cycles on sda sdb and sdd.  There were no changes to the sectors re-allocated for these drives.  (the numbers held steady)!  I attached results for cycle 3 and 4.

1_sda_ST3750330NS___9QK0D9WY_Pass_3_and_4_no_new.txt

3_sdd_ST3500630AS___9QG0GA2R_pass_3_and_4_no_new.txt

2_sdb_ST3500630NS___5QG1HKD0_pass_3_and_4_no_new.txt

Share this post


Link to post

Just cleared 3 new drives, can someone take a look at the result for me? Thanks

 

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD10EFRX-68FYTN0
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Aug 11 16:36:35 2015 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: 		(14160) 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: 	 ( 162) 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       -       2
  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       -       29
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       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   113   111   000    Old_age   Always       -       30
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.

 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD40EFRX-68WT0N0
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Aug 14 23:35:02 2015 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: 		(53940) 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: 	 ( 539) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	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       -       2
  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       -       108
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       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   110   108   000    Old_age   Always       -       42
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.

 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD60EFRX-68MYMN1
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: 3.0 Gb/s)
Local Time is:    Sun Aug 16 06:37:32 2015 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: 		( 5984) 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: 	 ( 713) 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       -       4
  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       -       139
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       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   113   110   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.

Share this post


Link to post

Just cleared 3 new drives, can someone take a look at the result for me? Thanks

 

Can you post the 'preclear rpt' files using the insert code? Makes it easier for people to read.

 

 

Here is a sample of mine.

 

== WDCWD30EFRX-68AX9N0 
== Disk /dev/sdb 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  : 9:00:25 (92 MB/s)
== Last Cycle's Zeroing time   : 7:27:26 (111 MB/s)
== Last Cycle's Post Read Time : 13:41:57 (60 MB/s)
== Last Cycle's Total Time     : 30:10:47
==
== Total Elapsed Time 30:10:47
==
== Disk Start Temperature: 26C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   121     124            0        ok          29
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.
89 sectors are pending re-allocation at the end of the preclear,
    a change of 89 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. 
============================================================================

 

And after a second pass

 

== WDCWD30EFRX-68AX9N0
== Disk /dev/sdb 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  : 9:14:40 (90 MB/s)
== Last Cycle's Zeroing time   : 7:27:32 (111 MB/s)
== Last Cycle's Post Read Time : 13:20:30 (62 MB/s)
== Last Cycle's Total Time     : 30:03:42
==
== Total Elapsed Time 30:03:42
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 27C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   123     121            0        ok          27
No SMART attributes are FAILING_NOW

89 sectors were pending re-allocation before the start of the preclear.
93 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 -89 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. 
============================================================================

 

 

Disk has around 11150 Hours on it.

 

Running the 3rd preclear now to see what it comes up with. Using the preclear_bjp script to cut down on time a little.

 

Any advice would be appreciated. Ive never had a disk with any sector issues after a preclear.

Share this post


Link to post

All look good. Maybe a tad warm, but nothing to worry about.

 

Just cleared 3 new drives, can someone take a look at the result for me? Thanks

 

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD10EFRX-68FYTN0
Firmware Version: 82.00A82
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Aug 11 16:36:35 2015 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: 		(14160) 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: 	 ( 162) 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       -       2
  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       -       29
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       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   113   111   000    Old_age   Always       -       30
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.

 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD40EFRX-68WT0N0
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Aug 14 23:35:02 2015 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: 		(53940) 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: 	 ( 539) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	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       -       2
  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       -       108
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       -       2
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   110   108   000    Old_age   Always       -       42
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.

 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD60EFRX-68MYMN1
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: 3.0 Gb/s)
Local Time is:    Sun Aug 16 06:37:32 2015 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: 		( 5984) 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: 	 ( 713) 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       -       4
  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       -       139
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       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   113   110   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.

Share this post


Link to post

What should be the ideal temp for the WD red drives? I notice they are around 5-8 degrees cooler than the WD green, I am looking to install some more fans in my case, currently only have 2 fans for 8 drives.

Share this post


Link to post

What should be the ideal temp for the WD red drives? I notice they are around 5-8 degrees cooler than the WD green, I am looking to install some more fans in my case, currently only have 2 fans for 8 drives.

 

No hard and fast rules. And some argue temps are a minor issue. Others say that it is the delta temp (ie. coolest to warmest) that makes the most difference, not the absolute max temperature. .

 

My personal experience is that cooler is better. My drives drop into the upper teens while spun down in the winter, running up to mid 30s running hard in the summer. I have had good longevity experience - although anything a single person experiences with a few dozen drives would be considered anecdotal.

 

All that being said, I like to see drives running in 30s. 45+ would lead me to advise more cooling. 50 I'd be worried and feel the situation was urgent. I have a couple of high capacity 7200RPM drives that run in the low 40s and I am ok with that. Your drives at 42 are in that "close to being too warm" range on my scale. I have no experience with REDS, but believe they are 5x00 RPM drives and should be cooler running.

 

I suggest people use drive cages (5in3s or 4in3s). Each unit has a built in fan. Some cool better than others, but most do a good job. They are also very important if a drive fails and you want to replace it. It is so easy to knock something loose swapping a drive and create big-time headaches trying to recover. The drive cages all but remove the risk of a simple drive swap causing further problems.

Share this post


Link to post

57K re-allocated sectors?? 

 

Just precleared a Seagate 3tb that had been in use for several years and was working fine.  I ran mymain and discovered there were 57240 reallocated sectors.  I quickly replaced this drive thinking it was dying, but a preclear doesn't note anything else wrong with it.  I have never seen this level of reallocated sectors before. 

 

Is it safe to use?

 

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.
57240 sectors had been re-allocated before the start of the preclear.
57240 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

Share this post


Link to post

57K re-allocated sectors?? 

 

Just precleared a Seagate 3tb that had been in use for several years and was working fine.  I ran mymain and discovered there were 57240 reallocated sectors.  I quickly replaced this drive thinking it was dying, but a preclear doesn't note anything else wrong with it.  I have never seen this level of reallocated sectors before. 

 

Is it safe to use?

 

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.
57240 sectors had been re-allocated before the start of the preclear.
57240 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

 

You may want to Preclear it one more time, see if you get the same result with no change.  But after that, it's going to be your decision.

 

I have several drives with corrupted SMART stuff, that I've lived with for quite awhile.  One drive was hit indirectly by a lightning spike, ruined the SMART firmware, but nothing otherwise (had to turn off SMART detection on that computer or it wouldn't boot).  It slowly clicks 7 times on power up, then runs perfectly and fast, for the last 3 to 4 years.  Another drive suddenly showed ALL spares used, max number of reallocated sectors, yet tests fine.  Another has temps that jump around 30 degrees once or twice a year, was 96 C, now 61 C, but actually same temps as others (about 33 C).  In each case, I saved anything important off, and used them only for non-vital stuff, until roughly a year had gone by, then trusted them with anything.  One is finally dying, but I got an extra 3 odd years from it, with no losses.

 

Or you can RMA it.

Share this post


Link to post

57K re-allocated sectors?? 

 

Just precleared a Seagate 3tb that had been in use for several years and was working fine.  I ran mymain and discovered there were 57240 reallocated sectors.  I quickly replaced this drive thinking it was dying, but a preclear doesn't note anything else wrong with it.  I have never seen this level of reallocated sectors before. 

 

Is it safe to use?

 

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.
57240 sectors had been re-allocated before the start of the preclear.
57240 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

 

I would say that 57,240 is too many reallocated sectors. I would suggest getting a warranty replacement if the drive is eligible.

 

The fact that it did not reallocate any more is a good sign, but it could also mean that there are no spare sectors to reallocate. No one has ever posted a definitive way to tell the number of spare sectors available. It may vary by drive model.

 

I'd like the see the actual smart report and see the drive's normalized value. It may be approaching the failure level.

 

If a drive has a few, even up to several hundred reallocated sectors the hold steady for 3 consecutive parity checks or preclear cycles, I'd keep using it (but continue to monitor). But I don't feel the same way about 57,000+. I'd say that 300, maybe 1000 max, would be my cutoff for trusting a drive with reallocations. Frankly I have never personally seen a drive with more than a very small number (single digit) of reallocations that don't have growing reallocations on every full disk operation. But I have seen forum posts with greater numbers. But nothing close to 1000 that I can remember.

Share this post


Link to post

I'm sorry, I realize I skipped right over the obvious.  The count of 57240 is clearly not a real number, roughly 10 times the possible maximum, just a random number, indicating corruption in the SMART system.  I completely forgot to state that, just assumed others would automatically recognize that.  It would be interesting to see the SMART report, see what other corruption it reveals.

 

It wouldn't surprise me if there actually aren't ANY sectors reallocated, but probably going to be hard to tell for sure.

Share this post


Link to post

I'm sorry, I realize I skipped right over the obvious.  The count of 57240 is clearly not a real number, roughly 10 times the possible maximum, just a random number, indicating corruption in the SMART system.  I completely forgot to state that, just assumed others would automatically recognize that.  It would be interesting to see the SMART report, see what other corruption it reveals.

 

It wouldn't surprise me if there actually aren't ANY sectors reallocated, but probably going to be hard to tell for sure.

 

You might be right - that it is not a real number of reallocated sectors. But that does not mean that the SMART data was corrupted. We see most of the other values are 0, just like they are supposed to be. My guess is that some condition occurred to cause that number to increment to that level. All software has bugs, and the more used a piece of software is, the more defects are reported and fixed, and the more reliable the software becomes. SMART firmware is arguably one of the the least used piece of software. (Maybe not least used, but most users don't even know about smart attributes, and even those familiar with them, refer to them infrequently.) So when defects in the smart system occur, they are often not found or reported.

 

I'd still like to see an actual smart report for other clues as to what might be happening. I'd certainly find it hard to trust the drive.

Share this post


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.