Sign in with
Sign up | Sign in
Your question

SMART Data wrong?

Last response: in Storage
Share
December 9, 2012 3:52:27 AM

Using smartctl, it tells me that my hard drive has only been powered for 10.8 hours, however I know it has definitely been running for more than 2 years. Could this be a sign of it dying?

More about : smart data wrong

a c 288 G Storage
December 9, 2012 4:09:31 AM

It sounds like an interpretation problem.

SMART raw values are always integers. Some drives report Power On Time in hours, others in seconds. I suspect that smartctl may be consulting its database of models and misinterpreting an hours count as seconds or something else.

Could we see your SMART data?

Do you have a Fujitsu / Toshiba / Hitachi drive?
m
0
l
December 9, 2012 4:58:00 AM


...i just saw that an error that occurred had a time stamp that makes more sense as far as age is concerned...im more confused now :p 
its an old 20 gig drive also that i use for important backups:



Here is the result of smartctl -a /dev/sdb




smartctl 5.40 2010-03-16 r3077 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 60 family
Device Model: Maxtor 5T020H2
Serial Number: T2LKYN1C
Firmware Version: TAH71DP0
User Capacity: 20,000,000,000 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 0
Local Time is: Sat Dec 8 21:46:26 2012 PST
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: ( 19) The self-test routine was aborted by
the host.
Total time to complete Offline
data collection: ( 30) 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: ( 14) 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 0x000a 253 252 000 Old_age Always - 100
3 Spin_Up_Time 0x0027 224 218 063 Pre-fail Always - 8036
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 819
5 Reallocated_Sector_Ct 0x0033 226 155 063 Pre-fail Always - 68
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 243 187 Pre-fail Always - 53503
9 Power_On_Minutes 0x0032 152 152 000 Old_age Always - 259h+59m
10 Spin_Retry_Count 0x002b 248 241 223 Pre-fail Always - 3
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 251 251 000 Old_age Always - 801
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 226 040 000 Old_age Offline - 27
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 - 184
202 Data_Address_Mark_Errs 0x000a 253 214 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 212 180 Pre-fail Always - 365
204 Soft_ECC_Correction 0x000a 253 249 000 Old_age Always - 0
205 Thermal_Asperity_Rate 0x000a 253 241 000 Old_age Always - 0
207 Spin_High_Current 0x002a 252 247 000 Old_age Always - 1
208 Spin_Buzz 0x002a 253 249 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 205 200 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 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 31012 inconsistent with error log pointer 5

ATA Error Count: 31012 (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 31012 occurred at disk power-on lifetime: 32259 hours (1344 days + 3 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 71 df de 04 f1 Error: UNC 113 sectors at LBA = 0x0104dedf = 17096415

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 00 00 df de 04 f1 08 01:15:17.360 READ DMA
f8 00 00 00 00 00 f0 08 01:15:17.344 READ NATIVE MAX ADDRESS
ec 00 00 00 00 00 b0 0a 01:15:17.344 IDENTIFY DEVICE
ef 03 42 00 00 00 b0 0a 01:15:17.344 SET FEATURES [Set transfer mode]
f8 00 00 00 00 00 f0 08 01:15:17.328 READ NATIVE MAX ADDRESS

Error 31011 occurred at disk power-on lifetime: 32259 hours (1344 days + 3 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 71 df de 04 f1 Error: UNC 113 sectors at LBA = 0x0104dedf = 17096415

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 00 00 df de 04 f1 08 01:15:14.928 READ DMA
f8 00 00 00 00 00 f0 08 01:15:14.912 READ NATIVE MAX ADDRESS
ec 00 00 00 00 00 b0 0a 01:15:14.912 IDENTIFY DEVICE
ef 03 42 00 00 00 b0 0a 01:15:14.912 SET FEATURES [Set transfer mode]
f8 00 00 00 00 00 f0 08 01:15:14.896 READ NATIVE MAX ADDRESS

Error 31010 occurred at disk power-on lifetime: 32259 hours (1344 days + 3 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 71 df de 04 f1 Error: UNC 113 sectors at LBA = 0x0104dedf = 17096415

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 00 00 df de 04 f1 08 01:15:12.512 READ DMA
f8 00 00 00 00 00 f0 08 01:15:12.496 READ NATIVE MAX ADDRESS
ec 00 00 00 00 00 b0 0a 01:15:12.496 IDENTIFY DEVICE
ef 03 42 00 00 00 b0 0a 01:15:12.496 SET FEATURES [Set transfer mode]
f8 00 00 00 00 00 f0 08 01:15:12.480 READ NATIVE MAX ADDRESS

Error 31009 occurred at disk power-on lifetime: 32259 hours (1344 days + 3 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 71 df de 04 f1 Error: UNC 113 sectors at LBA = 0x0104dedf = 17096415

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 00 00 df de 04 f1 08 01:15:10.112 READ DMA
f8 00 00 00 00 00 f0 08 01:15:10.096 READ NATIVE MAX ADDRESS
ec 00 00 00 00 00 b0 0a 01:15:10.096 IDENTIFY DEVICE
ef 03 42 00 00 00 b0 0a 01:15:10.096 SET FEATURES [Set transfer mode]
f8 00 00 00 00 00 f0 08 01:15:10.080 READ NATIVE MAX ADDRESS

Error 31008 occurred at disk power-on lifetime: 32259 hours (1344 days + 3 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 71 df de 04 f1 Error: UNC 113 sectors at LBA = 0x0104dedf = 17096415

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 00 00 df de 04 f1 08 01:15:07.696 READ DMA
f8 00 00 00 00 00 f0 08 01:15:07.680 READ NATIVE MAX ADDRESS
ec 00 00 00 00 00 b0 0a 01:15:07.680 IDENTIFY DEVICE
ef 03 42 00 00 00 b0 0a 01:15:07.664 SET FEATURES [Set transfer mode]
f8 00 00 00 00 00 f0 08 01:15:07.648 READ NATIVE MAX ADDRESS

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Aborted by host 30% 0 -

Device does not support Selective Self Tests/Logging
m
0
l
a c 288 G Storage
December 9, 2012 6:25:49 AM

Device Model: Maxtor 5T020H2
Firmware Version: TAH71DP0

9 Power_On_Minutes 0x0032 152 152 000 Old_age Always - 259h+59m

It does look like a problem with the interpretation. You can easily verify the actual units (hours / minutes / seconds) by waiting for a few minutes or one hour, and then re-examining the Power On Time Count.

However, if we take the total number of minutes and reinterpret it as hours, then we have a Power On Time of 1.78 years.

259h+59m = (260 x 60) - 1 minutes = 15599 minutes

15599 hours = 15599 / (24 x 365) years = 1.78 years

If we examine the normalised value and assume that it has declined from 252 to 152 over the course of 1.78 years, then we can calculate the expected life of the drive (according to SMART) as ...

1.78 x 252 / (252 - 152) = 4.49 years

I did some Googling and found the following SMART results:

http://pchelper.nl/showthread.php?t=28697

Maxtor 5T020H2
Revisie TAH71DP0
09 Power-On Time Count 0 252 252 34689 OK

Notice that the normalised value hasn't budged from 252, suggesting that the drive is almost new. However, the raw value is indicating otherwise. Stranger still, the firmware version is the same as yours (!?).

Here's another one:

http://forums.cnetfrance.fr/attachment.php?attachmentid...

Maxtor 5T020H2
RĂ©vision TAH71DP0
09 Power-On Time Count 0 237 237 5534 OK

Once again the firmware version is the same, but the results are different again.

Expected life <= 5534 hours x 252 / (252 - 237) / (24 x 365) years <= 10.6 years
Expected life >= 5534 hours x 252 / (252 - 236) / (24 x 365) years >= 9.95 years

This time it appears that SMART allows for a lifetime of 10 years, and the raw value reflects the lifetime in hours.

I confess I'm confused.
m
0
l
!