BlakeNagel07
Dabbler
- Joined
- Jan 4, 2016
- Messages
- 31
Last week I got a message in my local daily run output email stating below.
So I started by running a smart test and it completed with no issue. I figured this was a good time to start scheduling smart test to run regularly on their own.
I got another email saturday 5/5/18 stating below.
My question, is this a sign that ada3 is starting to fail?
Here is the output of #smartctl -a /dev/ada3
Any input would be greatly appreciated.
Code:
Checking status of zfs pools: NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT Server 3.62T 3.06T 582G - 41% 84% 1.00x ONLINE /mnt freenas-boot 14.8G 11.0G 3.76G - - 74% 1.00x ONLINE - pool: Server state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub repaired 3M in 0 days 05:33:20 with 0 errors on Sun Apr 29 05:33:22 2018 config: NAME STATE READ WRITE CKSUM Server ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/21ca543e-d349-11e5-b368-fcaa1499b2f4 ONLINE 0 0 0 gptid/2281f55f-d349-11e5-b368-fcaa1499b2f4 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gptid/233e369b-d349-11e5-b368-fcaa1499b2f4 ONLINE 0 0 0 gptid/23f12d7d-d349-11e5-b368-fcaa1499b2f4 ONLINE 0 0 5 errors: No known data errors -- End of daily output --
So I started by running a smart test and it completed with no issue. I figured this was a good time to start scheduling smart test to run regularly on their own.
I got another email saturday 5/5/18 stating below.
Code:
Device: /dev/ada3, Self-Test Log error count increased from 0 to 1
My question, is this a sign that ada3 is starting to fail?
Here is the output of #smartctl -a /dev/ada3
Code:
root@Server:~ # smartctl -a /dev/ada3 smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD20EFRX-68EUZN0 Serial Number: WD-WCC4M6VDFZPZ LU WWN Device Id: 5 0014ee 20cc30a65 Firmware Version: 82.00A82 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon May 7 08:24:33 2018 EDT 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: ( 113) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (26100) 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: ( 264) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) 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 - 26 3 Spin_Up_Time 0x0027 176 174 021 Pre-fail Always - 4183 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 77 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 074 074 000 Old_age Always - 19073 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 - 77 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 52 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 214 194 Temperature_Celsius 0x0022 120 113 000 Old_age Always - 27 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 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 5 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 5 occurred at disk power-on lifetime: 18877 hours (786 days + 13 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 e8 b6 1c 44 Error: UNC at LBA = 0x041cb6e8 = 68990696 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 e8 b6 1c 44 08 12d+16:49:21.507 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:18.033 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:14.636 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:11.251 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:07.721 READ DMA Error 4 occurred at disk power-on lifetime: 18877 hours (786 days + 13 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 e8 b6 1c 44 Error: UNC at LBA = 0x041cb6e8 = 68990696 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 e8 b6 1c 44 08 12d+16:49:18.033 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:14.636 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:11.251 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:07.721 READ DMA Error 3 occurred at disk power-on lifetime: 18877 hours (786 days + 13 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 e8 b6 1c 44 Error: UNC at LBA = 0x041cb6e8 = 68990696 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 e8 b6 1c 44 08 12d+16:49:14.636 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:11.251 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:07.721 READ DMA Error 2 occurred at disk power-on lifetime: 18877 hours (786 days + 13 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 e8 b6 1c 44 Error: UNC at LBA = 0x041cb6e8 = 68990696 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 e8 b6 1c 44 08 12d+16:49:11.251 READ DMA c8 00 00 e8 b6 1c 44 08 12d+16:49:07.721 READ DMA Error 1 occurred at disk power-on lifetime: 18877 hours (786 days + 13 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 e8 b6 1c 44 Error: UNC at LBA = 0x041cb6e8 = 68990696 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 e8 b6 1c 44 08 12d+16:49:07.721 READ DMA ca 00 20 58 fa 01 40 08 12d+16:49:07.720 WRITE DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 10% 19018 68987040 # 2 Extended offline Interrupted (host reset) 90% 18908 - # 3 Short offline Completed without error 00% 18908 - 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.
Any input would be greatly appreciated.
