View previous topic :: View next topic |
Author |
Message |
SloMoFG n00b
Joined: 30 Sep 2004 Posts: 3
|
Posted: Tue Feb 08, 2005 11:27 am Post subject: smartctl reporting errors - how to interpret output? |
|
|
I've had several read errors with my drive in the past days. Trying to find out whats wrong I emerged and ran 'smartctl' from 'smartmontools'. Running 'smartctl' with 'smartctl -a /dev/hda' it gives the attached output.
Now, I've got several questions:
How to interpret lines like 'Error: UNC at LBA = 0x005e9007 = 6197255'? What does the abbreviation 'UNC' mean?
Is there a problem with my hard drive or might there be a problem with my IDE controlle (I've got one of those unfamous VT82C686B)? [I ask this beacause all the SMART attributes are in range predicting no failure.]
Thanks in advance.
Martin
Code: |
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: Maxtor 6Y120L0
Serial Number: Y40GCLQE
Firmware Version: YAR41VW0
User Capacity: 122,942,324,736 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: Tue Feb 8 12:18:03 2005 CET
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: ( 242) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 63) 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 202 202 063 Pre-fail Always - 14438
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 869
5 Reallocated_Sector_Ct 0x0033 253 250 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 248 187 Pre-fail Always - 43222
9 Power_On_Minutes 0x0032 246 246 000 Old_age Always - 256h+02m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 757
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 253 253 000 Old_age Always - 44
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 1441
196 Reallocated_Event_Count 0x0008 232 232 000 Old_age Offline - 21
197 Current_Pending_Sector 0x0008 253 250 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 214 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 182 105 000 Old_age Offline - 93
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 - 0
202 TA_Increase_Count 0x000a 253 246 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 0
204 Shock_Count_Write_Opern 0x000a 253 249 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 199 193 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
SMART Error Log Version: 1
Warning: ATA error count 177 inconsistent with error log pointer 5
ATA Error Count: 177 (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 177 occurred at disk power-on lifetime: 2249 hours (93 days + 17 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 51 08 07 90 5e e0 Error: UNC at LBA = 0x005e9007 = 6197255
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 d8 08 07 90 5e e0 00 00:18:49.104 READ MULTIPLE
c8 d8 08 07 90 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 ff 8f 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 f7 8f 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 ef 8f 5e e0 00 00:18:48.032 READ DMA
Error 176 occurred at disk power-on lifetime: 2249 hours (93 days + 17 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 51 06 07 90 5e e0 Error: UNC 6 sectors at LBA = 0x005e9007 = 6197255
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 d8 08 07 90 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 ff 8f 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 f7 8f 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 ef 8f 5e e0 00 00:18:48.032 READ DMA
c8 d8 08 e7 8f 5e e0 00 00:18:48.032 READ DMA
Error 175 occurred at disk power-on lifetime: 1625 hours (67 days + 17 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 51 3c 80 98 b0 e3 Error: UNC 60 sectors at LBA = 0x03b09880 = 61905024
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 d8 40 80 98 b0 e3 00 00:56:30.640 READ DMA
c8 d8 40 40 98 b0 e3 00 00:56:30.640 READ DMA
c8 d8 40 00 98 b0 e3 00 00:56:30.640 READ DMA
c8 d8 40 c0 97 b0 e3 00 00:56:30.640 READ DMA
c8 d8 40 80 97 b0 e3 00 00:56:30.640 READ DMA
Error 174 occurred at disk power-on lifetime: 1625 hours (67 days + 17 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 51 26 40 97 b0 e3 Error: UNC 38 sectors at LBA = 0x03b09740 = 61904704
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 d8 40 40 97 b0 e3 00 00:56:29.616 READ DMA
c8 d8 40 00 97 b0 e3 00 00:56:29.616 READ DMA
c8 d8 40 c0 96 b0 e3 00 00:56:29.616 READ DMA
c8 d8 40 80 96 b0 e3 00 00:56:29.616 READ DMA
c8 d8 40 40 96 b0 e3 00 00:56:29.616 READ DMA
Error 173 occurred at disk power-on lifetime: 1625 hours (67 days + 17 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 51 37 c0 62 b0 e3 Error: UNC 55 sectors at LBA = 0x03b062c0 = 61891264
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 d8 40 c0 62 b0 e3 00 00:56:28.464 READ DMA
c8 d8 40 80 62 b0 e3 00 00:56:28.464 READ DMA
c8 d8 40 40 62 b0 e3 00 00:56:28.464 READ DMA
c8 d8 40 00 62 b0 e3 00 00:56:28.448 READ DMA
c8 d8 40 c0 61 b0 e3 00 00:56:28.448 READ DMA
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2287 -
# 2 Short offline Completed without error 00% 2286 -
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.
|
|
|
Back to top |
|
|
Raistlin l33t
Joined: 17 May 2004 Posts: 691 Location: Boston, MA
|
Posted: Tue Feb 08, 2005 11:44 am Post subject: Re: smartctl reporting errors - how to interpret output? |
|
|
SloMoFG wrote: | ...What does the abbreviation 'UNC' mean?... |
manpage of smarctl
cheers, R _________________ Zwei Was Eins Initially
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." |
|
Back to top |
|
|
SloMoFG n00b
Joined: 30 Sep 2004 Posts: 3
|
Posted: Tue Feb 08, 2005 12:15 pm Post subject: Re: smartctl reporting errors - how to interpret output? |
|
|
Raistlin wrote: | SloMoFG wrote: | ...What does the abbreviation 'UNC' mean?... |
manpage of smarctl
cheers, R |
Thanks. I looked at the man page but obviously not as carefully as I should. Nevertheless, are such things "normal" (because there are still "only" 177 such errors) or is it time for me to buy a new harddisk?
Thanks once again,
Martin |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|