One of my pools has 4x WD Red drives in a RAIDz1 and my system emailed me with the following errors overnight. Searching the forums this seems to be either a drive error or a SATA cable error. How can I determine which one it is?
Looking at my zpool status I also found:
smartctl -a /dev/ada3 reports the below. When I have had disk failures before usually I see pending sectors, reallocated sectors, or offline uncorrectable errors start increasing but in this case they have not:
Looking at the results of smartctl -x /dev/ada3 I noticed the following in the error log section. Does this mean it is the actual drive itself, or it still could be the cable or the drive?
Any thoughts would be appreciated?
Code:
Feb 18 10:10:02 freenas (ada3:ahcich5:0:0:0): READ_FPDMA_QUEUED. ACB: 60 b0 30 a9 dc 40 bd 01 00 00 00 00 Feb 18 10:10:02 freenas (ada3:ahcich5:0:0:0): CAM status: ATA Status Error Feb 18 10:10:02 freenas (ada3:ahcich5:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Feb 18 10:10:02 freenas (ada3:ahcich5:0:0:0): RES: 41 40 b0 a9 dc 40 bd 01 00 00 00 Feb 18 10:10:02 freenas (ada3:ahcich5:0:0:0): Retrying command Feb 18 10:10:05 freenas (ada3:ahcich5:0:0:0): READ_FPDMA_QUEUED. ACB: 60 b0 30 a9 dc 40 bd 01 00 00 00 00 Feb 18 10:10:05 freenas (ada3:ahcich5:0:0:0): CAM status: ATA Status Error Feb 18 10:10:05 freenas (ada3:ahcich5:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Feb 18 10:10:05 freenas (ada3:ahcich5:0:0:0): RES: 41 40 b0 a9 dc 40 bd 01 00 00 00 Feb 18 10:10:05 freenas (ada3:ahcich5:0:0:0): Retrying command Feb 18 10:10:09 freenas (ada3:ahcich5:0:0:0): READ_FPDMA_QUEUED. ACB: 60 b0 30 a9 dc 40 bd 01 00 00 00 00 Feb 18 10:10:09 freenas (ada3:ahcich5:0:0:0): CAM status: ATA Status Error Feb 18 10:10:09 freenas (ada3:ahcich5:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Feb 18 10:10:09 freenas (ada3:ahcich5:0:0:0): RES: 41 40 b0 a9 dc 40 bd 01 00 00 00 Feb 18 10:10:09 freenas (ada3:ahcich5:0:0:0): Retrying command Feb 18 10:10:12 freenas (ada3:ahcich5:0:0:0): READ_FPDMA_QUEUED. ACB: 60 b0 30 a9 dc 40 bd 01 00 00 00 00 Feb 18 10:10:12 freenas (ada3:ahcich5:0:0:0): CAM status: ATA Status Error Feb 18 10:10:12 freenas (ada3:ahcich5:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Feb 18 10:10:12 freenas (ada3:ahcich5:0:0:0): RES: 41 40 b0 a9 dc 40 bd 01 00 00 00 Feb 18 10:10:12 freenas (ada3:ahcich5:0:0:0): Retrying command Feb 18 10:10:16 freenas (ada3:ahcich5:0:0:0): READ_FPDMA_QUEUED. ACB: 60 b0 30 a9 dc 40 bd 01 00 00 00 00 Feb 18 10:10:16 freenas (ada3:ahcich5:0:0:0): CAM status: ATA Status Error Feb 18 10:10:16 freenas (ada3:ahcich5:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Feb 18 10:10:16 freenas (ada3:ahcich5:0:0:0): RES: 41 40 b0 a9 dc 40 bd 01 00 00 00 Feb 18 10:10:16 freenas (ada3:ahcich5:0:0:0): Error 5, Retries exhausted
Looking at my zpool status I also found:
Code:
pool: data state: ONLINE scan: scrub repaired 88K in 11h52m with 0 errors on Sun Feb 18 11:52:54 2018 config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 gptid/ed0ecf8b-8926-11e6-aeed-0cc47aca83c4 ONLINE 0 0 0 gptid/ee3b366f-8926-11e6-aeed-0cc47aca83c4 ONLINE 0 0 0 gptid/ef6c43ac-8926-11e6-aeed-0cc47aca83c4 ONLINE 0 0 0 gptid/f08f8ee8-8926-11e6-aeed-0cc47aca83c4 ONLINE 0 0 0 errors: No known data errors
smartctl -a /dev/ada3 reports the below. When I have had disk failures before usually I see pending sectors, reallocated sectors, or offline uncorrectable errors start increasing but in this case they have not:
Code:
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: <removed> LU WWN Device Id: <removed> Firmware Version: 82.00A82 User Capacity: 4,000,787,030,016 bytes [4.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 Feb 19 08:27:41 2018 ACDT 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: (57120) 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: ( 570) 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 - 5 3 Spin_Up_Time 0x0027 185 178 021 Pre-fail Always - 7733 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4891 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 069 069 000 Old_age Always - 22733 10 Spin_Retry_Count 0x0032 100 100 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 - 62 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 196 196 000 Old_age Always - 13422 194 Temperature_Celsius 0x0022 120 100 000 Old_age Always - 32 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 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 22459 - # 2 Short offline Completed without error 00% 22241 - # 3 Short offline Completed without error 00% 22085 - # 4 Short offline Completed without error 00% 21915 - # 5 Short offline Completed without error 00% 21744 - # 6 Short offline Completed without error 00% 21574 - # 7 Short offline Completed without error 00% 21407 - # 8 Short offline Completed without error 00% 21235 - # 9 Short offline Completed without error 00% 21072 - #10 Short offline Completed without error 00% 20903 - #11 Short offline Completed without error 00% 20737 - #12 Short offline Completed without error 00% 20565 - #13 Short offline Completed without error 00% 20427 - #14 Short offline Completed without error 00% 20332 - #15 Short offline Completed without error 00% 20123 - #16 Short offline Completed without error 00% 19892 - #17 Short offline Completed without error 00% 19728 - #18 Short offline Completed without error 00% 19566 - #19 Short offline Completed without error 00% 19397 - #20 Short offline Completed without error 00% 19234 - #21 Short offline Completed without error 00% 19078 - 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.
Looking at the results of smartctl -x /dev/ada3 I noticed the following in the error log section. Does this mean it is the actual drive itself, or it still could be the cable or the drive?
Code:
SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 5 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 5 [4] occurred at disk power-on lifetime: 22711 hours (946 days + 7 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 bd dc a9 b0 40 00 Error: UNC at LBA = 0x1bddca9b0 = 7480322480 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 b0 00 90 00 01 bd dc a9 e0 40 08 2d+00:30:56.381 READ FPDMA QUEUED 60 00 b0 00 88 00 01 bd dc a9 30 40 08 2d+00:30:56.381 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 40 08 2d+00:30:56.377 READ LOG EXT 60 00 b0 00 78 00 01 bd dc a9 e0 40 08 2d+00:30:52.973 READ FPDMA QUEUED 60 00 b0 00 70 00 01 bd dc a9 30 40 08 2d+00:30:52.973 READ FPDMA QUEUED Error 4 [3] occurred at disk power-on lifetime: 22711 hours (946 days + 7 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 bd dc a9 b0 40 00 Error: UNC at LBA = 0x1bddca9b0 = 7480322480 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 b0 00 78 00 01 bd dc a9 e0 40 08 2d+00:30:52.973 READ FPDMA QUEUED 60 00 b0 00 70 00 01 bd dc a9 30 40 08 2d+00:30:52.973 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 40 08 2d+00:30:52.969 READ LOG EXT 60 00 b0 00 60 00 01 bd dc a9 e0 40 08 2d+00:30:49.565 READ FPDMA QUEUED 60 00 b0 00 58 00 01 bd dc a9 30 40 08 2d+00:30:49.565 READ FPDMA QUEUED Error 3 [2] occurred at disk power-on lifetime: 22711 hours (946 days + 7 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 bd dc a9 b0 40 00 Error: UNC at LBA = 0x1bddca9b0 = 7480322480 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 b0 00 60 00 01 bd dc a9 e0 40 08 2d+00:30:49.565 READ FPDMA QUEUED 60 00 b0 00 58 00 01 bd dc a9 30 40 08 2d+00:30:49.565 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 40 08 2d+00:30:49.561 READ LOG EXT 60 00 b0 00 48 00 01 bd dc a9 e0 40 08 2d+00:30:46.158 READ FPDMA QUEUED 60 00 b0 00 40 00 01 bd dc a9 30 40 08 2d+00:30:46.158 READ FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 22711 hours (946 days + 7 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 bd dc a9 b0 40 00 Error: UNC at LBA = 0x1bddca9b0 = 7480322480 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 b0 00 48 00 01 bd dc a9 e0 40 08 2d+00:30:46.158 READ FPDMA QUEUED 60 00 b0 00 40 00 01 bd dc a9 30 40 08 2d+00:30:46.158 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 40 08 2d+00:30:46.154 READ LOG EXT 60 00 b0 00 28 00 01 bd dc a9 30 40 08 2d+00:30:42.774 READ FPDMA QUEUED 60 00 b0 00 20 00 01 bd dc a8 80 40 08 2d+00:30:42.772 READ FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 22711 hours (946 days + 7 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 bd dc a9 b0 40 00 Error: UNC at LBA = 0x1bddca9b0 = 7480322480 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 b0 00 28 00 01 bd dc a9 30 40 08 2d+00:30:42.774 READ FPDMA QUEUED 60 00 b0 00 20 00 01 bd dc a8 80 40 08 2d+00:30:42.772 READ FPDMA QUEUED 60 00 b0 00 18 00 01 bd dc a7 d0 40 08 2d+00:30:42.772 READ FPDMA QUEUED 60 00 b0 00 10 00 01 bd dc a7 20 40 08 2d+00:30:42.771 READ FPDMA QUEUED 60 00 b0 00 08 00 01 bd dc a6 70 40 08 2d+00:30:42.770 READ FPDMA QUEUED
Any thoughts would be appreciated?