smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: W1F11KN3 LU WWN Device Id: 5 000c50 053190b62 Firmware Version: CC9F User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Jun 6 23:50:18 2016 CEST 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3081) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 118 096 006 - 173858184 3 Spin_Up_Time PO---- 092 092 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 88 5 Reallocated_Sector_Ct PO--CK 100 100 036 - 0 7 Seek_Error_Rate POSR-- 072 060 030 - 15672392 9 Power_On_Hours -O--CK 093 093 000 - 6174 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 80 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error -O--CK 100 100 099 - 0 187 Reported_Uncorrect -O--CK 001 001 000 - 376 188 Command_Timeout -O--CK 100 098 000 - 4 4 45 189 High_Fly_Writes -O-RCK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 068 043 045 Past 32 (0 69 32 31) 191 G-Sense_Error_Rate -O--CK 100 100 000 - 0 192 Power-Off_Retract_Count -O--CK 100 100 000 - 77 193 Load_Cycle_Count -O--CK 051 051 000 - 99397 194 Temperature_Celsius -O---K 032 057 000 - 32 (0 16 0 0) 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 15 240 Head_Flying_Hours ------ 100 253 000 - 4476h+00m+38.269s 241 Total_LBAs_Written ------ 100 253 000 - 121733335771390 242 Total_LBAs_Read ------ 100 253 000 - 30609214658671 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [Summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 5 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [SMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [Selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error] GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters] GP Log at address 0x21 has 1 sectors [Write stream error log] GP Log at address 0x22 has 1 sectors [Read stream error log] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa1 has 20 sectors [Device vendor specific log] GP Log at address 0xa2 has 4496 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 20 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP Log at address 0xab has 1 sectors [Device vendor specific log] GP Log at address 0xb0 has 5067 sectors [Device vendor specific log] GP Log at address 0xbd has 512 sectors [Device vendor specific log] GP Log at address 0xbe has 65535 sectors [Device vendor specific log] GP Log at address 0xbf has 65535 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer] SMART Extended Comprehensive Error Log Version: 1 (5 sectors) Device Error Count: 325 (device log contains only the most recent 20 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register 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 325 [4] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: WP at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 00 00 08 00 00 00 5d 4d e0 40 00 1d+03:30:37.910 WRITE FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:30:37.910 READ FPDMA QUEUED 61 00 00 00 08 00 00 00 5d d3 88 40 00 1d+03:30:37.902 WRITE FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 00 00 1d+03:30:37.748 READ LOG EXT 61 00 00 00 08 00 00 00 5d d3 88 40 00 1d+03:30:37.166 WRITE FPDMA QUEUED Error 324 [3] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: WP at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 00 00 08 00 00 00 5d d3 88 40 00 1d+03:30:37.166 WRITE FPDMA QUEUED 61 00 00 00 08 00 00 00 66 ea d0 40 00 1d+03:30:34.997 WRITE FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:30:34.997 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 00 00 1d+03:30:34.971 FLUSH CACHE EXT 2f 00 00 00 01 00 00 00 00 00 10 00 00 1d+03:30:34.830 READ LOG EXT Error 323 [2] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: UNC at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:30:32.067 READ FPDMA QUEUED 61 00 00 00 08 00 00 00 5d 4d 60 40 00 1d+03:30:32.060 WRITE FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 00 00 1d+03:30:31.955 READ LOG EXT 61 00 00 00 08 00 00 00 5d 4d 60 40 00 1d+03:30:31.448 WRITE FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:30:29.224 READ FPDMA QUEUED Error 322 [1] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: WP at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 00 00 08 00 00 00 5d 4d 60 40 00 1d+03:30:31.448 WRITE FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:30:29.224 READ FPDMA QUEUED 61 00 00 00 08 00 00 00 5d 4d 58 40 00 1d+03:30:25.942 WRITE FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 00 00 1d+03:30:25.867 FLUSH CACHE EXT 61 00 00 00 08 00 00 00 5d 4d e0 40 00 1d+03:30:25.867 WRITE FPDMA QUEUED Error 321 [0] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: WP at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 00 00 08 00 00 00 5d d3 70 40 00 1d+03:30:03.203 WRITE FPDMA QUEUED 61 00 00 00 08 00 00 00 04 09 60 40 00 1d+03:30:01.628 WRITE FPDMA QUEUED 61 00 00 00 08 00 00 00 64 08 40 40 00 1d+03:30:01.628 WRITE FPDMA QUEUED 61 00 00 00 08 00 00 17 c3 84 d0 40 00 1d+03:30:01.628 WRITE FPDMA QUEUED 61 00 00 00 08 00 00 00 66 ea d0 40 00 1d+03:30:01.628 WRITE FPDMA QUEUED Error 320 [19] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: UNC at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:29:58.656 READ FPDMA QUEUED 60 00 00 00 80 00 00 1a d9 20 00 40 00 1d+03:29:58.655 READ FPDMA QUEUED 61 00 00 00 08 00 00 00 5d 4d e0 40 00 1d+03:29:58.646 WRITE FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 00 00 1d+03:29:58.507 READ LOG EXT 61 00 00 00 08 00 00 00 5d 4d e0 40 00 1d+03:29:55.904 WRITE FPDMA QUEUED Error 319 [18] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: WP at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 00 00 08 00 00 00 5d 4d e0 40 00 1d+03:29:55.904 WRITE FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:29:55.692 READ FPDMA QUEUED 60 00 00 00 80 00 01 51 59 77 28 40 00 1d+03:29:55.691 READ FPDMA QUEUED 60 00 00 00 80 00 00 1a d9 20 00 40 00 1d+03:29:55.691 READ FPDMA QUEUED 60 00 00 00 30 00 01 51 59 75 f8 40 00 1d+03:29:55.634 READ FPDMA QUEUED Error 318 [17] occurred at disk power-on lifetime: 6017 hours (250 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 51 59 75 f0 00 00 Error: UNC at LBA = 0x1515975f0 = 5659784688 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 30 00 01 51 59 75 f8 40 00 1d+03:29:52.763 READ FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 f0 40 00 1d+03:29:52.737 READ FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 e8 40 00 1d+03:29:52.737 READ FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 e0 40 00 1d+03:29:52.736 READ FPDMA QUEUED 60 00 00 00 08 00 01 51 59 75 d8 40 00 1d+03:29:52.736 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 5965 - # 2 Extended offline Completed: read failure 10% 5959 5659784688 # 3 Extended offline Completed: read failure 10% 5943 5659784688 # 4 Short offline Completed without error 00% 5934 - # 5 Short offline Completed without error 00% 5910 - # 6 Short offline Completed without error 00% 5886 - # 7 Short offline Completed without error 00% 5852 - # 8 Short offline Completed without error 00% 5828 - # 9 Extended offline Interrupted (host reset) 00% 5817 - #10 Short offline Completed without error 00% 5811 - #11 Short offline Completed without error 00% 5786 - #12 Extended offline Completed: read failure 10% 5772 5659784688 #13 Short offline Completed without error 00% 5762 - #14 Short offline Completed without error 00% 5738 - #15 Short offline Completed without error 00% 5714 - #16 Short offline Completed: read failure 90% 5690 5659784688 #17 Short offline Completed: read failure 90% 5666 5659784688 #18 Short offline Completed: read failure 90% 5642 5659784688 #19 Short offline Completed: read failure 80% 5623 5659784688 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. Warning: device does not support SCT Data Table command Warning: device does not support SCT Error Recovery Control command SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 4 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS