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


Recommended Posts

Agree ... low-to-mid 40's isn't an issue at all for pre-clear temps.    That's as high as they'll ever get ... and with a fairly high ambient (33) it's completely understandable.    Modern drives are rated for up to 60, so you're nowhere close to "dangerous" levels.  I agree that for normal operations it's nice to have enough airflow to keep the temps in the 30's.

 

Link to comment

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

=                unRAID server Pre-Clear disk /dev/sdi

=              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

=

Elapsed Time:  8:15:51

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

==

== SORRY: Disk /dev/sdi MBR could NOT be precleared

==

== out4= 00000

== out5= 00000

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

0+0 records in

0+0 records out

0 bytes (0 B) copied, 0.000130407 s, 0.0 kB/s

0000000

 

 

 

I bought 3 Seagate N000, preclear -A all of them gave the same results. I'm using Unraid 6 beta 14.

 

But I can format and put them in my array without any problem.. Should I be worry?

 

 

edited : its 3TB Seagate NAS

Link to comment

 

== SORRY: Disk /dev/sdi MBR could NOT be precleared

==

== out4= 00000

== out5= 00000

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

0+0 records in

0+0 records out

0 bytes (0 B) copied, 0.000130407 s, 0.0 kB/s

0000000

 

 

the fact it says it couldn't preclear the drives, is odd. i think it would be best for you to post the logs created

Link to comment

Actually, it said "0 bytes copied" so it could not read the disk when it was trying to.

Might be fine in operation, but I expect you might want to keep an eye on it.

Can you get a smart report on the drive right now?

(does it respond at all to read requests?)

 

What do you see when you run this command that attempts to read the disk's first 195 sectors:

(it will print, at most, 30 lines of text)

dd if=/dev/sdi count=195 | od -c -A d |  sed  30q

 

 

Link to comment

Actually, it said "0 bytes copied" so it could not read the disk when it was trying to.

Might be fine in operation, but I expect you might want to keep an eye on it.

Can you get a smart report on the drive right now?

(does it respond at all to read requests?)

 

What do you see when you run this command that attempts to read the disk's first 195 sectors:

(it will print, at most, 30 lines of text)

dd if=/dev/sdi count=195 | od -c -A d |  sed  30q

 

root@Silencio:/boot/config# dd if=/dev/sdi count=195 | od -c -A d |  sed  30q

0+0 records in

0+0 records out

0 bytes (0 B) copied0000000

, 5.9648e-05 s, 0.0 kB/s

root@Silencio:/boot/config#

 

 

Smart Log:

 

 

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build)

Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

 

=== START OF INFORMATION SECTION ===

Device Model:    ST3000VN000-1HJ166

Serial Number:    W73011GP

LU WWN Device Id: 5 000c50 0781dca3e

Firmware Version: SC60

User Capacity:    3,000,592,982,016 bytes [3.00 TB]

Sector Sizes:    512 bytes logical, 4096 bytes physical

Rotation Rate:    5900 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:    Sat Apr  4 17:45:02 2015 SGT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status:      (  0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: (  107) seconds.

Offline data collection

capabilities: (0x73) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

No Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: (  1) minutes.

Extended self-test routine

recommended polling time: ( 388) minutes.

Conveyance self-test routine

recommended polling time: (  2) minutes.

SCT capabilities:       (0x10bd) SCT Status supported.

SCT Error Recovery Control supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x000f  100  100  006    Pre-fail  Always      -      26736

  3 Spin_Up_Time            0x0003  100  100  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      -      7

  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

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  070  069  045    Old_age  Always      -      30 (Min/Max 26/31)

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

194 Temperature_Celsius    0x0022  030  040  000    Old_age  Always      -      30 (0 26 0 0 0)

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  200  253  000    Old_age  Always      -      0

 

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

That dd command failing to read any data from the disk is definitely worrying.  I would be extremely cautious about assuming this drive is OK at the moment.

 

Maybe the next step is to use smartctl to run some of the self-tests (which I see have never been run) to see if they complete OK.  The dd results suggest to me that even the short test may fail.

Link to comment

Disk definitely virginal. Never seen such low numbers!

 

Self-tests are a good idea as was already mentioned.

 

If the self-test passes, the behavior might be due to bad cabling. Although this doesn't have the normal symptoms, I'd definitely try replacing the SATA cable.

 

 

Link to comment

Disk definitely virginal. Never seen such low numbers!

 

Self-tests are a good idea as was already mentioned.

 

If the self-test passes, the behavior might be due to bad cabling. Although this doesn't have the normal symptoms, I'd definitely try replacing the SATA cable.

I would try running the short smart test before doing anything that would power cycle the disk.

 

type

smartctl -t short /dev/sdi

then wait  for the time it indicates and get a new smart report

smartctl -A /dev/sdi

 

followed by the same steps for the long test, waiting several hours or more as indicated when invoked before getting a subsequent smartctl -A report.

(Don't forget to disable any spin-down timers, as spinning down the disk will terminate the long test.)

smartctl -t long /dev/sdi

waiting hours as needed, then

smartctl -A /dev/sdi

It might have currently stopped responding to read requests, but might start again if power cycled.  The actual issue could be with the disk controller OR the disk itself.

(That is not a good behavior, as if you cease being able to read a disk it is a very bad thing in any network-storage-device)

Link to comment
  • 2 weeks later...

Hi all,

 

Newbie just starting out with Unraid, so be gentle...

 

6.0-beta14b on an i3-2100 with 8GB RAM. LSI9211-8i with 4x 5TB WD RED + 2 Sandisk 128GB SSD for cache.

 

Done preclear with results and SMART per below. Looks fine with my limited knowledge.

However, the last of the four drives took much longer to process. Should I be concerned with this? Or could it be a resource issue on CPU/RAM - the GUI was very sluggish during the entire process.

 

Thx for any feedback

 

Drive 1 (sdb) Preclear

== invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 3 /dev/sdb
== WDCWD50EFRX-68MYMN1   WD-WX11DA40H514
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1
== Ran 3 cycles
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 11:33:42 (120 MB/s)
== Last Cycle's Zeroing time   : 9:59:08 (139 MB/s)
== Last Cycle's Post Read Time : 21:34:18 (64 MB/s)
== Last Cycle's Total Time     : 31:34:25
==
== Total Elapsed Time 106:26:03
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: 32C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   120     122            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 3.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
0 sectors were pending re-allocation after post-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
0 sectors were pending re-allocation after post-read in cycle 2 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================

 

Drive 2 (sdc) Preclear

== invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 3 /dev/sdc
== WDCWD50EFRX-68MYMN1   WD-WX11DA40HE2L
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1
== Ran 3 cycles
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 11:31:33 (120 MB/s)
== Last Cycle's Zeroing time   : 10:01:20 (138 MB/s)
== Last Cycle's Post Read Time : 21:23:55 (64 MB/s)
== Last Cycle's Total Time     : 31:26:14
==
== Total Elapsed Time 105:53:18
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: 32C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   120     122            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 3.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
0 sectors were pending re-allocation after post-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
0 sectors were pending re-allocation after post-read in cycle 2 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================

 

Drive 3 (sdd) Preclear

== invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 3 /dev/sdd
== WDCWD50EFRX-68MYMN1   WD-WX11DA40HF8E
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 1
== Ran 3 cycles
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 11:39:03 (119 MB/s)
== Last Cycle's Zeroing time   : 10:11:16 (136 MB/s)
== Last Cycle's Post Read Time : 21:41:50 (64 MB/s)
== Last Cycle's Total Time     : 31:54:05
==
== Total Elapsed Time 107:24:17
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: 32C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   120     122            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 3.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
0 sectors were pending re-allocation after post-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
0 sectors were pending re-allocation after post-read in cycle 2 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.
============================================================================

 

Drive 4 (sde) Preclear (notice the time to complete vs the others)

== invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 3 /dev/sde
== WDCWD50EFRX-68MYMN1   WD-WX11DA40HSHL
== Disk /dev/sde has been successfully precleared
== with a starting sector of 1
== Ran 3 cycles
==
== Using :Read block size = 65536 Bytes
== Last Cycle's Pre Read Time  : 11:12:19 (123 MB/s)
== Last Cycle's Zeroing time   : 20:04:35 (69 MB/s)
== Last Cycle's Post Read Time : 21:02:44 (66 MB/s)
== Last Cycle's Total Time     : 41:08:17
==
== Total Elapsed Time 147:11:29
==
== Disk Start Temperature: 30C
==
== Current Disk Temperature: 33C,
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   119     122            0        ok          33
No SMART attributes are FAILING_NOW

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

 

SMART Drive 1

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       166
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       62
194 Temperature_Celsius     0x0022   122   117   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       157         -

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.

 

SMART Drive 2

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       166
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       59
194 Temperature_Celsius     0x0022   122   118   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       157         -

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.

 

Smart Drive 3

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       166
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       58
194 Temperature_Celsius     0x0022   122   117   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       158         -

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.

 

Smart Drive 4

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       166
10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       20
194 Temperature_Celsius     0x0022   122   117   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       157         -

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

Done preclear with results and SMART per below. Looks fine with my limited knowledge.

However, the last of the four drives took much longer to process. Should I be concerned with this? Or could it be a resource issue on CPU/RAM - the GUI was very sluggish during the entire process.

 

There do not appear to be any issues evident with any of the drives, apart from a slower write speed for the fourth drive.  The only difference is that the fourth drive reads a little faster than the others, but writes half as fast as the others.  For the fourth drive, preread time was 11 hours vs. 11.5 hours for the other drives, and postread time was 21 hours vs. 21.5 hours for the others.  Write speed was 20 hours vs. 10 hours for the others.

 

You can examine the complete SMART reports for each drive, to see what their firmware is (in the 'INFORMATION SECTION').  Perhaps one of the drives has a different firmware version.  If you did all 4 drives simultaneously, then there may be differences in the drive controllers and busses used.  It would still be hard to explain writes being much slower and reads faster though.

Link to comment

 

There do not appear to be any issues evident with any of the drives, apart from a slower write speed for the fourth drive.  The only difference is that the fourth drive reads a little faster than the others, but writes half as fast as the others.  For the fourth drive, preread time was 11 hours vs. 11.5 hours for the other drives, and postread time was 21 hours vs. 21.5 hours for the others.  Write speed was 20 hours vs. 10 hours for the others.

 

You can examine the complete SMART reports for each drive, to see what their firmware is (in the 'INFORMATION SECTION').  Perhaps one of the drives has a different firmware version.  If you did all 4 drives simultaneously, then there may be differences in the drive controllers and busses used.  It would still be hard to explain writes being much slower and reads faster though.

 

Thx for feedback. Yes, I did all of the 4 drives at the same time. Checked the FW revision and it is the same 4 all four.

I am thinking maybe I should try running a single pass on one drive at the time to see if the pattern remains? If I use the disk, considering its slow writes, would it be best as parity disk or part of the array?

 

Device Model:     WDC WD50EFRX-68MYMN1
Serial Number:    WD-WX11DA40H514
LU WWN Device Id: 5 0014ee 2b5ead6e4
Firmware Version: 82.00A82

Device Model:     WDC WD50EFRX-68MYMN1
Serial Number:    WD-WX11DA40HE2L
LU WWN Device Id: 5 0014ee 20b3fcab4
Firmware Version: 82.00A82

Device Model:     WDC WD50EFRX-68MYMN1
Serial Number:    WD-WX11DA40HF8E
LU WWN Device Id: 5 0014ee 2b5e9fc27
Firmware Version: 82.00A82

Device Model:     WDC WD50EFRX-68MYMN1
Serial Number:    WD-WX11DA40HSHL
LU WWN Device Id: 5 0014ee 2b5eaebd7
Firmware Version: 82.00A82

Link to comment

You definitely do not want to use it for your parity drive!

 

If you have time, you might try one more pass on the fourth drive, but connected to a different port.  If it still is a slow writer, that won't usually matter too much as an unRAID data drive, since typically you are archiving data to it, not using it for applications.  It will be best reserved for old backups, and files that rarely change, operations that involve few writes but many reads.

Link to comment

Hi All, I am trying to add a 3TB WD Red Drive to my array and the first preclear run just got completed, can someone check and let me know if this is fine? also how many preclear cycle should I run, 20 cycles might take lot of time:-) what would be the minimum safe number of runs?

 

I got this one line in the final summary, is this a issue? : 1 sector was pending re-allocation after pre-read in cycle 1 of 1.

 

I started the preclear with this command : preclear_disk.sh -A -M 4 /dev/sdf

Summary.txt

preclear_finish_2015-04-26.txt

Link to comment

Hi All, I am trying to add a 3TB WD Red Drive to my array and the first preclear run just got completed, can someone check and let me know if this is fine? also how many preclear cycle should I run, 20 cycles might take lot of time:-) what would be the minimum safe number of runs?

Drive looks fine, no issues.  Popular pass counts are one and three, I run just one pass, but many like 3 passes.

 

I got this one line in the final summary, is this a issue? : 1 sector was pending re-allocation after pre-read in cycle 1 of 1.

Just means the pre-read found a sector where the data was scrambled enough that the ECC (error correcting) info could not fix it.  But further testing found that the sector media underneath the sector was good, so good data is now written there.  If in doubt, run another pass.

Link to comment

For giggles.. I decided to take a look at my smart report from unraid.  This is what I got

 

» reported_uncorrect=31

» high_fly_writes=112

» current_pending_sector=64

» offline_uncorrectable=64

» ata_error_count=31

 

This is on my parity drive.  I have no idea when these occurred.  My last parity check was 25 days ago with no sync errors.

 

What should I do?  It just under a year old.

 

Thanks,

 

Jim

Link to comment

For giggles.. I decided to take a look at my smart report from unraid.  This is what I got

 

» reported_uncorrect=31

» high_fly_writes=112

» current_pending_sector=64

» offline_uncorrectable=64

» ata_error_count=31

 

This is on my parity drive.  I have no idea when these occurred.  My last parity check was 25 days ago with no sync errors.

 

What should I do?  It just under a year old.

 

Thanks,

 

Jim

 

High fly writes can be ignored ... they're not a problem.  HOWEVER ... both pending sectors and offline uncorrectable are parameters you want to be ZERO.    I'd replace the drive;  reformat it; and use it for backups or some other off-line use.

 

Link to comment

For giggles.. I decided to take a look at my smart report from unraid.  This is what I got

 

» reported_uncorrect=31

» high_fly_writes=112

» current_pending_sector=64

» offline_uncorrectable=64

» ata_error_count=31

 

This is on my parity drive.  I have no idea when these occurred.  My last parity check was 25 days ago with no sync errors.

 

What should I do?  It just under a year old.

Pending sectors are a bad thing as they indicate sectors that cannot be read properly.    However it is not at all unusual for them to be cleared when they are next written.

 

I would suggest that you might want to consider temporarily removing the parity disk from the array (however note that leaves you unprotected against another disk failing) and put it through a pre-clear cycle to see if the pending sectors resolve themselves. If it does then you are probably OK with that drive although it will bear watching.  It not then you want to look into an RMA for the drive.  If you have another spare disk of sufficient size you could put it in place of the current parity disk and let parity build onto that drive instead.

Link to comment

Pending sectors are a bad thing as they indicate sectors that cannot be read properly.    However it is not at all unusual for them to be cleared when they are next written.

 

I would suggest that you might want to consider temporarily removing the parity disk from the array (however note that leaves you unprotected against another disk failing) and put it through a pre-clear cycle to see if the pending sectors resolve themselves. If it does then you are probably OK with that drive although it will bear watching.  It not then you want to look into an RMA for the drive.  If you have another spare disk of sufficient size you could put it in place of the current parity disk and let parity build onto that drive instead.

I thought about doing this.  Coincidentally, I'm almost done preclearing another drive for  a different use.  maybe I'll just temporarily switch it out with the new drive and run another preclear..  hmm..

 

Will  Seagate replace a drive with 64 bad sectors?

 

 

Link to comment

I thought about doing this.  Coincidentally, I'm almost done preclearing another drive for  a different use.  maybe I'll just temporarily switch it out with the new drive and run another preclear..  hmm..

 

Will  Seagate replace a drive with 64 bad sectors?

I have never had Seagate query a RMA in practise. 

 

If they were reallocated sectors that would be one thing, but sectors that cannot be read or reallocated would be another I would think as that makes the disk unfit for use.

Link to comment

Just a caution before you throw out the drive too quick, pending sectors may or may not be bad.  The numbers you showed do indicate the drive needs some repair work, but do not mean the drive is bad, until after testing it.  Technically, 'pending' means 'pending full testing', which happens once you tell the drive you don't care about the current data stored there.  You do that by writing to it, so that the drive now knows you are OK'ing overwriting the current data.  It then can thoroughly test the sector to see how safely it saves test patterns, and if good, saves the data you requested to be saved there and unmarks it as pending.  If it decides the sector cannot be trusted, then it is remapped to a good spare sector.

 

A sector is marked as a 'current pending sector' when it fails to be read correctly, even after applying the error correction info.  That can happen either because of weak or damaged magnetic media under the sector, or because of electrical activity (spikes and outages while writing) that have scrambled too many bits in the sector.  I tend to call the latter ones 'soft errors', because the physical sector is completely fine, and testing will prove that.

 

If you have had a power outage or sparking or other serious power issues, then the 64 sectors may just be soft errors, and the drive be perfectly fine, once tested and rebuilt.

Link to comment

I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

Disk: /dev/sdf
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 ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD30EFRX-68EUZN0
LU WWN Device Id: 5 0014ee 6b002b183
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Apr 28 08:28:42 2015 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(41760) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 418) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       8
  3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       66
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       -       1
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       4
194 Temperature_Celsius     0x0022   120   119   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

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


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



Link to comment

I just completed the second preclear cycle and have Current_Pending_Sector = 2 and Raw_Read_Error_Rate=8, as per the explanation from RobJ above i think this should be ok right? I am planning to replace this drive as the Parity drive. Should I run one more cycle just to be on the safe side?

 

The "Raw_Read_Error_Rate=8" is not a problem, because the raw value for that attribute is meaningless.  What's important is the VALUE for it, 200, which is perfect.

 

What IS a problem is the "Current_Pending_Sector = 2".  As was stated above, that HAS to be zero.  If this SMART report occurred right after a Preclear then that is a bad sign.  Preclear it again, and if Current_Pending_Sector stays non-zero, I would not use that drive, it can't be trusted.

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.