From: Thane S. <ts...@au...> - 2006-09-07 13:12:40
|
I have a drive with some historical errors, though it passes self-tests now. I'm wondering about the value of the Hardware_ECC_Recovered attribute in predicting failure. The report follows, but I'm wondering about the raw value of this attribute. 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 201917 Does a raw value this high mean anything? T smartctl version 5.37 [i686-mingw32-xp] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: QUANTUM FIREBALLlct20 series Device Model: QUANTUM FIREBALLlct20 20 Serial Number: 352033221940 Firmware Version: APL.0900 User Capacity: 20,416,757,760 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 5 ATA Standard is: ATA/ATAPI-5 T13 1321D revision 1 Local Time is: Thu Sep 07 12:38:32 2006 SMART support is: Available - device has SMART capability. Enabled status cached by OS, trying SMART RETURN STATUS cmd. 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: (0x80) Offline data collection activity was never started. 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: ( 51) seconds. Offline data collection capabilities: (0x1b) 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. No 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. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 25) minutes. SMART Attributes Data Structure revision number: 11 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0029 100 253 020 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 081 079 020 Pre-fail Always - 2431 4 Start_Stop_Count 0x0032 095 095 008 Old_age Always - 3503 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 023 Pre-fail Always - 0 9 Power_On_Hours 0x0012 077 077 001 Old_age Always - 15720 10 Spin_Retry_Count 0x0026 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 098 098 008 Old_age Always - 1811 13 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail Always - 0 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 201917 196 Reallocated_Event_Count 0x0010 100 100 020 Old_age Offline - 0 197 Current_Pending_Sector 0x0032 100 100 020 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x001a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 3702 (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 3702 occurred at disk power-on lifetime: 8030 hours (334 days + 14 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 d1 01 00 3a 68 e0 Error: UNC at LBA = 0x00683a00 = 6830592 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 20 ff 01 00 3a 68 e0 00 49d+16:58:19.426 READ SECTOR(S) 91 ff 3f 01 00 00 ae 02 49d+16:58:19.327 INITIALIZE DEVICE PARAMETERS [OBS-6] 10 ff 01 01 00 00 a0 00 49d+16:58:19.318 RECALIBRATE [OBS-4] ff ff ff ff ff ff ff ff 49d+16:58:19.120 [VENDOR SPECIFIC] c8 ff 01 00 3a 68 e0 00 49d+16:58:15.280 READ DMA Error 3701 occurred at disk power-on lifetime: 8030 hours (334 days + 14 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 d1 01 00 3a 68 e0 Error: UNC 1 sectors at LBA = 0x00683a00 = 6830592 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 ff 01 00 3a 68 e0 00 49d+16:58:15.280 READ DMA ca ff 1e e0 39 68 e0 00 49d+16:58:15.280 WRITE DMA c8 ff 01 ff 39 68 e0 00 49d+16:58:15.280 READ DMA ca ff 16 b2 7e a3 e0 00 49d+16:58:15.279 WRITE DMA ca ff 11 4d 7b 98 e0 00 49d+16:58:15.279 WRITE DMA Error 3700 occurred at disk power-on lifetime: 8030 hours (334 days + 14 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 d9 06 ff 39 68 e0 Error: UNC 6 sectors at LBA = 0x006839ff = 6830591 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 ff 08 fe 39 68 e0 00 49d+16:58:07.375 READ DMA ca ff 0b 8a a4 66 e0 00 49d+16:58:07.360 WRITE DMA c8 ff 08 c6 7e a3 e0 00 49d+16:58:07.335 READ DMA c8 ff 06 c0 7e a3 e0 00 49d+16:58:07.334 READ DMA ca ff 13 ae f1 96 e0 00 49d+16:58:07.286 WRITE DMA Error 3699 occurred at disk power-on lifetime: 8011 hours (333 days + 19 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 d1 08 fe 39 68 e0 Error: UNC at LBA = 0x006839fe = 6830590 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c4 d1 08 fe 39 68 e0 00 00:02:02.107 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:58.457 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:54.808 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:51.159 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:47.514 READ MULTIPLE Error 3698 occurred at disk power-on lifetime: 8011 hours (333 days + 19 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 d1 08 fe 39 68 e0 Error: UNC at LBA = 0x006839fe = 6830590 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c4 d1 08 fe 39 68 e0 00 00:01:58.457 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:54.808 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:51.159 READ MULTIPLE c4 d1 08 fe 39 68 e0 00 00:01:47.514 READ MULTIPLE c4 d1 08 f6 39 68 e0 00 00:01:47.499 READ MULTIPLE SMART Self-test log structure revision number 0 Warning: ATA Specification requires 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% 15702 - # 2 Abort offline test Aborted by host 40% 5816 - # 3 Extended offline Completed without error 00% 0 - # 4 Short offline Completed without error 00% 0 - Device does not support Selective Self Tests/Logging |
From: Bruce A. <ba...@gr...> - 2006-09-07 14:38:20
|
On Thu, 7 Sep 2006, Thane Sherrington wrote: > I have a drive with some historical errors, though it passes > self-tests now. I'm wondering about the value of the > Hardware_ECC_Recovered attribute in predicting failure. The report > follows, but I'm wondering about the raw value of this attribute. > > 195 > Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always > - 201917 > > Does a raw value this high mean anything? No. Bruce |
From: Thane S. <ts...@au...> - 2006-09-07 14:57:18
|
At 11:38 AM 07/09/2006, Bruce Allen wrote: >On Thu, 7 Sep 2006, Thane Sherrington wrote: > >>I have a drive with some historical errors, though it passes >>self-tests now. I'm wondering about the value of the >>Hardware_ECC_Recovered attribute in predicting failure. The report >>follows, but I'm wondering about the raw value of this attribute. >> >>195 >>Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always >> - 201917 >> >>Does a raw value this high mean anything? > >No. Perfect, that's good to know. T |
From: Erwan V. <er...@se...> - 2006-09-07 14:44:18
|
Bruce Allen wrote: >> 195 >> Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always >> - 201917 >> >> Does a raw value this high mean anything? >> Bruce I'm usually facing some users asking me the same question. Maybe we could hide this field which is confusing and display it only when a flag is set ? Like smartctl --expert or whatever WDYT ? |
From: Serguei M. <mi...@ci...> - 2006-09-07 16:12:50
|
On Thursday 07 September 2006 07:44, Erwan Velu wrote: > Bruce Allen wrote: > >> 195 > >> Hardware_ECC_Recovered 0x001a 100 100 000 > >> Old_age Always - 201917 > >> > >> Does a raw value this high mean anything? > > Bruce I'm usually facing some users asking me the same > question. Maybe we could hide this field which is confusing > and display it only when a flag is set ? > Like smartctl --expert or whatever Well, if some attributes confuse people, why not to explain what are all these data for? It is very difficult to find an information about such attributes because any googling with these keywords just show a lot of pages with smartctl outputs. Do you have any reference, manual, etc., which describes all attributes and explain what they mean? |
From: Volker K. <lis...@pa...> - 2006-09-07 21:10:54
|
> Well, if some attributes confuse people, why not to explain > what are all these data for? It is very difficult to find an > information about such attributes because any googling with > these keywords just show a lot of pages with smartctl outputs. > Do you have any reference, manual, etc., which describes all > attributes and explain what they mean? Yes, I think that's true, I've been thinking the same for some time. Would a wiki best address this documentation need? More traditional answers would include "FAQ". I would volunteer some time. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |