Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

Hey guys, I'm hoping someone can help me.

 

I've precleared a couple of disks and the preclear reports that they were cleared successfully. However when I run preclear_disk.sh - t on them it reports them as not being precleared. If I stick them in the server it attempts to do a complete format, so for some reason it appears that the preclear flag is not being written correctly.

 

Any ideas??

preclear_reports.zip

Share this post


Link to post

Hey guys, I'm hoping someone can help me.

 

I've precleared a couple of disks and the preclear reports that they were cleared successfully. However when I run preclear_disk.sh - t on them it reports them as not being precleared. If I stick them in the server it attempts to do a complete format, so for some reason it appears that the preclear flag is not being written correctly.

 

Any ideas??

Don't have anything to say about your actual question, but I do want to comment on your use of the word format.

 

Formatting a disk when adding it to the array is the expected behavior. Since you said it fails the preclear -t I assume you instead meant that it is trying to clear the disk.

 

Formatting and clearing are completely different and unrelated operations. A formatted disk and a clear disk are very different things.

 

Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. Understanding this can help you avoid mistakes in the future.

 

 

Share this post


Link to post

Check this one... :o

 

== invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 /dev/sdb
== ST3500630AS   9QG2G37S
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 2:30:11 (55 MB/s)
== Last Cycle's Zeroing time   : 2:09:40 (64 MB/s)
== Last Cycle's Post Read Time : 4:44:04 (29 MB/s)
== Last Cycle's Total Time     : 9:24:56
==
== Total Elapsed Time 9:24:56
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: -->43<--C, 
==
============================================================================
** 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 =    57      70           45        In_the_past 43
      Temperature_Celsius =    43      30            0        ok          43
   Hardware_ECC_Recovered =    66      84            0        ok          30005550
   Current_Pending_Sector =     1       1            0        near_thresh 4294967295
    Offline_Uncorrectable =     1       1            0        near_thresh 4294967295
No SMART attributes are FAILING_NOW

4294967295 sectors were pending re-allocation before the start of the preclear.
4294967295 sectors were pending re-allocation after pre-read in cycle 1 of 1.
4294967295 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
4294967295 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 SMART attributes are FAILING_NOW" but I guess, I won't trust this drive...

Preclear_ST3500630AS.zip

Share this post


Link to post

Check this one... :o

 

== invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 /dev/sdb
== ST3500630AS   9QG2G37S
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 2:30:11 (55 MB/s)
== Last Cycle's Zeroing time   : 2:09:40 (64 MB/s)
== Last Cycle's Post Read Time : 4:44:04 (29 MB/s)
== Last Cycle's Total Time     : 9:24:56
==
== Total Elapsed Time 9:24:56
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: -->43<--C, 
==
============================================================================
** 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 =    57      70           45        In_the_past 43
      Temperature_Celsius =    43      30            0        ok          43
   Hardware_ECC_Recovered =    66      84            0        ok          30005550
   Current_Pending_Sector =     1       1            0        near_thresh 4294967295
    Offline_Uncorrectable =     1       1            0        near_thresh 4294967295
No SMART attributes are FAILING_NOW

4294967295 sectors were pending re-allocation before the start of the preclear.
4294967295 sectors were pending re-allocation after pre-read in cycle 1 of 1.
4294967295 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
4294967295 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 SMART attributes are FAILING_NOW" but I guess, I won't trust this drive...

4294967295 is FFFFFFFF so unlikely to be real. That number is what you would get if you had a 32bit zero and then subtracted one from it. I have seen similar with other attributes, where it looks like something that was 16bit zero got decremented by 2 and so became FFFE (65534), for example. Must be some bug in the drive firmware. Don't know if another preclear cycle would make any difference or not.

Share this post


Link to post

Precleared another drive of the same build some time ago, with a different firmware on a different rig.

 

========================================================================1.15b
== invoked as: ./preclear_bjp.sh -f -A /dev/sdd
== ST3500630AS   9QG4RFZ9
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 3:26:18 (40 MB/s)
== Last Cycle's Zeroing time   : 2:15:42 (61 MB/s)
== Last Cycle's Post Read Time : 2:40:48 (51 MB/s)
== Last Cycle's Total Time     : 8:23:50
==
== Total Elapsed Time 8:23:50
==
== Disk Start Temperature: 44C
==
== Current Disk Temperature: -->47<--C, 
==
============================================================================
** 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 =    53      56           45        In_the_past 47
      Temperature_Celsius =    47      44            0        ok          47
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. 
============================================================================

ST3500630AS_9QG4RFZ9.ZIP

Share this post


Link to post

Precleared another drive of the same build some time ago, with a different firmware on a different rig...

When I said I had seen similar, I meant similar reports on the forum. I have personally never had this with any drive of any kind. And my ideas about the cause is speculation. It's just that another interpretation of that number you reported is -1. That is the way -1 is represented in 32bit.

 

Share this post


Link to post

Precleared another drive of the same build some time ago, with a different firmware on a different rig...

When I said I had seen similar, I meant similar reports on the forum. I have personally never had this with any drive of any kind. And my ideas about the cause is speculation. It's just that another interpretation of that number you reported is -1. That is the way -1 is represented in 32bit.

 

Sure, got your point!

There was no specific/additional reason for my second post. :-)

Share this post


Link to post

Just ran pre-clear via the plugin on a new seagate 2TB...everything look okay here?

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdg
=               cycle 1 of 1, partition start on sector 64
= 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: 35C, Elapsed Time:  16:15:26
========================================================================1.15
== ST2000DM001-1ER164   Z5601NS2
== Disk /dev/sdg has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdg  /tmp/smart_finish_sdg
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     100            6        ok          154923144
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    65      76           45        near_thresh 35
      Temperature_Celsius =    35      24            0        ok          35
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.
root@Tower:/usr/local/emhttp#

Share this post


Link to post

Just ran pre-clear via the plugin on a new seagate 2TB...everything look okay here?

 

Looks perfect!

Share this post


Link to post

I had a 2Tb drive which was mounted with unassigned devices which showed some smart warnings. It was on a possibly dodgy Marvell controller, so I swapped it to a new LSI controller and precleared three times. Here is the report:

 

== Disk /dev/sdb has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Seek_Error_Rate =   100     200            0        ok          0
      Temperature_Celsius =   122     124            0        ok          28
No SMART attributes are FAILING_NOW
5 sectors were pending re-allocation before the start of the preclear.
5 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,
    a change of -5 in the number of sectors pending re-allocation.
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.

 

Is this disk ok? Was it the dodgy controller or is the disk dubious?

 

V

Share this post


Link to post

I had a 2Tb drive which was mounted with unassigned devices which showed some smart warnings. It was on a possibly dodgy Marvell controller, so I swapped it to a new LSI controller and precleared three times. Here is the report:

 

== Disk /dev/sdb has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Seek_Error_Rate =   100     200            0        ok          0
      Temperature_Celsius =   122     124            0        ok          28
No SMART attributes are FAILING_NOW
5 sectors were pending re-allocation before the start of the preclear.
5 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,
    a change of -5 in the number of sectors pending re-allocation.
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.

 

Is this disk ok? Was it the dodgy controller or is the disk dubious?

I'd say the drive is fine.  It showed 5 questionable sectors at the start, but the first zeroing resulted in none, not remapped either.  Very likely, they were the result of a power spike that scrambled them, not actual bad sectors.  Then you did 2 more Preclears without any changes or errors found.

Share this post


Link to post

Just finished preclearing a drive.

 

Got the drive out of an old computer...is it OK/safe to use in my server??? Seems like some things are "near threshold".

 

Thanks in advance!

 

========================================================================1.15

== invoked as: ./preclear_disk.sh /dev/sdb

== ST3500413AS  Z2A8GC0E

== Disk /dev/sdb has been successfully precleared

== with a starting sector of 64

== Ran 1 cycle

==

== Using :Read block size = 8388608 Bytes

== Last Cycle's Pre Read Time  : 1:27:09 (95 MB/s)

== Last Cycle's Zeroing time  : 1:17:55 (106 MB/s)

== Last Cycle's Post Read Time : 3:05:32 (44 MB/s)

== Last Cycle's Total Time    : 5:51:37

==

== Total Elapsed Time 5:51:37

==

== Disk Start Temperature: 26C

==

== Current Disk Temperature: 30C,

==

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

** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Raw_Read_Error_Rate =  117    114            6        ok          151669370

        Spin_Retry_Count =  100    100          97        near_thresh 0

        End-to-End_Error =  100    100          99        near_thresh 0

  Airflow_Temperature_Cel =    70      74          45        near_thresh 30

      Temperature_Celsius =    30      26            0        ok          30

  Hardware_ECC_Recovered =    51      41            0        ok          151669370

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.

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

 

 

Share this post


Link to post

 

 

Just finished preclearing a drive.

 

Got the drive out of an old computer...is it OK/safe to use in my server??? Seems like some things are "near threshold".

 

Thanks in advance!

 

Looks fine.

 

Share this post


Link to post

I just put a new 4 Tb Seagate SHDD in the system. The five year warranty is great even if the sdd part of drive is not used.

The problem I am having it is saying it is busy when I try to start a preclear process. It has never been part of the array or

formatted.  Reboot does not help. I can be chosen as a array drive but I want to preclear it first.

I checked the reported capacity and it is the same as the normal 4 TB drives.

john

 

Share this post


Link to post

I just put a new 4 Tb Seagate SHDD in the system. The five year warranty is great even if the sdd part of drive is not used.

The problem I am having it is saying it is busy when I try to start a preclear process. It has never been part of the array or

formatted.  Reboot does not help. I can be chosen as a array drive but I want to preclear it first.

I checked the reported capacity and it is the same as the normal 4 TB drives.

john

 

Are you using 6.2-beta? If yes use the new preclear beta plugin or patch the script.

Share this post


Link to post

This is my latest drive that i plan on using over my 6tb parity looks good to me what do you guys think?

========================================================================1.15b
== invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 -f -J /dev/sdo
== WDCWD80EFZX-68UW8N0   VKJG57DX
== Disk /dev/sdo 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  : 16:57:12 (131 MB/s)
== Last Cycle's Zeroing time   : 15:31:01 (143 MB/s)
== Last Cycle's Post Read Time : 19:27:57 (114 MB/s)
== Last Cycle's Total Time     : 51:57:08
==
== Total Elapsed Time 51:57:08
==
== Disk Start Temperature: 31C
==
== Current Disk Temperature: 35C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdo  /tmp/smart_finish_sdo
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
   Throughput_Performance =   129     100           54        ok          124
      Temperature_Celsius =   171     193            0        ok          35
No SMART attributes are FAILING_NOW

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





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

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD80EFZX-68UW8N0
Serial Number:    VKJG57DX
LU WWN Device Id: 5 000cca 254e29fde
Firmware Version: 83.H0A83
User Capacity:    8,001,563,222,016 bytes [8.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, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Jul 24 23:16:02 2016 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:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(  101) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				No 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: 	 (1083) minutes.
SCT capabilities: 	       (0x003d)	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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   129   129   054    Pre-fail  Offline      -       124
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       51
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1
22 Unknown_Attribute       0x0023   100   100   025    Pre-fail  Always       -       100
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       3
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       3
194 Temperature_Celsius     0x0002   171   171   000    Old_age   Always       -       35 (Min/Max 25/38)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       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

Results of the 10TB ironwolf drive:

 

rpt:

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdc
== ST10000VN0004-1ZD101   XXX
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1003520 Bytes
== Last Cycle's Pre Read Time  : 19:51:21 (139 MB/s)
== Last Cycle's Zeroing time   : 15:50:45 (175 MB/s)
== Last Cycle's Post Read Time : 39:39:30 (70 MB/s)
== Last Cycle's Total Time     : 75:22:36
==
== Total Elapsed Time 75:22:36
==
== Disk Start Temperature: 33C
==
== Current Disk Temperature: -->43<--C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =    83     100           44        ok          208480736
          Seek_Error_Rate =    74     100           45        ok          25147894
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    96     100            0        ok          4
  Airflow_Temperature_Cel =    57      67           40        near_thresh 43
      Temperature_Celsius =    43      33            0        ok          43
   Hardware_ECC_Recovered =     9     100            0        near_thresh 208480736
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. 
============================================================================

 

finish:

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

=== START OF INFORMATION SECTION ===
Device Model:     ST10000VN0004-1ZD101
Firmware Version: SC60
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 (unknown minor revision code: 0x006d)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Aug 21 08:27:28 2016 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:  (0x82)	Offline data collection activity
				was completed without error.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(  575) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 884) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x50bd)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   083   064   044    Pre-fail  Always       -       208480736
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   074   060   045    Pre-fail  Always       -       25147894
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       76 (90 57 0)
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   096   096   000    Old_age   Always       -       4
190 Airflow_Temperature_Cel 0x0022   057   056   040    Old_age   Always       -       43 (Min/Max 26/44)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       988
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       6
194 Temperature_Celsius     0x0022   043   044   000    Old_age   Always       -       43 (0 26 0 0 0)
195 Hardware_ECC_Recovered  0x001a   009   008   000    Old_age   Always       -       208480736
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0023   100   100   001    Pre-fail  Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       129063767244875
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       19533649576
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       59746352120

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:

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

=== START OF INFORMATION SECTION ===
Device Model:     ST10000VN0004-1ZD101
Firmware Version: SC60
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 (unknown minor revision code: 0x006d)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Aug 18 05:04:51 2016 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:  (0x82)	Offline data collection activity
				was completed without error.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(  575) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 884) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x50bd)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   044    Pre-fail  Always       -       2138040
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   045    Pre-fail  Always       -       88265
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       1 (61 2 0)
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   067   040    Old_age   Always       -       33 (Min/Max 26/33)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       6
194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 (0 26 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       2138040
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0023   100   100   001    Pre-fail  Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       97654671409152
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       775800
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1362240

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.

 

How does it look? Should I be worried about the "near threshold" values?

Share this post


Link to post

Results of the 10TB ironwolf drive:

...[snipped]...

How does it look? Should I be worried about the "near threshold" values?

No, "near threshold" values are almost always false positives, and the feature should probably have been fixed a long time ago.

 

Apart from 2 numbers, it looks like any other modern Seagate SMART report, for first month usage.  They have discontinued Runtime_Bad_Block, which doesn't surprise me as it was redundant, confusing therefore.

 

One mildly troubling number is Hardware_ECC_Recovered, which has already dropped to 8.  It is encoded into the same number fields as Raw_Read_Error_Rate (same RAW number), but it's not marked as a 'critical attribute' so can't fail the drive.  Raw_Read_Error_Rate *is* a critical one, and looks possibly worrisome, having dropped already to 64 (usually 100 or higher for the first years).  Everything else looks fine.

 

Since this is the first instance we've seen of the drive, it may be too soon to draw any conclusions yet, about your specific drive.

Share this post


Link to post

Thanks for the response. Not really good news though :(

I hope that more people will buy the drive to see if this is normal behavior for the drive or not.

I'm planning to buy two more of those until the end of the year, but they are damn expensive^^

Share this post


Link to post

Hello,

 

I'm hoping someone will help take a look at the preclear results for these three drives to see if there is anything I should be concerned about or keep an eye on.  Only 4 attachments are allowed so I've attached the reports, starts, and finishes together in one zip file "preclearFiles.zip"

 

The 4TB drives seem to have more SMART attributes in the report than the 6TB, even though the 6TB's "finish" file says its SMART support is available and enabled.  Maybe there is something extra I need to do in the BIOS or preclear switches?

 

The 4TB drives are both Seagate but the 6TB drive is a "white label" with just a one year warranty so I'm more concerned about it.

 

Thank you for anyone's input!

 

Without further ado, here are the contents of the reports:

 

ST4000DM000-1F2168  W3002X5W

========================================================================1.15
== invoked as: /boot/preclear_disk.sh -c 3 /dev/sdc
== ST4000DM000-1F2168   W3002X5W
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1 
== Ran 3 cycles
==
== Using :Read block size = 8388608 Bytes
== Last Cycle's Pre Read Time  : 9:51:06 (112 MB/s)
== Last Cycle's Zeroing time   : 8:45:43 (126 MB/s)
== Last Cycle's Post Read Time : 23:15:30 (47 MB/s)
== Last Cycle's Total Time     : 32:02:14
==
== Total Elapsed Time 105:31:57
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   111     119            6        ok          38120536
          Seek_Error_Rate =    64      62           30        ok          2892140
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    90      95            0        ok          10
  Airflow_Temperature_Cel =    70      71           45        near_thresh 30
      Temperature_Celsius =    30      29            0        ok          30
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. 
============================================================================

 

ST4000DM000-1F2168  Z3006399

========================================================================1.15
== invoked as: /boot/preclear_disk.sh -c 3 /dev/sdb
== ST4000DM000-1F2168   Z3006399
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1 
== Ran 3 cycles
==
== Using :Read block size = 8388608 Bytes
== Last Cycle's Pre Read Time  : 9:37:50 (115 MB/s)
== Last Cycle's Zeroing time   : 8:32:32 (130 MB/s)
== Last Cycle's Post Read Time : 22:51:46 (48 MB/s)
== Last Cycle's Total Time     : 31:25:18
==
== Total Elapsed Time 103:29:49
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 30C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   114     111            6        ok          74700168
          Seek_Error_Rate =    63      61           30        ok          2620745
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    93      97            0        ok          7
  Airflow_Temperature_Cel =    70      71           45        near_thresh 30
      Temperature_Celsius =    30      29            0        ok          30
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. 
============================================================================

 

WL6000GSA6454  WOL240346597

========================================================================1.15
== invoked as: /boot/preclear_disk.sh -c 2 /dev/sda
== WL6000GSA6454   WOL240346597
== Disk /dev/sda has been successfully precleared
== with a starting sector of 1 
== Ran 2 cycles
==
== Using :Read block size = 8388608 Bytes
== Last Cycle's Pre Read Time  : 15:43:39 (109 MB/s)
== Last Cycle's Zeroing time   : 13:00:39 (132 MB/s)
== Last Cycle's Post Read Time : 36:20:24 (47 MB/s)
== Last Cycle's Total Time     : 49:22:02
==
== Total Elapsed Time 114:41:28
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
        Unknown_Attribute =     4       0            0        near_thresh 85883701621
      Temperature_Celsius =   123     122            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 2.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 2.
0 sectors were pending re-allocation after post-read in cycle 1 of 2.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 2.
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. 
============================================================================

preclearFiles.zip

Share this post


Link to post

I'm hoping someone will help take a look at the preclear results for these three drives to see if there is anything I should be concerned about or keep an eye on.  Only 4 attachments are allowed so I've attached the reports, starts, and finishes together in one zip file "preclearFiles.zip"

 

The 4TB drives seem to have more SMART attributes in the report than the 6TB, even though the 6TB's "finish" file says its SMART support is available and enabled.  Maybe there is something extra I need to do in the BIOS or preclear switches?

 

The 4TB drives are both Seagate but the 6TB drive is a "white label" with just a one year warranty so I'm more concerned about it.

 

All 3 drives are fine, no issues seen.  The white label drive looks like a WD, same SMART attributes.

Share this post


Link to post

I'm hoping someone will help take a look at the preclear results for these three drives to see if there is anything I should be concerned about or keep an eye on.  Only 4 attachments are allowed so I've attached the reports, starts, and finishes together in one zip file "preclearFiles.zip"

 

The 4TB drives seem to have more SMART attributes in the report than the 6TB, even though the 6TB's "finish" file says its SMART support is available and enabled.  Maybe there is something extra I need to do in the BIOS or preclear switches?

 

The 4TB drives are both Seagate but the 6TB drive is a "white label" with just a one year warranty so I'm more concerned about it.

 

All 3 drives are fine, no issues seen.  The white label drive looks like a WD, same SMART attributes.

 

Thanks very much, RobJ!  I appreciate your time and the good news didn't hurt either :).  Have a good one!

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.