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


Recommended Posts

It's not necessary for the array to be started but it will help if the first "protection layer" fails.

 

 

Make sure you have the up to date version (1.13) of preclear.

If you still can see your array drives, then you might experience a bug!

Be careful not to wipe one of your array disks! Tripe check the serial number of the drive before typing "Yes"!

Link to comment

There's an issue with the -l  (list) option in pre-clear when running under version 5.  It will list ALL of the drives, whether or not they're in the array unless you (a) Start the array and (b) access the Web GUI (once is enough).    Then the "preclear_disk.sh -l" command will correctly list only those disks outside the array.

 

You don't, of course, have to bother if you're CERTAIN which disk you want to pre-clear.    But it's a nice "sanity check", and certainly worthwhile to confirm you're picked the right one.

 

I don't know if Joe L plans to modify the script to correct this or not -- he may be waiting until v5.0 is released before making any changes.

 

Link to comment

This may have already been mentioned.. but I can't seem to find it with the search..

 

Just got a new drive and went to pre clear it.. ran pre clear_disk.sh -l and it is showing ALL my disks, not just the unassigned ones. Is this a known issue or is there something wrong that might cause this??

 

Cheers,

 

whiteatoms

In the latest 5.X releases the array must be started for preclear to find the assigned disks.  Yes, known issue with the latest unRAID.  It use to keep a "readable" file with the disk assignments in the /boot/config folder, apparently, it no longer does.

 

MAKE SURE YOU KNOW THE DISK YOU WILL BE CLEARING BY THE SERIAL NUMBER...

 

Joe L.

Link to comment

Joe -- the array not only has to be started, but you have to access the Web GUI one time before the pre-clear script excludes the array disks.    I have absolutely no idea why that's the case, but if you simply Start the array (i.e. set it to auto-start), pre-clear will still list all of the disks until the Web GUI has been looked at one time.

 

But if you simply look at the Web GUI one time, pre-clear will then list the disks correctly -- i.e. it will only list those that are not part of the array.

 

Link to comment

I suspect in your case it has something to do with the fact you added the drive "hot" ... nothing wrong with doing that on a hot-swappable setup, but most folks power off to add drives, so the pre-clear is after a reboot.    And in that case, the behavior with v5 is you have to start the array; then access the web GUI; and then it works perfectly.    ... at least on every system I've seen (perhaps a dozen) and those that have reported the behavior on the forum.

 

Link to comment
  • 2 weeks later...

Is  End-to-End_Error something that I need to be worried about ?

 

 ==  Hitachi HTS541010A9E680    J8100019J1XWJA

 

 

 ** Changed attributes in files: /tmp/smart_start_sdb  /tmp/smart_finish_sdb
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         End-to-End_Error =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    74      76           45        In_the_past 26
No SMART attributes are FAILING_NOW

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

 

 

 

  SMART status Info for /dev/sdb
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HTS541010A9E680
Serial Number:    J8100019J1XWJA
Firmware Version: JA0OA4D0
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Sun Sep  8 07:55:16 2013 CEST
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 247)	Self-test routine in progress...
				70% of test remaining.
Total time to complete Offline 
data collection: 		 (  45) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
				No Auto Offline data collection support.
				Suspend Offline collection upon new
				command.
				No Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 241) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0025   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0023   170   100   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1565
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       1721
10 Spin_Retry_Count        0x0033   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1479
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       25769803777
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       73015623682
190 Airflow_Temperature_Cel 0x0022   079   044   045    Old_age   Always   In_the_past 21 (Min/Max 21/30)
191 G-Sense_Error_Rate      0x0032   096   096   000    Old_age   Always       -       1198
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1966110
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always       -       23668
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x002a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 494 hours (20 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  10 41 00 00 75 64 07

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 98 f0 62 ed 40 00      00:42:01.616  READ FPDMA QUEUED
  60 00 90 f0 61 ed 40 00      00:42:01.615  READ FPDMA QUEUED
  60 00 88 f0 60 ed 40 00      00:42:01.614  READ FPDMA QUEUED
  60 00 80 f0 5f ed 40 00      00:42:01.613  READ FPDMA QUEUED
  60 00 78 f0 5e ed 40 00      00:42:01.610  READ FPDMA QUEUED

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

Is  End-to-End_Error something that I need to be worried about ?

 

No ... not while the value is 100.  If the value starts to drop, then yes, it would be a bad sign.  It's not even clear why it's listed as a "changed" parameter, since both the before and after values were 100 (which is what you want it to be).

 

Link to comment

Hot Swap/Hot Plug is supported in the base SATA spec. It's been part of the spec for dang near 10 years. This includes power AND data cabling. Some (a very small percentage) of motherboards don't support. They don't support it because they were built wrong. I haven't owned a computer since 06 that hasn't properly supported hot swap. If they meet SATA spec, they are capable of hot swapping/hot plugging. However you want to call it.

 

I suspect in your case it has something to do with the fact you added the drive "hot" ... nothing wrong with doing that on a hot-swappable setup, but most folks power off to add drives, so the pre-clear is after a reboot.    And in that case, the behavior with v5 is you have to start the array; then access the web GUI; and then it works perfectly.    ... at least on every system I've seen (perhaps a dozen) and those that have reported the behavior on the forum.

Link to comment

Hot Swap is support on *ANY* properly built SATA system.

 

Hot-swap is supported on any SATA-II or later system that supports AHCI, but ONLY if AHCI is enabled in the BIOS.    I presume yours is ... but it wouldn't hurt to check.

 

... and despite technically supporting it, I've seen a fair number of systems it simply doesn't work well on.

Link to comment

Can one of the experts comment on the attached log showing two separate pre-cleared disks?

 

Thank you!

 

FIRST DISK
Disk: /dev/sdi
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS5C3030ALA630
Firmware Version: MEAOA5C0
User Capacity:    3,000,592,982,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:    Mon Sep  9 15:50:57 2013 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:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (37267) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   139   139   024    Pre-fail  Always       -       550 (Average 451)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       44
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       12
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       12
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 24/33)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

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


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





SECOND DISK
Disk: /dev/sdh
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HDS5C3030ALA630
Firmware Version: MEAOA5C0
User Capacity:    3,000,592,982,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:    Mon Sep  9 17:30:54 2013 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:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (38166) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
				Auto Offline data collection on/off support.
				Suspend Offline collection upon new
				command.
				Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
				power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   143   143   024    Pre-fail  Always       -       538 (Average 441)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       12
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       46
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       13
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       13
194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 24/33)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

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


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

root@Tower:/boot/preclear_reports# 

Link to comment

Thanks - I "more'd" the wrong files :)

 

Both drives show:

 

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.

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

 

Link to comment

The vast majority (in fact every one I've ever seen) of failures occur during the 1st cycle.

 

If you're still getting increasing reallocated sectors, you'll see that with the results of the first cycle => THEN it's a good idea to run more [although I'd be inclined to simply RMA the drive in the case].

 

 

Link to comment

Is this disk unsafe to use, with the Raw_Read_Error_Rate being so high?

All disks have raw-read-errors, some report them, some do not.

 

The failure threshold of 006 for that parameter in SMART is not close to the current normalized value of 116,  however the "worst" normalized value has been as low as 99, so I'd keep an eye on the disk over the next months/years.  It looks great otherwise.

 

  1 Raw_Read_Error_Rate    0x000f  116  099  006    Pre-fail  Always      -      105202000

 

The normalized value actually improved from 114 to 116 over the course of the preclear.  That is a good sign.

Link to comment

Is this disk unsafe to use, with the Raw_Read_Error_Rate being so high?

All disks have raw-read-errors, some report them, some do not.

 

The failure threshold of 006 for that parameter in SMART is not close to the current normalized value of 116,  however the "worst" normalized value has been as low as 99, so I'd keep an eye on the disk over the next months/years.  It looks great otherwise.

 

  1 Raw_Read_Error_Rate    0x000f  116  099  006    Pre-fail  Always      -      105202000

 

The normalized value actually improved from 114 to 116 over the course of the preclear.  That is a good sign.

 

Thanks for the help!  :)

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.