Re: Which attributes can estimate number of bad blocks?
Gandalf Corvotempesta <[email protected]> Tue, 2 Aug 2016 14:50:25 +0200
| Newsgroups | gmane.linux.utilities.smartmontools |
|---|---|
| Message-ID | <CAJH6TXixhMdwbNZLhU2=R9cyMHnfsvzLDmnx30ZUYL4WVbk9aQ@mail.gmail.com> |
2016-08-02 13:29 GMT+02:00 Bruce Allen <[email protected]>: > I would not replace this, if the number of bad sectors is not growing. 16 is not a large number. ok. > Probably not. What types of errors. I'm unable to read the smartctl output looking for errors. This is the whole "-x" output: # smartctl -x /dev/sg3 smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD6000HLHX-01JJPV0 Serial Number: WD-WXG1E2155577 Firmware Version: 04.05G04 User Capacity: 600,127,266,816 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Aug 2 14:46:38 2016 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ Register values returned from SMART Status command are: ERR=0x00, SC=0x00, LL=0x00, LM=0x00, LH=0x00, DEV=0x00, STS=0x00 SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. 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: (8280) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 88) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 0x002f 200 200 051 Pre-fail Always - 53 3 Spin_Up_Time 0x0027 233 233 021 Pre-fail Always - 3325 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 25 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 042 042 000 Old_age Always - 42590 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 23 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 22 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2 194 Temperature_Celsius 0x0022 115 108 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 General Purpose Logging (GPL) feature set supported 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 6 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/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 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xbd has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 24 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 (6 sectors) Device Error Count: 3 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 3 [2] occurred at disk power-on lifetime: 26697 hours (1112 days + 9 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 -- -- -- == -- == == == -- -- -- -- -- 01 -- 51 00 18 00 00 00 f0 8c d0 40 00 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 18 00 00 00 00 00 f0 8c d0 40 00 39d+04:52:53.462 READ FPDMA QUEUED e5 00 00 00 00 00 00 00 00 00 00 00 00 39d+04:52:53.462 CHECK POWER MODE 2f 00 00 00 01 00 00 00 00 00 10 40 00 39d+04:52:53.461 READ LOG EXT 60 00 18 00 00 00 00 00 f0 8c d0 40 00 39d+04:52:52.135 READ FPDMA QUEUED 61 00 01 00 00 00 00 45 dc 6f af 40 00 39d+04:52:52.060 WRITE FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 26697 hours (1112 days + 9 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 18 00 00 00 f0 8c d0 40 00 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 18 00 00 00 00 00 f0 8c d0 40 00 39d+04:52:52.135 READ FPDMA QUEUED 61 00 01 00 00 00 00 45 dc 6f af 40 00 39d+04:52:52.060 WRITE FPDMA QUEUED 61 00 08 00 00 00 00 45 dc 6f b2 40 00 39d+04:52:52.055 WRITE FPDMA QUEUED 60 00 06 00 00 00 00 45 dc 6f b4 40 00 39d+04:52:52.054 READ FPDMA QUEUED 61 00 08 00 00 00 00 45 dc 6f b2 40 00 39d+04:52:52.050 WRITE FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 26697 hours (1112 days + 9 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 18 00 00 00 f0 8c d0 40 00 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 18 00 00 00 00 00 f0 8c d0 40 00 39d+04:52:50.694 READ FPDMA QUEUED 60 00 40 00 00 00 00 01 21 fb 40 40 00 39d+04:52:50.692 READ FPDMA QUEUED 60 00 08 00 00 00 00 01 21 fb 30 40 00 39d+04:52:50.686 READ FPDMA QUEUED 60 00 08 00 00 00 00 00 4b 2a 28 40 00 39d+04:52:50.682 READ FPDMA QUEUED 60 00 08 00 00 00 00 00 3b 55 90 40 00 39d+04:52:50.679 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% 42577 - # 2 Short offline Completed without error 00% 42553 - # 3 Short offline Completed without error 00% 42529 - # 4 Extended offline Completed without error 00% 42508 - # 5 Short offline Completed without error 00% 42505 - # 6 Extended offline Completed without error 00% 42493 - 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. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Active (0) Current Temperature: 35 Celsius Power Cycle Min/Max Temperature: 30/42 Celsius Lifetime Min/Max Temperature: 30/42 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (427) Index Estimated Time Temperature Celsius 428 2016-08-02 06:49 35 **************** ... ..(112 skipped). .. **************** 63 2016-08-02 08:42 35 **************** 64 2016-08-02 08:43 34 *************** 65 2016-08-02 08:44 35 **************** ... ..(203 skipped). .. **************** 269 2016-08-02 12:08 35 **************** 270 2016-08-02 12:09 36 ***************** 271 2016-08-02 12:10 35 **************** ... ..( 66 skipped). .. **************** 338 2016-08-02 13:17 35 **************** 339 2016-08-02 13:18 36 ***************** 340 2016-08-02 13:19 36 ***************** 341 2016-08-02 13:20 35 **************** ... ..( 17 skipped). .. **************** 359 2016-08-02 13:38 35 **************** 360 2016-08-02 13:39 36 ***************** 361 2016-08-02 13:40 35 **************** ... ..( 65 skipped). .. **************** 427 2016-08-02 14:46 35 **************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-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 0x000a 2 5 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x8000 4 46869469 Vendor specific > I would not worry about this. It could have to do with the normalization of this raw value, which might render the actual value meaningless. Do you have other drives which are identical hardware and firmware to compare with I have 6 identical disks in this server. Only one has some raw read error and some errors logged many years ago (about 194 hours since power on). Nothing to do with the previous posted smartctl output. This is another disk in another server. ------------------------------------------------------------------------------