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


Recommended Posts

  • 2 weeks later...

Hi JOE....  ;D

 

Just finished preclearing my 2 harddrives after almost 28 hours.

 

Now there is a message after it was done.... this is for sda  

 

sorry: /dev/sdboota does not exist as a block device clearing will not be performed

 

root@Tower:/boot# B

 

I have to mention that before I did a preclear I did add the 2 harddrives to the array and did the sync that took 5 hours.

 

After that I wanted to do the preclear witch I should of done from the first time.

(I unmounted them first)

So I started from scratch. I reformatted the usb flash drive then started again and did the preclear.

 

 

For SDB has been succcesfully preacleared (so I added sdb to the array and already transferred about 1.5 TB to it, yet I have not added SDA to the array)

 

*Update

 

So I did this code: you can use the "-t" option.  It runs in a few seconds and will let you know if the pre-cleared signature is present.

 

on SDA  the one with the problem and it came back to:

 

DISK /dev/sda IS PRECLEARED with a starting sector of 64

 

Am I good to go? I will wait to add it till you give me the go....

 

* Also SDA the Hitachi has this little click (or swootch) once  in a while at idle (but not spun down).... I don't know if it matters but the WD does not do that (well it does but its way softer).

preclear_results.txt

reports.zip

Link to comment

I'm currently building my first unraid server, using a HP N36L, I've just finished preclearing on two of my drives. Got a couple of SMART-errors and it was also very slow, should I be worried?

 

The F4 2TB is brand new, but is showing some errors: Multi_Zone_Error_Rate =  100    252            0        ok          11 - it was also really slow. Is it because of the overall hardware of the n36l? (AMD Athlon II Neo 1.3GHz - 1GB ram) or something else?

 

The F2 has reported some smart-errors before (UDMA_CRC_Error_Count    0x003e  100  095  000    Old_age  Always      -      64) but since I changed cable in my previous computer I haven't seen it rise.

 

I'm really thankful for your help!

preclear_log.txt

preclear_log_2.txt

Link to comment

Hi JOE....  ;D

 

Just finished preclearing my 2 harddrives after almost 28 hours.

 

Now there is a message after it was done.... this is for sda  

 

sorry: /dev/sdboota does not exist as a block device clearing will not be performed

 

root@Tower:/boot# B

 

I have to mention that before I did a preclear I did add the 2 harddrives to the array and did the sync that took 5 hours.

 

After that I wanted to do the preclear witch I should of done from the first time.

(I unmounted them first)

So I started from scratch. I reformatted the usb flash drive then started again and did the preclear.

 

 

For SDB has been succcesfully preacleared (so I added sdb to the array and already transferred about 1.5 TB to it, yet I have not added SDA to the array)

 

*Update

 

So I did this code: you can use the "-t" option.  It runs in a few seconds and will let you know if the pre-cleared signature is present.

 

on SDA  the one with the problem and it came back to:

 

DISK /dev/sda IS PRECLEARED with a starting sector of 64

 

Am I good to go? I will wait to add it till you give me the go....

 

* Also SDA the Hitachi has this little click (or swootch) once  in a while at idle (but not spun down).... I don't know if it matters but the WD does not do that (well it does but its way softer).

Both disks cleared fine.  SDB has a lot of load cycles, it seems to be parking its heads every few minutes..  That is a firmware option that apparently can be changed on some drives.
Link to comment

Thank you Joe. I will add the parity drive now  ;D

So there is nothing to be concerned when SDA gave me this message instead of the Preclear was successful message right away?

 

sorry: /dev/sdboota does not exist as a block device clearing will not be performed

 

root@Tower:/boot# B

 

and should I worry about SDB has a lot of load cycles? how easy is this so I can change it in the firmware?

 

.................................................

 

Now here is another HD I am going to add to the server later on this is in my main pc at the moment. It's an EADS this one. Should I also worry about the load cycle on this one too? or does it need to be turned off? Had this over 2 years.

 

WOW! I been reading about this...  even speed fan or hd tune if you have it running in the background it will add 1 to the Load cycle time every minute. Witch I do have hd tune running in the background so I can see the temp of the HD.  :-\

 

Now I wonder why I never seen or someone mention that problem about the WD green drives... I would of not bought the EARS.... they always tell me buy the ears

 

 

HD Tune Pro: WDC WD20EADS-00S2B0 Health

 

ID                                  Current  Worst    ThresholdData     Status  

(01) Raw Read Error Rate            200      200      51       0        ok      

(03) Spin Up Time                   156      145      21       9200     ok      

(04) Start/Stop Count               99       99       0        1909     ok      

(05) Reallocated Sector Count       200      200      140      0        ok      

(07) Seek Error Rate                100      253      0        0        ok      

(09) Power On Hours Count           95       95       0        3722     ok      

(0A) Spin Retry Count               100      100      0        0        ok      

(0B) Calibration Retry Count        100      100      0        0        ok      

(0C) Power Cycle Count              100      100      0        818      ok      

(C0) Unsafe Shutdown Count          200      200      0        121      ok      

(C1) Load Cycle Count               182      182      0        56643    ok      

(C2) Temperature                    123      99       0        29       ok      

(C4) Reallocated Event Count        200      200      0        0        ok      

(C5) Current Pending Sector         200      200      0        0        ok      

(C6) Offline Uncorrectable          200      200      0        0        ok      

(C7) Ultra DMA CRC Error Count      200      200      0        0        ok      

(C8) Write Error Rate               200      200      0        0        ok      

 

Health Status         : ok

 

 

 

Link to comment

Thank you Joe. I will add the parity drive now  ;D

So there is nothing to be concerned when SDA gave me this message instead of the Preclear was successful message right away?

 

sorry: /dev/sdboota does not exist as a block device clearing will not be performed

 

root@Tower:/boot# B

It indicates you fat-fingered the command.  /dev/sdboota does not exist.

 

and should I worry about SDB has a lot of load cycles? how easy is this so I can change it in the firmware?

There is a utility that can be run on some hard disks.
Link to comment

This is for the EARS.... I am not sure if it will work with EADS  ???

 

1 Create bootable USB

2 Copy wdidle3.exe to the root directory of the disk

3 Power down server, and replace unraid USB with USB created in #1

4 Disconnect the SATA cables from all the other HDDs in your server except the ones you want to disable the timer on

5 Power up server. Server will boot to MS-DOS prompt.

6 Type WDIDLE3 /R (this will show you the surrent setting which is most likely 8 seconds)

7 Disable the timer by typing WDIDLE3 /S0 (note: the /D command which most guides tell you to use did not disable the timer but instead set it to 5 minutes. I  used the WDIDLE3 /S0 command and that disabled the timer)

8 Verify that the timer has been disabled by using WDIDLE3 /R command again

9 Turn off server

10 Reconnect SATA cables to all HDDs

11 Remove USB drive and replace with unraid USB drive

 

http://www.storagereview.com/how_stop_excessive_load_cycles_western_digital_2tb_caviar_green_wd20ears_wdidle3

 

Thank you wsume99

 

BTW!  I did have to use WDIDLE3 /D and it worked.....    WDIDLE3 /S0 did not work for me it still was 8 seconds....  :P

 

On a second note! it looks also like it works with EADS....  I'll give that a shot later when I transfer the HD over...

 

http://homeservershow.com/forums/index.php?/topic/2015-wdidle3-question/

 

http://www.pcreview.co.uk/forums/arno-did-wd-eads-work-out-t4038383.html

Link to comment
  • 2 weeks later...

Just finished 2 (separate) rounds of preclear on a drive that will replace my parity, and just wanted some eyes more familiar with SMART stats to confirm that these deltas are nothing to be concerned about:

 

1st preclear

** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   116     100            6        ok          102990368
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    60      61           45        near_thresh 40
      Temperature_Celsius =    40      39            0        ok          40
   Hardware_ECC_Recovered =    37     100            0        ok          102990368
No SMART attributes are FAILING_NOW

 

 

2nd preclear

Disk Temperature: 38C, Elapsed Time:  26:23:28
========================================================================1.13
==  ST2000DL003-9VT166    5YD517KW
== 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
      Raw_Read_Error_Rate =   119     116            6        ok          211246080
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    62      64           45        near_thresh 38
      Temperature_Celsius =    38      36            0        ok          38
   Hardware_ECC_Recovered =    37      26            0        ok          211246080
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.

 

The only ones that seem intuitively concerning to me are the Raw_Read_Error_Rate and Hardware_ECC_Recovered changes. Though this page seems to indicate this may be fine.  Thoughts?

Link to comment

Look at the normalized values... they actually improved during the preclear.  (they are further from their failure thresholds, and it looks as if they start at 100 when fresh from the factory, as that is the "old value" for most those that channged)

 

Ignore the raw values... very few are meaningful to end users.  Your drive got better as it broke in during the preclear.

Link to comment

Look at the normalized values... they actually improved during the preclear.   (they are further from their failure thresholds, and it looks as if they start at 100 when fresh from the factory, as that is the "old value" for most those that channged)

 

Ignore the raw values... very few are meaningful to end users.  Your drive got better as it broke in during the preclear.

Thanks, Joe! Helpful as always :)

Link to comment

hello, I recently got one of the 2TB seagate green drives on sale at best buy for a spare.  I don't really understand all of the smart stats.  I ran preclear twice and got these results:

 

1st run:

 

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  116  100  006    Pre-fail  Always      -      113282616

  3 Spin_Up_Time            0x0003  093  093  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      7

  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  100  253  030    Pre-fail  Always      -      199895

  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      30

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      7

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  071  071  045    Old_age  Always      -      29 (Lifetime Min/Max 25/29)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      5

193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      7

194 Temperature_Celsius    0x0022  029  040  000    Old_age  Always      -      29 (0 23 0 0)

195 Hardware_ECC_Recovered  0x001a  037  020  000    Old_age  Always      -      113282616

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      -      142880677036062

241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3866248928

242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      3298977179

 

Run 2:

 

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  100  006    Pre-fail  Always      -      228055680

  3 Spin_Up_Time            0x0003  093  093  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      7

  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  100  253  030    Pre-fail  Always      -      401582

  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      64

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      7

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  073  071  045    Old_age  Always      -      27 (Lifetime Min/Max 25/29)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      5

193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      7

194 Temperature_Celsius    0x0022  027  040  000    Old_age  Always      -      27 (0 23 0 0)

195 Hardware_ECC_Recovered  0x001a  037  020  000    Old_age  Always      -      228055680

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      -      67512590925888

241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3438057546

242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      1505844440

 

 

Is there anything here to worry about??  Thanks for your help as I'm sure there have been 1000 of these posts.

Link to comment

Should I be concerned about this drive. Specifically the Raw_Read_Error_Rate and Seek_Error_Rate parameters. Here are the results after 1 pass:

 

Device Model:    ST2000DL003-9VT166

Serial Number:   

Firmware Version: CC32

User Capacity:    2,000,398,934,016 bytes

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:  8

ATA Standard is:  ATA-8-ACS revision 4

Local Time is:    Sat Nov  5 21:55:21 2011 EDT

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: ( 623) 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: ( 255) minutes.

Conveyance self-test routine

recommended polling time: (  2) minutes.

SCT capabilities:       (0x30b7) SCT Status 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  116  099  006    Pre-fail  Always      -      112825032

  3 Spin_Up_Time            0x0003  091  091  000    Pre-fail  Always      -      0

  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      7

  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  100  253  030    Pre-fail  Always      -      333680

  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      24

10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      7

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  072  071  045    Old_age  Always      -      28 (Lifetime Min/Max 21/29)

191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      6

193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      7

194 Temperature_Celsius    0x0022  028  040  000    Old_age  Always      -      28 (0 21 0 0)

195 Hardware_ECC_Recovered  0x001a  036  030  000    Old_age  Always      -      112825032

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      -      248850405130264

241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3893722297

242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      2157208327

Link to comment

Hi Everyone

 

I just used preclear for the first time . Can some one please look at the syslog file .

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: === START OF READ SMART DATA SECTION ===

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART overall-health self-assessment test result: PASSED

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: General SMART Values:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Offline data collection status:  (0x82)^IOffline data collection activity

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^Iwas completed without error.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^IAuto Offline Data Collection: Enabled.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Self-test execution status:      (  0)^IThe previous self-test routine completed

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^Iwithout error or no self-test has ever

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^Ibeen run.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Total time to complete Offline

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: data collection: ^I^I ( 612) seconds.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Offline data collection

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^IAuto Offline data collection on/off support.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISuspend Offline collection upon new

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^Icommand.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^IOffline surface scan supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISelf-test supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^IConveyance Self-test supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISelective Self-test supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART capabilities:            (0x0003)^ISaves SMART data before entering

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^Ipower-saving mode.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISupports SMART auto save timer.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Error logging capability:        (0x01)^IError logging supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^IGeneral Purpose Logging supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Short self-test routine

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: recommended polling time: ^I (  1) minutes.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Extended self-test routine

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: recommended polling time: ^I ( 255) minutes.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Conveyance self-test routine

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: recommended polling time: ^I (  2) minutes.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SCT capabilities: ^I      (0x30b7)^ISCT Status supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISCT Feature Control supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ^I^I^I^I^ISCT Data Table supported.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART Attributes Data Structure revision number: 10

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Vendor Specific SMART Attributes with Thresholds:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  1 Raw_Read_Error_Rate    0x000f  108  100  006    Pre-fail  Always      -      16012712

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  3 Spin_Up_Time            0x0003  093  093  000    Pre-fail  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  4 Start_Stop_Count        0x0032  100  100  020    Old_age  Always      -      13

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  7 Seek_Error_Rate        0x000f  061  060  030    Pre-fail  Always      -      1565312

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  9 Power_On_Hours          0x0032  100  100  000    Old_age  Always      -      29

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  12 Power_Cycle_Count      0x0032  100  100  020    Old_age  Always      -      13

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 189 High_Fly_Writes        0x003a  099  099  000    Old_age  Always      -      1

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 190 Airflow_Temperature_Cel 0x0022  069  069  045    Old_age  Always      -      31 (Min/Max 29/31)

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 191 G-Sense_Error_Rate      0x0032  100  100  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 192 Power-Off_Retract_Count 0x0032  100  100  000    Old_age  Always      -      8

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 193 Load_Cycle_Count        0x0032  100  100  000    Old_age  Always      -      13

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 194 Temperature_Celsius    0x0022  031  040  000    Old_age  Always      -      31 (0 24 0 0)

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 195 Hardware_ECC_Recovered  0x001a  036  016  000    Old_age  Always      -      16012712

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      110500918591518

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 241 Total_LBAs_Written      0x0000  100  253  000    Old_age  Offline      -      3645151637

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: 242 Total_LBAs_Read        0x0000  100  253  000    Old_age  Offline      -      3315528952

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART Error Log Version: 1

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: No Errors Logged

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART Self-test log structure revision number 1

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART Selective self-test log data structure revision number 1

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:    1        0        0  Not_testing

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:    2        0        0  Not_testing

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:    3        0        0  Not_testing

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:    4        0        0  Not_testing

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:    5        0        0  Not_testing

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: Selective self-test flags (0x0):

Nov 16 09:54:10 Tower preclear_disk-diff[29415]:  After scanning selected spans, do NOT read-scan remainder of disk.

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: If Selective self-test is pending on power-up, resume after 0 minute delay.

 

Link to comment

I just precleared my hard drive through putty with screen.  This is what it says:

 

 

== 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 =   114     100            6        ok          70588808
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    58      64           45        near_thresh 42
      Temperature_Celsius =    42      36            0        ok          42
   Hardware_ECC_Recovered =    36     100            0        ok          70588808
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.

 

is this enough information to know if the drive is fine or do you require more?

 

thanks in advance.

Link to comment

Hi Everyone

 

I just used preclear for the first time . Can some one please look at the syslog file .

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: === START OF READ SMART DATA SECTION ===

Nov 16 09:54:10 Tower preclear_disk-diff[29415]: SMART overall-health self-assessment test result: PASSED

What you posted is the second smart report loogged by the preclear process. 

It does not indicate if the process was successful or not.    It is NOT the output of the preclear process, nor is it a full syslog.  It shows a perfectly healthy drive

 

For this thread, we would like the preclear output, not the syslog.  In fact, it is not necessary to look at the syslog at all in most cases.

 

You can find the preclear report in a "preclear_reports" directory on your flash drive.  It will be named "preclear_rpt_(drive)_YYYY-MM-DD"

 

Link to comment

I found the full preclear results thanks to the above post by Joe L.  Is everything fine?

 

Disk: /dev/sdg
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST2000DL003-9VT166
Serial Number:    5YD69HTY
Firmware Version: CC32
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Tue Nov 15 21:57:12 2011 PST
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: 		 ( 612) 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: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x30b7)	SCT Status 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   114   100   006    Pre-fail  Always       -       70588808
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       7
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       193273872698
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       25
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       7
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   058   057   045    Old_age   Always       -       42 (Lifetime Min/Max 26/43)
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       -       6
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   042   043   000    Old_age   Always       -       42 (0 26 0 0)
195 Hardware_ECC_Recovered  0x001a   036   025   000    Old_age   Always       -       70588808
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      -       178631984807961
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3889415671
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3479408396

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Link to comment

I found the full preclear results thanks to the above post by Joe L.  Is everything fine?

Looking at what you provided I cannot tell if that is the pre or post SMART report. However the fact that your disk reports 25 power on hours leads me to believe that it is the post-read assessment. If the info you posted is in fact the SMART report from the post-read then your disk is good (no reallocated or pending sectors).

Link to comment

Ok, so I got a 3TB and started a preclear run. After an hour or so I checked in on it, seeing this:

 

================================================================== 1.12
=                unRAID server Pre-Clear disk /dev/sda
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Read in progress: 0% complete
= ( 27,965,952,000  bytes of  3,000,592,982,016  read ) 1.3 MB/s
=
=
=
=
=
=
=
=
=
=
Disk Temperature: 43C, Elapsed Time:  1:01:02

 

Doesn't look too good. It's running hot, but most of all at snails pace. Well, a look in the syslog shows something is rotten in the state of Denmark:

Nov 16 21:47:29 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:29 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:29 Tower kernel: ata4.00: cmd c8/00:08:d8:41:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:29 Tower kernel:          res 51/40:08:d8:41:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:29 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:29 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:29 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:29 Tower kernel: ata4: EH complete                                                                                                   
Nov 16 21:47:31 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0                                                           
Nov 16 21:47:31 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:31 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:31 Tower kernel: ata4.00: cmd c8/00:08:d8:41:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:31 Tower kernel:          res 51/40:08:d8:41:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:31 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:31 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:31 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda] Unhandled sense code                                                                              
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x08                                                            
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  Sense Key : 0x3 [current] [descriptor]                                                           
Nov 16 21:47:31 Tower kernel: Descriptor sense data with sense descriptors (in hex):                                                              
Nov 16 21:47:31 Tower kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00                                                             
Nov 16 21:47:31 Tower kernel:         03 65 41 d8                                                                                                 
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  ASC=0x11 ASCQ=0x4                                                                                
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 03 65 41 d8 00 00 08 00                                                   
Nov 16 21:47:31 Tower kernel: end_request: I/O error, dev sda, sector 56967640                                                                    
Nov 16 21:47:31 Tower kernel: Buffer I/O error on device sda, logical block 7120955                                                               
Nov 16 21:47:31 Tower kernel: ata4: EH complete                                                                                                   
Nov 16 21:47:34 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0                                                           
Nov 16 21:47:34 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:34 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:34 Tower kernel: ata4.00: cmd c8/00:08:28:7d:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:34 Tower kernel:          res 51/40:08:28:7d:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:34 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:34 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:34 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:34 Tower kernel: ata4: EH complete                           

And this just repeats over and over. Setup is an ESATA cradle on a marvell onboard chip. I haven't noticed any particular performance problems with it before, but will now relocate it (temp prob) and check the cabling. Is it possible to see any reason from the logs above, or other logs, or should I just trial and error to find a working setup (or broken disk). All of my internal SATA is busy with the array, so I cannot try it there.

 

/Lars Olof

Link to comment

Ok, so I got a 3TB and started a preclear run. After an hour or so I checked in on it, seeing this:

 

================================================================== 1.12
=                unRAID server Pre-Clear disk /dev/sda
=               cycle 1 of 1, partition start on sector 1
= Disk Pre-Read in progress: 0% complete
= ( 27,965,952,000  bytes of  3,000,592,982,016  read ) 1.3 MB/s
=
=
=
=
=
=
=
=
=
=
Disk Temperature: 43C, Elapsed Time:  1:01:02

 

Doesn't look too good. It's running hot, but most of all at snails pace. Well, a look in the syslog shows something is rotten in the state of Denmark:

Nov 16 21:47:29 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:29 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:29 Tower kernel: ata4.00: cmd c8/00:08:d8:41:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:29 Tower kernel:          res 51/40:08:d8:41:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:29 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:29 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:29 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:29 Tower kernel: ata4: EH complete                                                                                                   
Nov 16 21:47:31 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0                                                           
Nov 16 21:47:31 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:31 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:31 Tower kernel: ata4.00: cmd c8/00:08:d8:41:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:31 Tower kernel:          res 51/40:08:d8:41:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:31 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:31 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:31 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda] Unhandled sense code                                                                              
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x08                                                            
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  Sense Key : 0x3 [current] [descriptor]                                                           
Nov 16 21:47:31 Tower kernel: Descriptor sense data with sense descriptors (in hex):                                                              
Nov 16 21:47:31 Tower kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00                                                             
Nov 16 21:47:31 Tower kernel:         03 65 41 d8                                                                                                 
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda]  ASC=0x11 ASCQ=0x4                                                                                
Nov 16 21:47:31 Tower kernel: sd 5:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 03 65 41 d8 00 00 08 00                                                   
Nov 16 21:47:31 Tower kernel: end_request: I/O error, dev sda, sector 56967640                                                                    
Nov 16 21:47:31 Tower kernel: Buffer I/O error on device sda, logical block 7120955                                                               
Nov 16 21:47:31 Tower kernel: ata4: EH complete                                                                                                   
Nov 16 21:47:34 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0                                                           
Nov 16 21:47:34 Tower kernel: ata4.00: BMDMA stat 0x64                                                                                            
Nov 16 21:47:34 Tower kernel: ata4.00: failed command: READ DMA                                                                                   
Nov 16 21:47:34 Tower kernel: ata4.00: cmd c8/00:08:28:7d:65/00:00:00:00:00/e3 tag 0 dma 4096 in                                                  
Nov 16 21:47:34 Tower kernel:          res 51/40:08:28:7d:65/00:00:00:00:00/e3 Emask 0x9 (media error)                                            
Nov 16 21:47:34 Tower kernel: ata4.00: status: { DRDY ERR }                                                                                       
Nov 16 21:47:34 Tower kernel: ata4.00: error: { UNC }                                                                                             
Nov 16 21:47:34 Tower kernel: ata4.00: configured for UDMA/133                                                                                    
Nov 16 21:47:34 Tower kernel: ata4: EH complete                           

And this just repeats over and over. Setup is an ESATA cradle on a marvell onboard chip. I haven't noticed any particular performance problems with it before, but will now relocate it (temp prob) and check the cabling. Is it possible to see any reason from the logs above, or other logs, or should I just trial and error to find a working setup (or broken disk). All of my internal SATA is busy with the array, so I cannot try it there.

 

/Lars Olof

Media errors are unreadable sectors.  You should see a bunch of them pending re-allocation/re-allocated if you get a smart report now.

 

Joe L..

Link to comment

Current SMART status from Unmenu:

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   193   191   051    Pre-fail  Always       -       24
  3 Spin_Up_Time            0x0027   202   178   021    Pre-fail  Always       -       6900
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       11
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       10
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       -       8
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       19
194 Temperature_Celsius     0x0022   113   108   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       3
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

Status of disk is started once in ESATA cradle, started running Preclear, aborted it, spin down once and left in cradle overnight. Makes me curious about

"12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      8"

 

/Lars Olof

Link to comment

Current SMART status from Unmenu:

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   193   191   051    Pre-fail  Always       -       24
  3 Spin_Up_Time            0x0027   202   178   021    Pre-fail  Always       -       6900
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       11
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       10
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       -       8
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       19
194 Temperature_Celsius     0x0022   113   108   000    Old_age   Always       -       39
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       3
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

Status of disk is started once in ESATA cradle, started running Preclear, aborted it, spin down once and left in cradle overnight. Makes me curious about

"12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       8"

 

/Lars Olof

It says the disk had been power cycled 8 times since it was manufactured. 

I'd be more concerned about the 7 times the disk heads retracted because power was suddenly lost.

 

192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      7

 

Check your power connections.

Link to comment

It says the disk had been power cycled 8 times since it was manufactured.  

I'd be more concerned about the 7 times the disk heads retracted because power was suddenly lost.

 

192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7

 

Check your power connections.

 

I have tried again to run Preclear on this disk. Since I run it in a external cradle (similar to this: http://www.storagedepot.co.uk/External-Hard-Drives/Hard-Drive-Docks/sc883/p753popup1532.aspx) I cannot do much to the connectors. I relocated the cradle, reseated the disk and checked the cabling. But still the run is crawling to a halt. 2% overnight :-( I'll see if I can find a free internal sata connector to run it there. For now I give you logs from this run. What I would like to know is if the lack of performance might be a result of bad power, or if the interface or even the disk is giving up.

 

First just the SMART snippets, first report:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE                                                  
 1 Raw_Read_Error_Rate     0x002f   193   191   051    Pre-fail  Always       -       24                                                         
 3 Spin_Up_Time            0x0027   196   178   021    Pre-fail  Always       -       7166                                                       
 4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       12                                                         
 5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       1                                                          
 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       -       9                                                          
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7                                                          
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       27                                                         
194 Temperature_Celsius     0x0022   112   108   000    Old_age   Always       -       40                                                         
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0                                                          
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       3                                                          
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

 

Then rerun after breaking after a few hours:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE                                                  
 1 Raw_Read_Error_Rate     0x002f   194   191   051    Pre-fail  Always       -       48                                                         
 3 Spin_Up_Time            0x0027   196   178   021    Pre-fail  Always       -       7166                                                       
 4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       12                                                         
 5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       2                                                          
 7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0                                                          
 9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       35                                                         
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       -       9                                                          
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7                                                          
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       29                                                         
194 Temperature_Celsius     0x0022   108   108   000    Old_age   Always       -       44                                                         
196 Reallocated_Event_Count 0x0032   199   199   000    Old_age   Always       -       1                                                          
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       3                                                          
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

 

I would also attach my syslogs (it looks to have split tonight), the dmesg and the two full preclear start logs, but the zip gets too big. Hope it will work from here: http://www.larsolof.se/files/syslogs.zip

 

My power issue looks fixed, since the value hasn't increased on this run. Something else is no good.

 

/Lars Olof

Link to comment

Your syslog is filled with these "media errors" (unreadable sectors)

The speed is slowed way down since unRAID is resetting the disk and trying again and again on each failure.

ov 18 08:05:56 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 18 08:05:56 Tower kernel: ata8.00: BMDMA stat 0x64

Nov 18 08:05:56 Tower kernel: ata8.00: failed command: READ DMA

Nov 18 08:05:56 Tower kernel: ata8.00: cmd c8/00:08:b8:b8:dd/00:00:00:00:00/e7 tag 0 dma 4096 in

Nov 18 08:05:56 Tower kernel:          res 51/40:08:b8:b8:dd/40:00:07:00:00/e7 Emask 0x9 (media error)

Nov 18 08:05:56 Tower kernel: ata8.00: status: { DRDY ERR }

Nov 18 08:05:56 Tower kernel: ata8.00: error: { UNC }

Nov 18 08:05:56 Tower kernel: ata8.00: configured for UDMA/33

Nov 18 08:05:56 Tower kernel: ata8: EH complete

Nov 18 08:05:59 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 18 08:05:59 Tower kernel: ata8.00: BMDMA stat 0x64

Nov 18 08:05:59 Tower kernel: ata8.00: failed command: READ DMA

Nov 18 08:05:59 Tower kernel: ata8.00: cmd c8/00:08:b8:b8:dd/00:00:00:00:00/e7 tag 0 dma 4096 in

Nov 18 08:05:59 Tower kernel:          res 51/40:08:b8:b8:dd/40:00:07:00:00/e7 Emask 0x9 (media error)

Nov 18 08:05:59 Tower kernel: ata8.00: status: { DRDY ERR }

Nov 18 08:05:59 Tower kernel: ata8.00: error: { UNC }

Nov 18 08:05:59 Tower kernel: ata8.00: configured for UDMA/33

Nov 18 08:05:59 Tower kernel: ata8: EH complete

Nov 18 08:06:01 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 18 08:06:01 Tower kernel: ata8.00: BMDMA stat 0x64

Nov 18 08:06:01 Tower kernel: ata8.00: failed command: READ DMA

Nov 18 08:06:01 Tower kernel: ata8.00: cmd c8/00:08:b8:b8:dd/00:00:00:00:00/e7 tag 0 dma 4096 in

Nov 18 08:06:01 Tower kernel:          res 51/40:08:b8:b8:dd/40:00:07:00:00/e7 Emask 0x9 (media error)

Nov 18 08:06:01 Tower kernel: ata8.00: status: { DRDY ERR }

Nov 18 08:06:01 Tower kernel: ata8.00: error: { UNC }

Nov 18 08:06:01 Tower kernel: ata8.00: configured for UDMA/33

Nov 18 08:06:01 Tower kernel: sd 5:0:0:0: [sdj] Unhandled sense code

Nov 18 08:06:01 Tower kernel: sd 5:0:0:0: [sdj]  Result: hostbyte=0x00 driverbyte=0x08

Nov 18 08:06:01 Tower kernel: sd 5:0:0:0: [sdj]  Sense Key : 0x3 [current] [descriptor]

Nov 18 08:06:01 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 18 08:06:01 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 18 08:06:01 Tower kernel:        07 dd b8 b8

Nov 18 08:06:01 Tower kernel: sd 5:0:0:0: [sdj]  ASC=0x11 ASCQ=0x4

Nov 18 08:06:01 Tower kernel: sd 5:0:0:0: [sdj] CDB: cdb[0]=0x28: 28 00 07 dd b8 b8 00 00 08 00

Nov 18 08:06:01 Tower kernel: end_request: I/O error, dev sdj, sector 131971256

Nov 18 08:06:01 Tower kernel: Buffer I/O error on device sdj, logical block 16496407

Nov 18 08:06:01 Tower kernel: ata8: EH complete

Nov 18 08:06:04 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 18 08:06:04 Tower kernel: ata8.00: BMDMA stat 0x64

Nov 18 08:06:04 Tower kernel: ata8.00: failed command: READ DMA

Nov 18 08:06:04 Tower kernel: ata8.00: cmd c8/00:08:c0:f5:dd/00:00:00:00:00/e7 tag 0 dma 4096 in

Nov 18 08:06:04 Tower kernel:          res 51/40:08:c0:f5:dd/40:00:07:00:00/e7 Emask 0x9 (media error)

Link to comment

Join the conversation

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

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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