November 10, 201213 yr This is the preclear finish file. I don't see anywhere that it says the disk was cleared but I can't tellt hat it is failing either. Can you guys comment? Disk: /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3750640AS Serial Number: 3QD0RQD1 Firmware Version: 3.AAE User Capacity: 750,155,292,160 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Nov 9 15:57:36 2012 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) 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: ( 202) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 086 006 Pre-fail Always - 212824034 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 936 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 088 060 030 Pre-fail Always - 675414168 9 Power_On_Hours 0x0032 057 057 000 Old_age Always - 38473 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 243 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 052 051 045 Old_age Always - 48 (Min/Max 38/49) 194 Temperature_Celsius 0x0022 048 049 000 Old_age Always - 48 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 059 053 000 Old_age Always - 217344359 197 Current_Pending_Sector 0x0012 094 093 000 Old_age Always - 141 198 Offline_Uncorrectable 0x0010 094 093 000 Old_age Offline - 141 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 94 (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 94 occurred at disk power-on lifetime: 29996 hours (1249 days + 20 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 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 04:05:06.024 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 04:05:05.799 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 04:05:05.735 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 04:05:03.655 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 04:05:03.596 SET MAX ADDRESS EXT Error 93 occurred at disk power-on lifetime: 29996 hours (1249 days + 20 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 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 04:04:58.326 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 04:04:58.326 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 04:04:58.326 SET MAX ADDRESS EXT 27 00 01 ef 66 54 e0 00 04:05:03.655 READ NATIVE MAX ADDRESS EXT 29 00 01 ef 66 54 e0 00 04:05:03.596 READ MULTIPLE EXT Error 92 occurred at disk power-on lifetime: 29993 hours (1249 days + 17 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 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 01:35:25.972 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 01:35:25.911 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 01:35:22.233 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 01:35:22.205 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 01:35:22.205 SET MAX ADDRESS EXT Error 91 occurred at disk power-on lifetime: 29993 hours (1249 days + 17 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 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 01:35:25.972 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 01:35:25.911 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 01:35:22.233 SET MAX ADDRESS EXT 27 00 01 ef 66 54 e0 00 01:35:22.205 READ NATIVE MAX ADDRESS EXT 29 00 01 ef 66 54 e0 00 01:35:22.205 READ MULTIPLE EXT Error 90 occurred at disk power-on lifetime: 29983 hours (1249 days + 7 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 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 07:07:17.975 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 07:07:24.857 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 07:07:24.798 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 07:07:24.573 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 07:07:24.509 SET MAX ADDRESS 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% 25 - 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.
November 10, 201213 yr Author This is the preclear rpt file. Here it says it was cleared, but I don't understand what it means that so many sectors we pending re-allocation. Haven't had a drive do that yet. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST3750640AS 3QD0RQD1 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 4:00:36 (51 MB/s) == Last Cycle's Zeroing time : 3:27:34 (60 MB/s) == Last Cycle's Post Read Time : 10:01:07 (20 MB/s) == Last Cycle's Total Time : 17:30:21 == == Total Elapsed Time 17:30:21 == == Disk Start Temperature: 41C == == Current Disk Temperature: -->48<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 88 87 30 ok 675414168 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 52 59 45 near_thresh 48 Temperature_Celsius = 48 41 0 ok 48 Hardware_ECC_Recovered = 59 75 0 ok 217344359 Current_Pending_Sector = 94 93 0 ok 141 Offline_Uncorrectable = 94 93 0 ok 141 No SMART attributes are FAILING_NOW 155 sectors were pending re-allocation before the start of the preclear. 155 sectors were pending re-allocation after pre-read in cycle 1 of 1. 141 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 141 sectors are pending re-allocation at the end of the preclear, a change of -14 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. ============================================================================
November 10, 201213 yr I'd run another preclear cycle and see what the results are. My gut instinct says the drive is failing sooner rather than later. I definitely wouldn't trust it in an array until you get the pending sectors down to zero, and maybe not even then. All drives eventually fail, it's just a matter of when.
November 10, 201213 yr Author So what is important to look at here? Pending sectors? Could you explain what that means as well please? Thanks
November 11, 201213 yr Author Ran the preclear again and got same results. The drive passed the preclear. All numbers were same except now all of them say 141 sectors were pending re-allocation were as in the first test the first two lines said 151 were pending. At the end it says 0 had been re-allocated... What does this mean? Should I throughout the drive? I thought the most important part to pay attention was whether the drive passed preclear or not.
November 11, 201213 yr Ran the preclear again and got same results. The drive passed the preclear. All numbers were same except now all of them say 141 sectors were pending re-allocation were as in the first test the first two lines said 151 were pending. At the end it says 0 had been re-allocated... What does this mean? Should I throughout the drive? I thought the most important part to pay attention was whether the drive passed preclear or not. Don't use the drive in unRAID. RMA it. No drive should ever have sectors marked as pending after a preclear. They should all have been re-allocated when the disk was written to. The only way your issue can happen is if they are again un-readable in the post-read phase. Joe L.
Archived
This topic is now archived and is closed to further replies.