Jump to content
jbuszkie

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

2840 posts in this topic Last Reply

Recommended Posts

I'm sorry, I realize I skipped right over the obvious.  The count of 57240 is clearly not a real number, roughly 10 times the possible maximum, just a random number, indicating corruption in the SMART system.  I completely forgot to state that, just assumed others would automatically recognize that.  It would be interesting to see the SMART report, see what other corruption it reveals.

 

It wouldn't surprise me if there actually aren't ANY sectors reallocated, but probably going to be hard to tell for sure.

 

Final results a second time are fully the same as the first time.  No change.  I've posted all the reports as an attachment to see if we can figure out this one...

 

Love these 3tb Seagate drives faster than a speeding bullet.  Others have had lots of issues with them, but I've been lucky with only one in about 20 drives.

preclear_reports.zip

Share this post


Link to post

Final results a second time are fully the same as the first time.  No change.  I've posted all the reports as an attachment to see if we can figure out this one...

 

Love these 3tb Seagate drives faster than a speeding bullet.  Others have had lots of issues with them, but I've been lucky with only one in about 20 drives.

 

Perfect time for a SMART long test!  Since the long test examines every sector, it should (if the code is done right) reinitialize the overall counters, as to how many are really remapped.

 

It's probably a coincidence, but can't help noticing that both VALUE and WORST for Reallocated_Sector_Ct is 57, same as the leading integers of the RAW 57240.  Could be a bug there.  Unfortunately, that doesn't make sense from a programmatic view, as it's 57 and 57000, VERY different numbers.

 

The one way you can estimate the number of spares a given drive model has is to find one with a number of reallocated sectors and see how far it dropped the VALUE for Reallocated_Sector_Ct.  It dropped it 43% for your drive with a count of 57240, so if you extrapolate that, you get an estimate of about 130,000 spare sectors, an obviously crazy number!  What we need is a SMART report for another ST3000DM001-9YN166 with reallocated sectors, to see what the real spare count should be.

 

You are at 6300 operational hours now.  Back at 2860 hours, something went wrong, ostensibly with uncorrectable sectors.  The reported LBA numbers are meaningless though, so it's hard to tell what actually was wrong.  Certainly not confidence building in this drive.

 

All other numbers look fine, with a very few runtime bad blocks and uncorrectable sectors, nothing that correlates with 57000 of them though, or even 240 of them.  Kinda funny but the Raw_Read_Error_Rate has improved with every single SMART report, has never been worse than 99 (almost perfect).

Share this post


Link to post

Final results a second time are fully the same as the first time.  No change.  I've posted all the reports as an attachment to see if we can figure out this one...

 

Love these 3tb Seagate drives faster than a speeding bullet.  Others have had lots of issues with them, but I've been lucky with only one in about 20 drives.

 

Perfect time for a SMART long test!  Since the long test examines every sector, it should (if the code is done right) reinitialize the overall counters, as to how many are really remapped.

 

It's probably a coincidence, but can't help noticing that both VALUE and WORST for Reallocated_Sector_Ct is 57, same as the leading integers of the RAW 57240.  Could be a bug there.  Unfortunately, that doesn't make sense from a programmatic view, as it's 57 and 57000, VERY different numbers.

 

The one way you can estimate the number of spares a given drive model has is to find one with a number of reallocated sectors and see how far it dropped the VALUE for Reallocated_Sector_Ct.  It dropped it 43% for your drive with a count of 57240, so if you extrapolate that, you get an estimate of about 130,000 spare sectors, an obviously crazy number!  What we need is a SMART report for another ST3000DM001-9YN166 with reallocated sectors, to see what the real spare count should be.

 

You are at 6300 operational hours now.  Back at 2860 hours, something went wrong, ostensibly with uncorrectable sectors.  The reported LBA numbers are meaningless though, so it's hard to tell what actually was wrong.  Certainly not confidence building in this drive.

 

All other numbers look fine, with a very few runtime bad blocks and uncorrectable sectors, nothing that correlates with 57000 of them though, or even 240 of them.  Kinda funny but the Raw_Read_Error_Rate has improved with every single SMART report, has never been worse than 99 (almost perfect).

 

Ok here is the long smart test report and the preclear report for another ST3000DM001-9YN166.  Sorry it doesn't have issues though....

 

Found another one with errors. ED2

 

 smartctl -a -A /dev/sdn
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-9YN166
Serial Number:    W1F0LAFX
LU WWN Device Id: 5 000c50 05246d833
Firmware Version: CC9E
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Aug 24 20:25:32 2015 CDT
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:                (  584) 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:        ( 338) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x3081) SCT Status 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       -       104284160
  3 Spin_Up_Time            0x0003   093   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1186
  5 Reallocated_Sector_Ct   0x0033   057   057   036    Pre-fail  Always       -       57240
  7 Seek_Error_Rate         0x000f   075   060   030    Pre-fail  Always       -       36360856
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6378
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       848
183 Runtime_Bad_Block       0x0032   097   097   000    Old_age   Always       -       3
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   068   068   000    Old_age   Always       -       32
188 Command_Timeout         0x0032   100   097   000    Old_age   Always       -       11 18 18
189 High_Fly_Writes         0x003a   098   098   000    Old_age   Always       -       2
190 Airflow_Temperature_Cel 0x0022   057   046   045    Old_age   Always       -       43 (Min/Max 35/50)
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       -       99
193 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       12620
194 Temperature_Celsius     0x0022   043   054   000    Old_age   Always       -       43 (0 7 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   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1148h+05m+44.061s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       20989294796726
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       178319632353629

SMART Error Log Version: 1
ATA Error Count: 28 (device log contains only the most recent five errors)
        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 28 occurred at disk power-on lifetime: 2860 hours (119 days + 4 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      01:35:54.630  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:35:54.625  READ DMA EXT
  25 00 90 ff ff ff ef 00      01:35:49.050  READ DMA EXT
  25 00 d8 ff ff ff ef 00      01:35:49.042  READ DMA EXT
  25 00 68 ff ff ff ef 00      01:35:49.041  READ DMA EXT

Error 27 occurred at disk power-on lifetime: 2860 hours (119 days + 4 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      01:34:21.313  READ DMA EXT
  ea 00 00 ff ff ff af 00      01:34:21.039  FLUSH CACHE EXT
  25 00 00 ff ff ff ef 00      01:34:21.019  READ DMA EXT
  35 00 08 ff ff ff ef 00      01:34:21.019  WRITE DMA EXT
  35 00 08 ff ff ff ef 00      01:34:21.019  WRITE DMA EXT

Error 26 occurred at disk power-on lifetime: 2860 hours (119 days + 4 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      01:34:17.122  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:34:16.265  READ DMA EXT
  25 00 10 ff ff ff ef 00      01:34:16.188  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:34:14.071  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:34:13.801  READ DMA EXT

Error 25 occurred at disk power-on lifetime: 2860 hours (119 days + 4 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      01:34:09.809  READ DMA EXT
  ea 00 00 ff ff ff af 00      01:34:09.558  FLUSH CACHE EXT
  25 00 00 ff ff ff ef 00      01:34:09.539  READ DMA EXT
  35 00 08 ff ff ff ef 00      01:34:09.538  WRITE DMA EXT
  35 00 08 ff ff ff ef 00      01:34:09.538  WRITE DMA EXT

Error 24 occurred at disk power-on lifetime: 2860 hours (119 days + 4 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      01:34:06.061  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:34:06.058  READ DMA EXT
  ea 00 00 ff ff ff af 00      01:34:05.782  FLUSH CACHE EXT
  25 00 00 ff ff ff ef 00      01:34:05.757  READ DMA EXT
  35 00 08 ff ff ff ef 00      01:34:05.757  WRITE DMA EXT

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%      6377         -
# 2  Short offline       Completed without error       00%      6372         -
# 3  Short offline       Completed without error       00%      6372         -
# 4  Short offline       Completed without error       00%      2164         -
# 5  Extended offline    Aborted by host               90%      1721         -
# 6  Short offline       Completed without error       00%      1720         -
# 7  Short offline       Completed without error       00%      1417         -

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.

preclear_rpt_W1F0N4JK_2015-07-19.zip

preclear_start_W1F0MED2_2015-08-17.zip

Share this post


Link to post

I just upgraded from v5.0.6 -> v6.1 and I'm now noticing SMART warnings for two disks. I'd like some help

 

1.) Parity drive - ST3000DM001 (reported uncorrect is 1)

 

1	Raw Read Error Rate	0x000f	105	099	006	Pre-fail	Always	-	9702136
3	Spin Up Time	0x0003	094	094	000	Pre-fail	Always	-	0
4	Start Stop Count	0x0032	095	095	020	Old age	Always	-	5286
5	Reallocated Sector Ct	0x0033	100	100	010	Pre-fail	Always	-	0
7	Seek Error Rate	0x000f	047	043	030	Pre-fail	Always	-	1859744137980
9	Power On Hours	0x0032	073	073	000	Old age	Always	-	23749 (2y, 259d, 13h)
10	Spin Retry Count	0x0013	100	100	097	Pre-fail	Always	-	0
12	Power Cycle Count	0x0032	100	100	020	Old age	Always	-	55
183	Runtime Bad Block	0x0032	099	099	000	Old age	Always	-	1
184	End-to-End Error	0x0032	100	100	099	Old age	Always	-	0
187	Reported Uncorrect	0x0032	099	099	000	Old age	Always	-	1
188	Command Timeout	0x0032	100	100	000	Old age	Always	-	0 0 0
189	High Fly Writes	0x003a	099	099	000	Old age	Always	-	1
190	Airflow Temperature Cel	0x0022	069	058	045	Old age	Always	-	31 (Min/Max 21/35)
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	-	55
193	Load Cycle Count	0x0032	014	014	000	Old age	Always	-	172046
194	Temperature Celsius	0x0022	031	042	000	Old age	Always	-	31 (0 15 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	200	000	Old age	Always	-	3
240	Head Flying Hours	0x0000	100	253	000	Old age	Offline	-	5201h+54m+36.322s
241	Total LBAs Written	0x0000	100	253	000	Old age	Offline	-	37836775592
242	Total LBAs Read	0x0000	100	253	000	Old age	Offline	-	227760941004

 

2.) Data drive - TOSHIBA DT01ACA300 ( reallocated sector ct is 48 / current pending sector is 8 )

 

1	Raw Read Error Rate	0x000b	100	100	016	Pre-fail	Always	-	0
2	Throughput Performance	0x0005	139	139	054	Pre-fail	Offline	-	73
3	Spin Up Time	0x0007	133	133	024	Pre-fail	Always	-	430 (Average 430)
4	Start Stop Count	0x0012	100	100	000	Old age	Always	-	2798
5	Reallocated Sector Ct	0x0033	100	100	005	Pre-fail	Always	-	48
7	Seek Error Rate	0x000b	100	100	067	Pre-fail	Always	-	0
8	Seek Time Performance	0x0005	124	124	020	Pre-fail	Offline	-	33
9	Power On Hours	0x0012	099	099	000	Old age	Always	-	9679 (1y, 38d, 7h)
10	Spin Retry Count	0x0013	100	100	060	Pre-fail	Always	-	0
12	Power Cycle Count	0x0032	100	100	000	Old age	Always	-	17
192	Power-Off Retract Count	0x0032	098	098	000	Old age	Always	-	2799
193	Load Cycle Count	0x0012	098	098	000	Old age	Always	-	2799
194	Temperature Celsius	0x0002	181	181	000	Old age	Always	-	33 (Min/Max 19/42)
196	Reallocated Event Count	0x0032	100	100	000	Old age	Always	-	49
197	Current Pending Sector	0x0022	100	100	000	Old age	Always	-	8
198	Offline Uncorrectable	0x0008	100	100	000	Old age	Offline	-	0
199	UDMA CRC Error Count	0x000a	200	200	000	Old age	Always	-	0

 

Thoughts? Which should I be more concerned about?

Share this post


Link to post

I just upgraded from v5.0.6 -> v6.1 and I'm now noticing SMART warnings for two disks. I'd like some help

 

1.) Parity drive - ST3000DM001 (reported uncorrect is 1)

5	Reallocated Sector Ct	0x0033	100	100	010	Pre-fail	Always	-	0
183	Runtime Bad Block	0x0032	099	099	000	Old age	Always	-	1
187	Reported Uncorrect	0x0032	099	099	000	Old age	Always	-	1
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	-	3

No problem here.  That's a historical counter, indicates there was one in the past, but it's fine now.

 

2.) Data drive - TOSHIBA DT01ACA300 ( reallocated sector ct is 48 / current pending sector is 8 )

5	Reallocated Sector Ct	0x0033	100	100	005	Pre-fail	Always	-	48
196	Reallocated Event Count	0x0032	100	100	000	Old age	Always	-	49
197	Current Pending Sector	0x0022	100	100	000	Old age	Always	-	8
198	Offline Uncorrectable	0x0008	100	100	000	Old age	Offline	-	0
199	UDMA CRC Error Count	0x000a	200	200	000	Old age	Always	-	0

 

Thoughts? Which should I be more concerned about?

 

The Current Pending Sectors ARE a problem!  They MUST be dealt with.  Do you have a replacement drive?  Preferably, you want to unassign it, start and stop the array without it, then assign the replacement drive and let it rebuild onto it.  Then Preclear the Toshiba above twice, until clean, no pending sectors.

Share this post


Link to post

The Current Pending Sectors ARE a problem!  They MUST be dealt with.  Do you have a replacement drive?  Preferably, you want to unassign it, start and stop the array without it, then assign the replacement drive and let it rebuild onto it.  Then Preclear the Toshiba above twice, until clean, no pending sectors.

 

Thanks RobJ, I have replaced the Toshiba and in the process of rebuilding. So to clarify, you suggest running the preclear on the Toshiba to clean out the pending sectors?

 

It's still under warranty, I had in mind to RMA it. Is it worth keeping at this point? I was planning on just writing zeros (with the -W switch) and sending it back. Would the zeroing of the drive alone fix the pending sectors?

 

Have yet to RMA a Toshiba drive, do they send you a recertified one back like seagate?

Share this post


Link to post

The Current Pending Sectors ARE a problem!  They MUST be dealt with.  Do you have a replacement drive?  Preferably, you want to unassign it, start and stop the array without it, then assign the replacement drive and let it rebuild onto it.  Then Preclear the Toshiba above twice, until clean, no pending sectors.

 

Thanks RobJ, I have replaced the Toshiba and in the process of rebuilding. So to clarify, you suggest running the preclear on the Toshiba to clean out the pending sectors?

 

It's still under warranty, I had in mind to RMA it. Is it worth keeping at this point? I was planning on just writing zeros (with the -W switch) and sending it back. Would the zeroing of the drive alone fix the pending sectors?

Some users are quick to RMA.  My preference is to try to clean it, while monitoring the SMART info.  I would hope that the first Preclear clears all pending sectors, then the second Preclear has no changes at all, indicating some stability.  Some users would Preclear it one more time, dare it to misbehave.  If it takes more Preclears, then my confidence in the drive starts dropping.

 

Have yet to RMA a Toshiba drive, do they send you a recertified one back like seagate?

No experience.  Hopefully someone else will respond.

Share this post


Link to post

RobJ, I precleared the Toshiba three times, here's the output:

 

================================================================== 1.15
=                unRAID server Pre-Clear disk /dev/sdp
=               cycle 3 of 3, partition start on sector 1
=
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 35C, Elapsed Time:  67:54:01
========================================================================1.15
== TOSHIBADT01ACA300  
== Disk /dev/sdp has been successfully precleared
== with a starting sector of 1
============================================================================
** Changed attributes in files: /tmp/smart_start_sdp  /tmp/smart_finish_sdp
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   171     136            0        ok          35
No SMART attributes are FAILING_NOW

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

 

I no longer see the pending, and I assume I should just keep it at this point, instead of going through the hassle of rma'ing it.

Share this post


Link to post

RobJ, I precleared the Toshiba three times, here's the output:

 

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

 

I no longer see the pending, and I assume I should just keep it at this point, instead of going through the hassle of rma'ing it.

 

Looks fine to me!  Sectors that appear bad may be because they ARE bad, or may just look like it because an electrical spike occurred while the sector was being written, causing scrambled data to be written.  Once tested and rewritten, they prove that the underlying physical media was undamaged, so they are restored.  That appears to be what you have.

Share this post


Link to post

Hi guys,

 

What do you think about these results? This drive went offline with errors when I was transferring a fair amount of data from one share to another. After some playing around with the cabling I replaced it with a new drive and got back up and running.

 

Since being back up and running I have precleared the drive twice. The drive was coming up with pending sectors with numbers 60, 63 and 69 from memory - I dont really know what that means...

 

After the first preclear the drive came up with - uncorrectable #69. After the second preclear that error disappeared. I ran an extended smart test and it completed without error. What do you think about the health of the drive?

 

Thanks in advance.

WDC_WD30EZRX-00DC0B0_WD-WMC1T0562149-20150924-1440.txt

Share this post


Link to post

 

After the first preclear the drive came up with - uncorrectable #69. After the second preclear that error disappeared. I ran an extended smart test and it completed without error. What do you think about the health of the drive?

 

Thanks in advance.

 

As user GK20 said once:

 

It shouldn't be just disappeared, "offline uncorrectable" error is similar to "reallocated sector" error, it is "offline" because those errors are detected by self-diagnostic facility in hard disk that will be triggered whenever disk is idle for certain period of time. sometime it will just randomly wandering around and reading sectors here and there.

 

The fact that they disappeared mean that after some data was written to those sectors (the second zeroing), the firmware tested the media surface and found it wasn't damaged at all, and no reallocation was needed.

 

The disk appears to be healthy.

Share this post


Link to post

 

The fact that they disappeared mean that after some data was written to those sectors (the second zeroing), the firmware tested the media surface and found it wasn't damaged at all, and no reallocation was needed.

 

The disk appears to be healthy.

 

Thanks gfjardim. I thought it would be right. I just thought it was odd that it took two preclears to resolve the issues. Cheers

Share this post


Link to post

Aww crud..  I start a parity check because I just upgraded to V6.1 and I was testing speeds and I had a couple drives with a current sector pending.  one went away..  but another disk got a bunch of read errors!  Will this disk now be red balled?  The parity check didn't get any errors.  but I got 113 read errors.

 

Sep 24 03:05:01 Tower kernel: sd 7:0:0:0: [sdf] tag#3 CDB: opcode=0x28 28 00 a5 a6 78 5f 00 05 40 00 (Drive related)
Sep 24 03:05:01 Tower kernel: blk_update_request: I/O error, dev sdf, sector 2779150872 (Errors)
Sep 24 03:05:01 Tower kernel: ata7: EH complete (Drive related)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150808 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150816 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150824 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150832 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150840 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150848 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150856 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150864 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150872 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150880 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150888 (Errors)
Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150896 (Errors)
.
.
.

 

What should I do?  Since the parity check didn't give any errors??

The disk is 5 years old.. but I have a couple that are 6 that are next in line to be replaced..

 

Jim

Share this post


Link to post
disk got a bunch of read errors!  Will this disk now be red balled?
Theoretically the drive accepted the writes to replace the data that could not be read. When a drive has read errors, unraid reads all the other drives and calculates what should have been in the location that had read errors, and issues a write command to put the data that couldn't be read back onto the drive. If the write fails, the drive is red balled (X'ed?) otherwise if the write returns success, the drive stays in service and the error count for that drive is incremented.

 

I'd disable spindown for that drive and run a long smart test, then get a smart report and post it.

 

If you want help deciding what drive needs to be replaced next, get smart reports on all your drives and post them.

Share this post


Link to post

disk got a bunch of read errors!  Will this disk now be red balled?
Theoretically the drive accepted the writes to replace the data that could not be read. When a drive has read errors, unraid reads all the other drives and calculates what should have been in the location that had read errors, and issues a write command to put the data that couldn't be read back onto the drive. If the write fails, the drive is red balled (X'ed?) otherwise if the write returns success, the drive stays in service and the error count for that drive is incremented.

 

I'd disable spindown for that drive and run a long smart test, then get a smart report and post it.

 

If you want help deciding what drive needs to be replaced next, get smart reports on all your drives and post them.

Thanks!  So if the drive's not redballed now it should be there on a restart, right?

Now does the long smart test have to be done with the array offline?

 

And how can I just *read* everything on the drive to see if I get the errors again? something like dd to /dev/null.

 

Jim

Share this post


Link to post
So if the drive's not redballed now it should be there on a restart, right?
Not correlated. Red ball happens the moment a write to the drive by unraid fails. Could happen at any time data is written, restart or not.

Now does the long smart test have to be done with the array offline? And how can I just *read* everything on the drive to see if I get the errors again? something like dd to /dev/null.

You can leave the array online, just make sure unraid doesn't try to spindown the drive during the test. A long smart test will read the entire drive, and after the test is done you will be able to see the results when you obtain a new smart report.

Share this post


Link to post

Just got a warning with my parity drive.

 

Warning [TOWER] - current pending sector is 16

 

I've also never encountered a " Offline_Uncorrectable " smart error as of yet.

 

Thoughts on the next course of action (will firstly swap in a new parity drive)

sdj_smart.txt

Share this post


Link to post

Just got a warning with my parity drive.

 

Warning [TOWER] - current pending sector is 16

 

I've also never encountered a " Offline_Uncorrectable " smart error as of yet.

 

Thoughts on the next course of action (will firstly swap in a new parity drive)

Good plan on the new drive. Then you can try to clear the pending sectors on the other drive by preclearing it.

Share this post


Link to post

Good plan on the new drive. Then you can try to clear the pending sectors on the other drive by preclearing it.

 

Thanks. I precleared the drive three times and see the pending sectors gone.

 

===========================================================================
** Changed attributes in files: /tmp/smart_start_sdq  /tmp/smart_finish_sdq
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   111     110            6        ok          37282784
             Spin_Up_Time =    98      94            0        ok          0
          Seek_Error_Rate =    47      46           30        near_thresh 2040135090721
           Power_On_Hours =    72      73            0        ok          24538
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =    96      99            0        ok          4
          High_Fly_Writes =    98      99            0        ok          2
  Airflow_Temperature_Cel =    63      76           45        near_thresh 37
         Load_Cycle_Count =    14      14            0        near_thresh 173170
      Temperature_Celsius =    37      24            0        ok          37
No SMART attributes are FAILING_NOW
16 sectors were pending re-allocation before the start of the preclear.
16 sectors were pending re-allocation after pre-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 3.
0 sectors were pending re-allocation after post-read in cycle 1 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 2 of 3.
0 sectors were pending re-allocation after post-read in cycle 2 of 3.
0 sectors were pending re-allocation after zero of disk in cycle 3 of 3.
0 sectors are pending re-allocation at the end of the preclear,
    a change of -16 in the number of sectors pending re-allocation.
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.

 

What worries is that I see this (attached smart report as well:

 

187 Reported_Uncorrect      0x0032   096   096   000    Old_age   Always       -       4

sdg.txt

Share this post


Link to post

Is this good or bad?

 

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

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

    a change of 576 in the number of sectors re-allocated.

That part is bad, but not necessarily fatal. Run another preclear cycle, and if you get more sectors reallocated, preclear it again until either the number stabilizes for _at least_ one additional preclear cycle, or the drive fails, one or the other.

 

I'm betting the drive will run out of re-allocatable sectors and fail. I don't like to see re-allocated sectors in the double digits, let alone over 4000+.  Looks like a failing drive to me.

Share this post


Link to post

So my first ever attempt at running pre clear - I have a bunch of older 3tb Seagte Drives I was hoping to reuse building my first array.  But am unsure what I should be looking for, if someone could explain to me what looks good and what doesn't I would be most grateful!  Perhaps an oh my god do not dare use that drive would help as well :-)

 

I have attached the logs for 7 drives that have now completed - a bunch more to go...

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdd
== ST3000DM001-1CH166   Z1F2YGHE
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:59:37 (119 MB/s)
== Last Cycle's Zeroing time   : 5:26:34 (153 MB/s)
== Last Cycle's Post Read Time : 12:47:19 (65 MB/s)
== Last Cycle's Total Time     : 25:15:13
==
== Total Elapsed Time 25:15:13
==
== Disk Start Temperature: 27C
==
== Current Disk Temperature: 30C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
          Seek_Error_Rate =    60      59           30        ok          124583539784
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =    48      57            0        ok          52
          High_Fly_Writes =    97      99            0        ok          3
  Airflow_Temperature_Cel =    70      73           45        near_thresh 30
      Temperature_Celsius =    30      27            0        ok          30
No SMART attributes are FAILING_NOW

24 sectors were pending re-allocation before the start of the preclear.
24 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,
    a change of -24 in the number of sectors pending re-allocation.
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. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdi
== ST3000DM001-9YN166   Z1F10KDK
== Disk /dev/sdi has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:37:22 (125 MB/s)
== Last Cycle's Zeroing time   : 5:16:58 (157 MB/s)
== Last Cycle's Post Read Time : 12:04:01 (69 MB/s)
== Last Cycle's Total Time     : 23:59:20
==
== Total Elapsed Time 23:59:20
==
== Disk Start Temperature: 27C
==
== Current Disk Temperature: 30C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdi  /tmp/smart_finish_sdi
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     114            6        ok          128415840
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =     1       1            0        near_thresh 512
          High_Fly_Writes =    82      85            0        ok          18
  Airflow_Temperature_Cel =    70      73           45        near_thresh 30
      Temperature_Celsius =    30      27            0        ok          30
   Current_Pending_Sector =    99     100            0        ok          168
    Offline_Uncorrectable =    99     100            0        ok          168
No SMART attributes are FAILING_NOW

120 sectors were pending re-allocation before the start of the preclear.
120 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.
168 sectors are pending re-allocation at the end of the preclear,
    a change of 48 in the number of sectors pending re-allocation.
5616 sectors had been re-allocated before the start of the preclear.
5648 sectors are re-allocated at the end of the preclear,
    a change of 32 in the number of sectors re-allocated. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdf
== ST3000DM001-9YN166   Z1F0YMDZ
== Disk /dev/sdf has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:32:33 (127 MB/s)
== Last Cycle's Zeroing time   : 5:17:36 (157 MB/s)
== Last Cycle's Post Read Time : 11:55:07 (69 MB/s)
== Last Cycle's Total Time     : 23:46:15
==
== Total Elapsed Time 23:46:15
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   117     114            6        ok          117901408
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
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. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdc
== ST3000DM001-9YN166   Z1F0GZE7
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:31:29 (127 MB/s)
== Last Cycle's Zeroing time   : 5:17:05 (157 MB/s)
== Last Cycle's Post Read Time : 12:10:31 (68 MB/s)
== Last Cycle's Total Time     : 24:00:05
==
== Total Elapsed Time 24:00:05
==
== Disk Start Temperature: 29C
==
== Current Disk Temperature: 31C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =    92     109            6        ok          172826854
    Reallocated_Sector_Ct =    99     100           36        ok          1312
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
       Reported_Uncorrect =     1      30            0        near_thresh 291
          High_Fly_Writes =    93      96            0        ok          7
  Airflow_Temperature_Cel =    69      71           45        near_thresh 31
      Temperature_Celsius =    31      29            0        ok          31
   Current_Pending_Sector =    98     100            0        ok          392
    Offline_Uncorrectable =    98     100            0        ok          392
No SMART attributes are FAILING_NOW

48 sectors were pending re-allocation before the start of the preclear.
48 sectors were pending re-allocation after pre-read in cycle 1 of 1.
112 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
392 sectors are pending re-allocation at the end of the preclear,
    a change of 344 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
1312 sectors are re-allocated at the end of the preclear,
    a change of 1312 in the number of sectors re-allocated. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdb
== ST3000DM001-9YN166   Z1F12629
== Disk /dev/sdb has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:36:18 (126 MB/s)
== Last Cycle's Zeroing time   : 5:17:04 (157 MB/s)
== Last Cycle's Post Read Time : 11:56:05 (69 MB/s)
== Last Cycle's Total Time     : 23:50:28
==
== Total Elapsed Time 23:50:28
==
== Disk Start Temperature: 27C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** 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 =   109     117            6        ok          168592136
    Reallocated_Sector_Ct =    97      98           36        ok          4288
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
          High_Fly_Writes =    93      99            0        ok          7
  Airflow_Temperature_Cel =    71      73           45        ok          29
      Temperature_Celsius =    29      27            0        ok          29
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 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.
3712 sectors had been re-allocated before the start of the preclear.
4288 sectors are re-allocated at the end of the preclear,
    a change of 576 in the number of sectors re-allocated. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sdh
== ST3000DM001-9YN166   Z1F10QCX
== Disk /dev/sdh has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:32:28 (127 MB/s)
== Last Cycle's Zeroing time   : 5:15:17 (158 MB/s)
== Last Cycle's Post Read Time : 11:54:04 (70 MB/s)
== Last Cycle's Total Time     : 23:42:48
==
== Total Elapsed Time 23:42:48
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 30C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   119     118            6        ok          221764640
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    70      72           45        near_thresh 30
      Temperature_Celsius =    30      28            0        ok          30
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 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. 
============================================================================

 

========================================================================1.15
== invoked as: ./preclear_disk.sh /dev/sde
== ST3000DM001-1CH166   Z1F31YMA
== Disk /dev/sde has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 6:45:04 (123 MB/s)
== Last Cycle's Zeroing time   : 5:16:11 (158 MB/s)
== Last Cycle's Post Read Time : 12:11:24 (68 MB/s)
== Last Cycle's Total Time     : 24:13:46
==
== Total Elapsed Time 24:13:46
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 29C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sde  /tmp/smart_finish_sde
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   118     116            6        ok          172706560
          Seek_Error_Rate =    54      54           30        near_thresh 575556739148
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    71      72           45        ok          29
      Temperature_Celsius =    29      28            0        ok          29
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 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. 
============================================================================

 

Thanks

 

Stuart

Share this post


Link to post

So would I be right in thinking - only the 4 drives with (after the scan) zero pending and zero actual re-allocation were worthy of being resused?

 

Thanks

 

Stuart

Share this post


Link to post

So would I be right in thinking - only the 4 drives with (after the scan) zero pending and zero actual re-allocation were worthy of being resused?

the zero pending is important and you should not use a drive where that value does not go back to zero after a pre-clear.

 

The zero reallocation is good but not as important.  As long as the value is small and is stable (i.e. not increasing) then the drive should be OK to use..

Share this post


Link to post

I ran a preclear on a drive I just replaced and do not trust in an attempt to understand the preclear results so I can test all drives I use moving forward.

 

Can you help me understand these results? Id this good or bad and what tells me that

 

 

========================================================================1.15
== invoked as: ./preclear_disk.sh -A /dev/sdd
== WDCWD5000AAKS-00YGA0   WD-WCAS80792713
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 1000448 Bytes
== Last Cycle's Pre Read Time  : 7:20:48 (18 MB/s)
== Last Cycle's Zeroing time   : 2:13:43 (62 MB/s)
== Last Cycle's Post Read Time : 20:00:24 (6 MB/s)
== Last Cycle's Total Time     : 29:35:54
==
== Total Elapsed Time 29:35:54
==
== Disk Start Temperature: 41C
==
== Current Disk Temperature: -->41<--C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   199     200           51        ok          180125
    Reallocated_Sector_Ct =   199     200          140        ok          1
           Power_On_Hours =    10      10            0        near_thresh 66111
  Reallocated_Event_Count =   199     200            0        ok          1
   Current_Pending_Sector =   200     196            0        ok          9
    Multi_Zone_Error_Rate =     1       1           51        FAILING_NOW 22423

*** Failing SMART Attributes in /tmp/smart_finish_sdd *** 
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
200 Multi_Zone_Error_Rate   0x0008   001   001   051    Old_age   Offline  FAILING_NOW 22423

327 sectors were pending re-allocation before the start of the preclear.
331 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.
9 sectors are pending re-allocation at the end of the preclear,
    a change of -318 in the number of sectors pending re-allocation.
0 sectors had been re-allocated before the start of the preclear.
1 sector is re-allocated at the end of the preclear,
    a change of 1 in the number of sectors re-allocated. 
============================================================================

 

 

Share this post


Link to post

Join the conversation

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

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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