SLRist Posted November 29, 2013 Share Posted November 29, 2013 I noticed that one of the disks in my 3rd unRAID box has 4 error reports appended to the SMART metrics. I generally just check Reallocated_Sector_Ct every few months and make sure it isn't growing, but I'm not sure what to make of these reports. This box is quite a recent build, and this is the first SMART report I've run on it. I've coloured the section I'm concerned about in maroon. Can someone set my mind at ease, or suggest what action I should take? The disk is only about 6 months old, so within warranty. Many thanks. root@UNRAID-03:/dev# smartctl -a /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST4000DM000-1F2168 Serial Number: W300AM7S Firmware Version: CC52 User Capacity: 4,000,787,030,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Fri Nov 29 11:43:35 2013 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: (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: ( 612) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: (0x1085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 120 099 006 Pre-fail Always - 238342312 3 Spin_Up_Time 0x0003 091 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 217 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3721999 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3595 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 14 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 096 096 000 Old_age Always - 4 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 071 062 045 Old_age Always - 29 (Min/Max 19/31) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2114 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 13 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 44220983279911 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 6752236736 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 43160503321 SMART Error Log Version: 1 ATA Error Count: 4 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 4 occurred at disk power-on lifetime: 2584 hours (107 days + 16 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 -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+22:59:46.289 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:46.266 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:46.256 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:46.246 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:44.618 READ DMA EXT Error 3 occurred at disk power-on lifetime: 2584 hours (107 days + 16 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 -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+22:59:35.952 READ DMA EXT 35 00 38 ff ff ff ef 00 40d+22:59:35.585 WRITE DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:35.354 READ DMA EXT ef 10 02 00 00 00 a0 00 40d+22:59:35.353 SET FEATURES [Reserved for Serial A TA] 27 00 00 00 00 00 e0 00 40d+22:59:35.353 READ NATIVE MAX ADDRESS EXT Error 2 occurred at disk power-on lifetime: 2584 hours (107 days + 16 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 -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+22:59:26.227 READ DMA EXT 25 00 28 ff ff ff ef 00 40d+22:59:26.207 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:23.024 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:22.248 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:22.184 READ DMA EXT Error 1 occurred at disk power-on lifetime: 2584 hours (107 days + 16 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 -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+22:59:08.794 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:08.766 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:08.755 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:08.745 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+22:59:08.736 READ DMA EXT SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Link to comment
c3 Posted November 29, 2013 Share Posted November 29, 2013 They are uncorrectable read errors, all occurred at once (or close enough) several weeks ago (1000 hours ago), possible sequentially. You might have noticed it. If not, the read was successful on retry. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.