Messages in this thread | | | Date | Sat, 10 Jun 2006 06:59:07 -0400 (EDT) | From | Justin Piszcz <> | Subject | Re: The Death and Diagnosis of a Dying Hard Drive - Is S.M.A.R.T. useful? |
| |
# smartctl -d ata -H /dev/sdc smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED
#
The --all output below:
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION === Model Family: Maxtor DiamondMax 10 family Device Model: Maxtor 6B250S0 Serial Number: /* commented out */ Firmware Version: BANC1B70 User Capacity: 251,000,193,024 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is: Sat Jun 10 06:58:29 2006 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: (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: (2283) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 109) minutes.
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 3 Spin_Up_Time 0x0027 184 182 063 Pre-fail Always - 25693 4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 91 5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0 7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0 8 Seek_Time_Performance 0x0027 252 237 187 Pre-fail Always - 56515 9 Power_On_Minutes 0x0032 218 218 000 Old_age Always - 103h+42m 10 Spin_Retry_Count 0x002b 249 248 157 Pre-fail Always - 4 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 253 253 000 Old_age Always - 191 192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0 194 Temperature_Celsius 0x0032 038 253 000 Old_age Always - 32 195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 312 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0 197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0 198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 2 202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0 203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 0 204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0 207 Spin_High_Current 0x002a 249 248 000 Old_age Always - 4 208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0 209 Offline_Seek_Performnce 0x0024 241 241 000 Old_age Offline - 152 210 Unknown_Attribute 0x0032 253 252 000 Old_age Always - 0 211 Unknown_Attribute 0x0032 253 252 000 Old_age Always - 0 212 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
SMART Error Log Version: 1 ATA Error Count: 252 (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 252 occurred at disk power-on lifetime: 11354 hours (473 days + 2 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 -- -- -- -- -- -- -- 78 00 08 b0 19 eb e0
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 08 b0 19 eb e0 00 01:39:12.107 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:10.649 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:09.191 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:07.716 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:06.258 NOP [Abort queued commands]
Error 251 occurred at disk power-on lifetime: 11354 hours (473 days + 2 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 -- -- -- -- -- -- -- 78 00 08 b0 19 eb e0
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 08 b0 19 eb e0 00 01:39:10.649 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:09.191 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:07.716 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:06.258 NOP [Abort queued commands] 00 00 08 b0 19 eb e0 00 01:39:04.791 NOP [Abort queued commands]
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% 12117 - # 2 Short offline Completed without error 00% 12116 - # 3 Extended offline Completed without error 00% 12099 - # 4 Short offline Completed without error 00% 12097 - # 5 Short offline Completed without error 00% 12090 - # 6 Short offline Completed without error 00% 12044 - # 7 Short offline Completed without error 00% 12020 - # 8 Short offline Completed without error 00% 11996 - # 9 Short offline Completed without error 00% 11972 - #10 Short offline Completed without error 00% 11949 - #11 Short offline Completed without error 00% 11924 - #12 Short offline Completed without error 00% 11900 - #13 Short offline Completed without error 00% 11877 - #14 Short offline Completed without error 00% 11853 - #15 Short offline Completed without error 00% 11829 - #16 Short offline Completed without error 00% 11806 - #17 Short offline Completed without error 00% 11782 - #18 Short offline Completed without error 00% 11758 - #19 Short offline Completed without error 00% 11734 - #20 Short offline Completed without error 00% 11711 - #21 Short offline Completed without error 00% 11687 -
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.
On Sat, 10 Jun 2006, Jan-Benedict Glaw wrote:
> On Sat, 2006-06-10 06:23:32 -0400, Justin Piszcz <jpiszcz@lucidpixels.com> wrote: >> SUMMARY: >> I pose the following question in the subject, as over the years running >> smartd and having failed disks, I have always first been alerted of bad >> sectors and such through dmesg or logcheck. Even with a bad disk I >> currently have, smartd does not pickup any errors, except those with the >> kernel writes to syslog. > > What do > > smartctl -H > smartctl --all > > tell you? > > MfG, JBG > > -- > Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _ > "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O > fÃŒr einen Freien Staat voll Freier BÃŒrger" | im Internet! | im Irak! O O O > ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); > | |