Re: [smartmontools-support] Selftests complete without errors, but ATA error count is 24539

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I have no idea what this vendor-specific error is.  For example it could 
be provoked by bad communication between the drive and the disk 
controller.  But as a first step, since IBM makes both the computer and 
the drive, ask IBM to either replace the drive or "diagnose the problem". 
The latter probably means 'swap the laptop's motherboard'.

Cheers,
 	Bruce

   But you should ask IBM 
to replace the drive

On Sun, 25 Jun 2006 re2823@Safe-mail.net wrote:

> Hi,
>
> The 2.5 inch Travelstar drive in my IBM Thinkpad started making
> repetetive clunking noises yesterday, and at the same time, the
> following appeared in the syslog:
>
> Jun 24 19:11:12 t21eh kernel: [17184187.648000] hda: dma_timer_expiry: dma status == 0x20
> Jun 24 19:11:12 t21eh kernel: [17184187.648000] hda: DMA timeout retry
> Jun 24 19:11:12 t21eh kernel: [17184187.648000] hda: timeout waiting for DMA
> Jun 24 19:11:12 t21eh kernel: [17184192.652000] hda: status timeout: status=0xd0 { Busy }
> Jun 24 19:11:12 t21eh kernel: [17184192.652000] ide: failed opcode was: unknown
> Jun 24 19:11:12 t21eh kernel: [17184192.652000] hda: drive not ready for command
> Jun 24 19:11:12 t21eh kernel: [17184192.652000] rt2500MlmeEnqueue full, msg dropped and may corrupt MLME
> Jun 24 19:11:13 t21eh kernel: [17184193.516000] ide0: reset: success
> Jun 24 19:12:32 t21eh kernel: [17184272.452000] hda: dma_timer_expiry: dma status == 0x21
>
> I've tried a few short tests and one long selftest using smartctl,
> and they have all completed without error, however I've noticed
> that according to the output, the "ATA error count" is 24539,
> which seems very high to me.
>
> Is is possible that either a kernel bug or driver/dma bug could
> push the error count up so high (while, in fact, the drive is
> still OK)? I ask because the simultaneous rt2500 entry in the
> syslog is for a wireless card with known driver problems.
>
> I've read some of Bruce's past posts about how SMART only catches
> 2/3 (two thirds) of hard drive failures - could this be somewhere
> in the other third?
>
> Here's the full output in case it helps:
>
> smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Model Family: IBM Travelstar 48GH, 30GN, and 15GN family
> Device Model: IC25N020ATDA04-0
> Serial Number: 63A63339885
> Firmware Version: DA3OA76A
> User Capacity: 20,003,880,960 bytes
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: 5
> ATA Standard is: ATA/ATAPI-5 T13 1321D revision 3
> Local Time is: Sun Jun 25 10:02:41 2006 BST
> 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: ( 645) 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: ( 27) 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
>  1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0
>  2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
>  3 Spin_Up_Time 0x0007 129 129 033 Pre-fail Always - 1
>  4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 1798
>  5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
>  7 Seek_Error_Rate 0x000b 098 098 067 Pre-fail Always - 2
>  8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
>  9 Power_On_Hours 0x0012 075 075 000 Old_age Always - 11225
> 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1734
> 191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
> 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 93
> 193 Load_Cycle_Count 0x0012 049 049 000 Old_age Always - 517058
> 194 Temperature_Celsius 0x0002 122 122 000 Old_age Always - 45 (Lifetime Min/Max 16/69)
> 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 3
> 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
> ATA Error Count: 24539 (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 24539 occurred at disk power-on lifetime: 11215 hours (467 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
>  -- -- -- -- -- -- --
>  01 51 01 15 e0 fe af
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
>  -- -- -- -- -- -- -- -- ---------------- --------------------
>  fe a2 01 15 e0 fe ef 02 00:29:41.000 [VENDOR SPECIFIC]
>  fe a2 01 14 e0 fe ef 02 00:29:41.000 [VENDOR SPECIFIC]
>  fe a2 01 13 e0 fe ef 02 00:29:41.000 [VENDOR SPECIFIC]
>  fe a2 01 12 e0 fe ef 02 00:29:40.900 [VENDOR SPECIFIC]
>  fe a2 01 11 e0 fe ef 02 00:29:40.900 [VENDOR SPECIFIC]
>
> Error 24538 occurred at disk power-on lifetime: 11215 hours (467 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
>  -- -- -- -- -- -- --
>  01 51 01 15 e0 fe af
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
>  -- -- -- -- -- -- -- -- ---------------- --------------------
>  fe a2 01 15 e0 fe ef 02 00:03:03.000 [VENDOR SPECIFIC]
>  fe a2 01 14 e0 fe ef 02 00:03:03.000 [VENDOR SPECIFIC]
>  fe a2 01 13 e0 fe ef 02 00:03:03.000 [VENDOR SPECIFIC]
>  fe a2 01 12 e0 fe ef 02 00:03:03.000 [VENDOR SPECIFIC]
>  fe a2 01 11 e0 fe ef 02 00:03:03.000 [VENDOR SPECIFIC]
>
> Error 24537 occurred at disk power-on lifetime: 11215 hours (467 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
>  -- -- -- -- -- -- --
>  01 51 01 15 e0 fe af
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
>  -- -- -- -- -- -- -- -- ---------------- --------------------
>  fe a2 01 15 e0 fe ef 02 01:14:38.200 [VENDOR SPECIFIC]
>  fe a2 01 14 e0 fe ef 02 01:14:38.200 [VENDOR SPECIFIC]
>  fe a2 01 13 e0 fe ef 02 01:14:38.200 [VENDOR SPECIFIC]
>  fe a2 01 12 e0 fe ef 02 01:14:38.200 [VENDOR SPECIFIC]
>  fe a2 01 11 e0 fe ef 02 01:14:38.200 [VENDOR SPECIFIC]
>
> Error 24536 occurred at disk power-on lifetime: 11215 hours (467 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
>  -- -- -- -- -- -- --
>  01 51 01 15 e0 fe af
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
>  -- -- -- -- -- -- -- -- ---------------- --------------------
>  fe a2 01 15 e0 fe ef 02 01:13:03.900 [VENDOR SPECIFIC]
>  fe a2 01 14 e0 fe ef 02 01:13:03.900 [VENDOR SPECIFIC]
>  fe a2 01 13 e0 fe ef 02 01:13:03.900 [VENDOR SPECIFIC]
>  fe a2 01 12 e0 fe ef 02 01:13:03.900 [VENDOR SPECIFIC]
>  fe a2 01 11 e0 fe ef 02 01:13:03.900 [VENDOR SPECIFIC]
>
> Error 24535 occurred at disk power-on lifetime: 7928 hours (330 days + 8 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 70 86 ac e2 Error: IDNF at LBA = 0x02ac8670 = 44861040
>
>  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 03 01 70 86 ac e2 00 00:00:15.400 READ SECTOR(S)
>  20 03 01 f0 d4 eb e3 00 00:00:15.400 READ SECTOR(S)
>  20 03 01 70 23 2b e5 00 00:00:15.300 READ SECTOR(S)
>  20 03 01 f0 71 6a e6 00 00:00:15.300 READ SECTOR(S)
>  20 03 01 70 c0 a9 e7 00 00:00:15.200 READ SECTOR(S)
>
> 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% 11223 -
> # 2 Short offline Completed without error 00% 11223 -
> # 3 Short offline Completed without error 00% 11215 -
> # 4 Short offline Completed without error 00% 11214 -
> # 5 Short offline Completed without error 00% 11214 -
>
> Device does not support Selective Self Tests/Logging
>
>
> Thank you for any help you can offer,
>
> Jaime :-)
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Smartmontools-support mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>

Re: [smartmontools-support] Selftests complete without errors, but ATA error count is 24539

Disk Inspection and Monitoring

Re: [smartmontools-support] Selftests complete without errors, but ATA error count is 24539