Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

I am about to pre-clear my new 4TB HGST for my parity. All of my  2TB drives have been pre-cleared with 4k-aligned.  Should I do 4k-aligned with my new 4TB drive?  :) Thank you.

Alignment has no effect on drives > 2.2TB.

Share this post


Link to post

I am about to pre-clear my new 4TB HGST for my parity. All of my  2TB drives have been pre-cleared with 4k-aligned.  Should I do 4k-aligned with my new 4TB drive?  :) Thank you.

Alignment has no effect on drives > 2.2TB.

 

Thank you for the fast response. So ok I will not do the 4k and it will start on sector 63.

 

Should I change the default partition format from 4k to unaligned?

 

settings.JPG.8fbded7cd58daf8ba010b3d053c6ae47.JPG

Share this post


Link to post

Cool its done....can someone tell me it its ok for me to add it to the array?

 

Thank you.

 

:D

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.

Perfect score

Share this post


Link to post

Everything looks fine to me after 1 preclear, going to run one more to verify.  Can you just confirm its OK

 

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

=                unRAID server Pre-Clear disk /dev/sdf

=              cycle 1 of 1, partition start on sector 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 32C, Elapsed Time:  42:40:56

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

== HGSTHDN724040ALE640  PK1334PCJTM1JS

== Disk /dev/sdf has been successfully precleared

== with a starting sector of 1

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

** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Temperature_Celsius =  187    181            0        ok          32

No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.

0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

0 sectors are pending re-allocation at the end of the preclear,

    the number of sectors pending re-allocation did not change.

0 sectors had been re-allocated before the start of the preclear.

0 sectors are re-allocated at the end of the preclear,

    the number of sectors re-allocated did not change.

root@Tower:/usr/local/emhttp#

Share this post


Link to post

Everything looks fine to me after 1 preclear, going to run one more to verify.  Can you just confirm its OK

 

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

=                unRAID server Pre-Clear disk /dev/sdf

=              cycle 1 of 1, partition start on sector 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 32C, Elapsed Time:  42:40:56

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

== HGSTHDN724040ALE640  PK1334PCJTM1JS

== Disk /dev/sdf has been successfully precleared

== with a starting sector of 1

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

** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Temperature_Celsius =  187    181            0        ok          32

No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.

0 sectors were pending re-allocation after pre-read in cycle 1 of 1.

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.

0 sectors are pending re-allocation at the end of the preclear,

    the number of sectors pending re-allocation did not change.

0 sectors had been re-allocated before the start of the preclear.

0 sectors are re-allocated at the end of the preclear,

    the number of sectors re-allocated did not change.

root@Tower:/usr/local/emhttp#

 

squirrellydw, there have been a number of users that have posted a perfect result then asked if it's OK, and I'm never sure how to answer.  There's only success messages above, nothing at all wrong, but perhaps there's too much technical info, and it's creating confusion or ambiguity?  Can you tell me what caused doubt in your mind?  What would you prefer it to say that would be clearer?

 

I think we should probably push more users to use the plugin, which I believe completes with a clear and unambiguous result.

Share this post


Link to post

This is from the plugin, I was pretty sure it was perfect but I haven't had to run one in about a year and just wanted to make sure.  Also I should start it on sector 1 correct?

 

As for suggestions I guess it would be nice if it came back perfect that it would say perfect and nothing to worry about.  Just like to know I didn't miss anything.

Share this post


Link to post

I'm very new to unRaid and have just finished preclearing (using the preclear plug-in) 3 6tb WD reds. 2 came back perfect but the third came back with some Seek Error Read info which I dont understand. Should I be concerned? I have express RMA for another 2 weeks on this drive so exchanging it shouldnt be a problem as long as this problem warrants an exchange, could this just be bad cable? maybe I can re do the test using a different cable, 56 hours to preclear though...... I appreciate any help I get, Thanks.

 

Also, am I finished with the preclear process or is there another step I should do before creating the array and starting a parity sync?

 

THANKS!

 

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

=                unRAID server Pre-Clear disk /dev/sdb

=              cycle 1 of 1, partition start on sector 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Verifying if the MBR is cleared.              DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 23C, Elapsed Time:  55:21:39

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

== WDCWD60EFRX

== Disk /dev/sdb has been successfully precleared

== with a starting sector of 1

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

** 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 =  129    126            0        ok          23

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

I've got my very first running through preclear right now.

 

I have two 4TB drives at the same time.

 

Now to the questions.

 

1) The pre-read finished, but I was not logged in when it happened.  Is there a way to see the results?

2) I thought I bought a pretty beefy CPU for Unraid (I3-4170) but during the zero writing the usage is consistantly between 60-80%.  Is that high cpu usage normal?  Is there a way to see if you cpu is functioning correctly in unraid (all cores used ect ect)?

 

Thanks.

Share this post


Link to post

Thanks for any comments on what look like high numbers to me for the Raw_Read_Error_Rate, Seek_Error_Rate and Hardware_ECC_Recovered compared to other drives I have including a recent WD 6TB Red.

 

I know Reallocated_Sector_Ct and Current_Pending_Sector are key values to check and those look ok.

 

This is one of the newer Seagate 8TB drives cleared using the Unofficial Faster Preclear

 

I want to use this drive as part of a parity swap procedure including a failed drive.  Just to be clear I'm familiar with that procedure.

 

Thanks for any comments!

 

======

 

The start report:

 

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

=== START OF INFORMATION SECTION ===
Device Model:     ST8000AS0002-1NA17Z
Serial Number:    Z8409FV4
LU WWN Device Id: 5 000c50 0872476dc
Firmware Version: AR15
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Jan 11 18:36:49 2016 EST
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: 		(    0) 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: 	 ( 962) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x30a5)	SCT Status 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   006    Pre-fail  Always       -       7104
  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   030    Pre-fail  Always       -       98
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       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
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   076   076   045    Old_age   Always       -       24 (Min/Max 20/24)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       2
194 Temperature_Celsius     0x0022   024   040   000    Old_age   Always       -       24 (0 20 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       7104
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       146810572111872
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       0
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       488

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.

 

The Finish report:

 

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

=== START OF INFORMATION SECTION ===
Device Model:     ST8000AS0002-1NA17Z
Serial Number:    Z8409FV4
LU WWN Device Id: 5 000c50 0872476dc
Firmware Version: AR15
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jan 13 23:13:00 2016 EST
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: 		(    0) 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: 	 ( 962) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x30a5)	SCT Status 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   119   099   006    Pre-fail  Always       -       204562656
  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   072   060   030    Pre-fail  Always       -       16240967
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       52
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   063   000    Old_age   Always       -       1503
189 High_Fly_Writes         0x003a   081   081   000    Old_age   Always       -       19
190 Airflow_Temperature_Cel 0x0022   072   070   045    Old_age   Always       -       28 (Min/Max 20/30)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       4
194 Temperature_Celsius     0x0022   028   040   000    Old_age   Always       -       28 (0 20 0 0 0)
195 Hardware_ECC_Recovered  0x001a   119   099   000    Old_age   Always       -       204562656
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       24678882082868
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       15628118912
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       32051898463

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.

 

The RPT report:

 

========================================================================1.15b
== invoked as: ./preclear_bjp.sh -f -A /dev/sdj
== ST8000AS0002-1NA17Z   Z8409FV4
== Disk /dev/sdj has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 8388608 Bytes
== Last Cycle's Pre Read Time  : 17:28:23 (127 MB/s)
== Last Cycle's Zeroing time   : 15:28:54 (143 MB/s)
== Last Cycle's Post Read Time : 19:37:49 (113 MB/s)
== Last Cycle's Total Time     : 52:36:12
==
== Total Elapsed Time 52:36:12
==
== Disk Start Temperature: 24C
==
== Current Disk Temperature: 28C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdj  /tmp/smart_finish_sdj
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   119     100            6        ok          204562656
          Seek_Error_Rate =    72     100           30        ok          16240967
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    81     100            0        ok          19
  Airflow_Temperature_Cel =    72      76           45        ok          28
      Temperature_Celsius =    28      24            0        ok          28
   Hardware_ECC_Recovered =   119     100            0        ok          204562656
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

The pre-read finished, but I was not logged in when it happened.  Is there a way to see the results?

Looking at your post history I assume you were using the plugin. You should be able to see the results by clicking on the "eye" next to the disk. The results are also saved to your flash.

Share this post


Link to post

Yes I am using the webgui.  I just assumed there would be a results of the pre-read portion of the preclear.

 

It is now on writing zeros, and I can click the eye to see that status, but nothing about the pre-read.  Guess we will wait to see what happens when it finishes up.

 

I'm also curious about the High CPU usage.

Share this post


Link to post

Just wanted to make sure these results are okay.

Nothing popped out at me so I'm hoping everything is good.  I did 2 cycles using the plugin.

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdf
=               cycle 2 of 2, partition start on sector 64
=
= 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: 38C, Elapsed Time:  26:58:16
========================================================================1.15
== ST2000DM001-1ER164   Z4Z3MYP1
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 64
============================================================================
** 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 =   119     100            6        ok          208315656
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    99     100            0        ok          1
  Airflow_Temperature_Cel =    62      65           45        near_thresh 38
      Temperature_Celsius =    38      35            0        ok          38
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.
root@Tower:/usr/local/emhttp#

Share this post


Link to post

Just wanted to make sure these results are okay.

Nothing popped out at me so I'm hoping everything is good.  I did 2 cycles using the plugin.

Yours looks essentially perfect too, and with a Raw_Read_Error_Rate of 119, you could say it's better than perfect!

Share this post


Link to post

Thanks for any comments on what look like high numbers to me for the Raw_Read_Error_Rate, Seek_Error_Rate and Hardware_ECC_Recovered compared to other drives I have including a recent WD 6TB Red.

 

I know Reallocated_Sector_Ct and Current_Pending_Sector are key values to check and those look ok.

 

This is one of the newer Seagate 8TB drives cleared using the Unofficial Faster Preclear

 

I want to use this drive as part of a parity swap procedure including a failed drive.  Just to be clear I'm familiar with that procedure.

 

Thanks for any comments!

Drive looks fine.

 

With 180 pages in this thread, you can be excused for not reading it all!  We've often commented about the error rates, and their ridiculous numbers on Seagates (unlike other brands which don't use the RAW here), but haven't mentioned it in awhile, so might as well again.  The Raw_Read_Error_Rate and Seek_Error_Rate are just error rates, not counters, and their RAW values are actually coded fields, but displayed (wrongly) as a decimal number.  If you were to examine that number in hex across multiple SMART reports, you would be able to see parts of the hex string changing, but much of it not changing.  Displaying it as a decimal is always misleading.  More importantly, its construction is only of use to the manufacturer, not to us, so it should always be ignored.  What is important with error rates is how the VALUE and WORST are behaving, whether they are dropping, getting close to the THRESHOLD.  Because they are based on rates, not counters, they jump around some, and can go up and down.  Usually, 100 (or sometimes 200) is set to correspond to an optimal rate of read or seek errors, but at times the rate may be even better, producing numbers like the 119 you currently have.  There are exceptions in how they are handled though.  For example, Seagate optimal seek error rates are typically in the 60's, not near 100.

 

Hardware_ECC_Recovered is just a copy of Raw_Read_Error_Rate, ignore it.

 

The 2 that ARE a bit unusual (but only minor items to monitor over time), are High_Fly_Writes and Command_Timeout, particularly because it's a brand new drive.  High_Fly_Writes is 19 already, can sometimes indicate mechanical issues in the future.  Just monitor it.  The scaling function for the VALUE is a dummy routine, ignore what happens to it.  Command_Timeout is 1503, somewhat unusual, but probably not a problem, especially since VALUE hasn't budged from 100.  My research found two rather different (and both confusing) descriptions for it, and nothing yet that is conclusive about it.  As usual(!), different vendors are using it quite differently.  I personally have seen no correlation with any other issue at all.

Share this post


Link to post

Drive looks fine.

 

Thanks Rob for the fast reply and great info, greatly appreciated.  I will definitely take note of this for future use of Seagate drives with preclear/smartctl.

Share this post


Link to post

I started a pre-clear of 3 drives the other day. 2x2TB and 1x160gb. A 2tb and the 160gb drive cleared no problems. But it seems the other 2tb has frozen at 66%.

 

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

=                unRAID server Pre-Clear disk /dev/sde

=              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

= Post-Read in progress: 66% complete.

(  1,329,595,392,000  of  2,000,398,934,016  bytes read ) 63.9 MB/s

Disk Temperature: 42C, Elapsed Time:  46:03:23

 

The number of bytes read has not changed in the last half hour.

 

Question. Since its at Post Read, can i just run Post Read again or do i need to start from the beginning?

I'm using Joe's script and the plugin if that matters

 

Thanks

Share this post


Link to post

I started a pre-clear of 3 drives the other day. 2x2TB and 1x160gb. A 2tb and the 160gb drive cleared no problems. But it seems the other 2tb has frozen at 66%.

 

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

=                unRAID server Pre-Clear disk /dev/sde

=              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

= Post-Read in progress: 66% complete.

(  1,329,595,392,000  of  2,000,398,934,016  bytes read ) 63.9 MB/s

Disk Temperature: 42C, Elapsed Time:  46:03:23

 

The number of bytes read has not changed in the last half hour.

 

Question. Since its at Post Read, can i just run Post Read again or do i need to start from the beginning?

I'm using Joe's script and the plugin if that matters

 

Thanks

In theory you can start again with the post-read, but that leaves open the question of why it failed in the first place!  Things to do before trying again would be:
  • Run the tools->Diagnostics option in case it has any information relating to why the preclear failed.  You could post the ZIP file here if you want anyone else to look at it.
  • See if you can obtain a SMART report for the drive (there should be a copy in the diagnostics file but doing it for just this drive will see if it may have dropped offline.  Also the SMART report might indicate if the drive is having problems.
  • Look in the preclear reports to see if there is anything useful about the earlier stages.
  • Check cabling to the drive

Share this post


Link to post

I started a pre-clear of 3 drives the other day. 2x2TB and 1x160gb. A 2tb and the 160gb drive cleared no problems. But it seems the other 2tb has frozen at 66%.

 

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

=                unRAID server Pre-Clear disk /dev/sde

=              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

= Post-Read in progress: 66% complete.

(  1,329,595,392,000  of  2,000,398,934,016  bytes read ) 63.9 MB/s

Disk Temperature: 42C, Elapsed Time:  46:03:23

 

The number of bytes read has not changed in the last half hour.

 

Question. Since its at Post Read, can i just run Post Read again or do i need to start from the beginning?

I'm using Joe's script and the plugin if that matters

 

Thanks

In theory you can start again with the post-read, but that leaves open the question of why it failed in the first place!  Things to do before trying again would be:
  • Run the tools->Diagnostics option in case it has any information relating to why the preclear failed.  You could post the ZIP file here if you want anyone else to look at it.
  • See if you can obtain a SMART report for the drive (there should be a copy in the diagnostics file but doing it for just this drive will see if it may have dropped offline.  Also the SMART report might indicate if the drive is having problems.
  • Look in the preclear reports to see if there is anything useful about the earlier stages.
  • Check cabling to the drive

 

Thanks itimpi. Ive noticed the sector count has changed, but ever so slightly and at an extremely slow rate.

 

Ive also attached my smart report.

 

Thanks

tower-smart-20160120-2219.zip

Share this post


Link to post

Ive noticed the sector count has changed, but ever so slightly and at an extremely slow rate.

 

Ive also attached my smart report.

I think that drive has problems.  The Pending Sector count needs to be 0 for the drive to be used successfully with unRAID and that SMART report for the drive shows 1453 (it has probably gone up since).    That is probably why the count shown is incrementing so slowly - the drive is continually retrying to read sectors, and eventually giving up and marking them as 'pending' to indicate a read failure.  I bet if you looked at the syslog it will be filled with read errors for that drive.

Share this post


Link to post

Ive noticed the sector count has changed, but ever so slightly and at an extremely slow rate.

 

Ive also attached my smart report.

I think that drive has problems.  The Pending Sector count needs to be 0 for the drive to be used successfully with unRAID and that SMART report for the drive shows 1453 (it has probably gone up since).    That is probably why the count shown is incrementing so slowly - the drive is continually retrying to read sectors, and eventually giving up and marking them as 'pending' to indicate a read failure.  I bet if you looked at the syslog it will be filled with read errors for that drive.

 

This is exactly why we preclear! Far better to have this happen before you load data!

Share this post


Link to post

Ive noticed the sector count has changed, but ever so slightly and at an extremely slow rate.

 

Ive also attached my smart report.

I think that drive has problems.  The Pending Sector count needs to be 0 for the drive to be used successfully with unRAID and that SMART report for the drive shows 1453 (it has probably gone up since).    That is probably why the count shown is incrementing so slowly - the drive is continually retrying to read sectors, and eventually giving up and marking them as 'pending' to indicate a read failure.  I bet if you looked at the syslog it will be filled with read errors for that drive.

 

Thanks itimpi - Now you've mentioned syslogs, i do remeber seeing errors, but dont recall if they were for the drive...Should have realised with a preclear in process..

 

I agree bjp999 - Rather it happen now than later for sure.

 

Im assuming that there is no point in restarting it? Just wait till it finally finishes and see the report?

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.