weetnie Posted September 28, 2019 Share Posted September 28, 2019 Event: unRAID Disk 6 error Subject: Alert [TOWER] - Disk 6 in error state (disk dsbl) Description: WDC_WD60EFRX-68MYMN1_WD-WX81D65ASKPC (sdg) Importance: alert Woke up this morning to a red X next to Disk 6. From https://wiki.unraid.net/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F - I have gathered the SMART report for Disk 6 along with tower diagnostics. I have not rebooted my system yet. I've also done a recheck of all of the connections, nothing seems to have come loose. smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD60EFRX-68MYMN1 Serial Number: WD-WX81D65ASKPC LU WWN Device Id: 5 0014ee 2b740f33e Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Sep 28 09:04:43 2019 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: 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: ( 1904) 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: ( 673) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 198 194 021 - 9066 4 Start_Stop_Count -O--CK 100 100 000 - 95 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 055 055 000 - 33158 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 91 192 Power-Off_Retract_Count -O--CK 200 200 000 - 73 193 Load_Cycle_Count -O--CK 189 189 000 - 34766 194 Temperature_Celsius -O---K 128 107 000 - 24 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0 ||||||_ 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] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 40 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 1 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 1 [0] occurred at disk power-on lifetime: 33136 hours (1380 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 COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 00 00 00 02 89 b0 18 40 00 Error: IDNF at LBA = 0x0289b018 = 42577944 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 04 00 00 00 00 00 02 89 b0 18 40 00 39d+17:24:46.106 WRITE FPDMA QUEUED 61 04 00 00 00 00 00 02 89 ac 18 40 00 39d+17:24:46.100 WRITE FPDMA QUEUED 61 04 00 00 00 00 00 02 89 a8 18 40 00 39d+17:24:46.084 WRITE FPDMA QUEUED 61 04 00 00 00 00 00 02 89 a4 18 40 00 39d+17:24:46.083 WRITE FPDMA QUEUED 60 04 00 00 00 00 00 02 89 bc 18 40 00 39d+17:24:46.082 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) 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. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) Device State: Active (0) Current Temperature: 24 Celsius Power Cycle Min/Max Temperature: 23/36 Celsius Lifetime Min/Max Temperature: 2/45 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 (358) Index Estimated Time Temperature Celsius 359 2019-09-28 01:07 23 **** ... ..( 48 skipped). .. **** 408 2019-09-28 01:56 23 **** 409 2019-09-28 01:57 24 ***** ... ..( 14 skipped). .. ***** 424 2019-09-28 02:12 24 ***** 425 2019-09-28 02:13 26 ******* ... ..( 14 skipped). .. ******* 440 2019-09-28 02:28 26 ******* 441 2019-09-28 02:29 27 ******** ... ..( 22 skipped). .. ******** 464 2019-09-28 02:52 27 ******** 465 2019-09-28 02:53 26 ******* ... ..( 73 skipped). .. ******* 61 2019-09-28 04:07 26 ******* 62 2019-09-28 04:08 25 ****** ... ..( 66 skipped). .. ****** 129 2019-09-28 05:15 25 ****** 130 2019-09-28 05:16 24 ***** 131 2019-09-28 05:17 24 ***** 132 2019-09-28 05:18 24 ***** 133 2019-09-28 05:19 25 ****** ... ..( 18 skipped). .. ****** 152 2019-09-28 05:38 25 ****** 153 2019-09-28 05:39 24 ***** ... ..(124 skipped). .. ***** 278 2019-09-28 07:44 24 ***** 279 2019-09-28 07:45 23 **** ... ..( 78 skipped). .. **** 358 2019-09-28 09:04 23 **** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported 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 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 6 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 153 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 3513313 Vendor specific tower-diagnostics-20190928-1606.zip WDC_WD60EFRX-68MYMN1_WD-WX81D65ASKPC-20190928-1606 disk6 (sdg) - DISK_DSBL.txt Quote Link to comment
JorgeB Posted September 29, 2019 Share Posted September 29, 2019 Disk looks fine, suggest replacing/swapping cables just to rull them out and rebuild, you can also run an extended SMART test. Quote Link to comment
weetnie Posted September 29, 2019 Author Share Posted September 29, 2019 8 hours ago, johnnie.black said: Disk looks fine, suggest replacing/swapping cables just to rull them out and rebuild, you can also run an extended SMART test. Appreciate the post, that's reassuring. If there were signs of the drive failing, or getting ready to fail, what type of logs would I be seeing? Trying to learn how I can debug myself in the future. I ran an extended SMART test last night and results came back "Completed without error." However, I looked at syslog.txt and see close to 300 write errors to various sectors. Is this just an effect of whatever caused the original error? Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577888 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577896 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577904 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577912 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577920 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577928 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577936 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577944 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577952 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577960 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577968 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577976 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577984 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42577992 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578000 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578008 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578016 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578024 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578032 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578040 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578048 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578056 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578064 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578072 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578080 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578088 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578096 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578104 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578112 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578120 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578128 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578136 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578144 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578152 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578160 Sep 27 10:33:05 Tower kernel: md: disk6 write error, sector=42578168 Quote Link to comment
JorgeB Posted October 5, 2019 Share Posted October 5, 2019 On 9/29/2019 at 6:40 PM, weetnie said: However, I looked at syslog.txt and see close to 300 write errors to various sectors. Is this just an effect of whatever caused the original error? Likely yes, but can't say without the diags. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.