June 1, 20197 yr Hi, one of my drives is marked as disabled, probably because an error occured on it. I've run a SMART test on this which also indicated an error. How can i tell if the drive should be replaced? This is the smart report for the drive: Quote smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.49-unRAID] (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-WCC4M3ALAV1J LU WWN Device Id: 5 0014ee 20da1cc34 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: Sat Jun 1 16:42:01 2019 CEST 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (27240) 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: ( 275) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 204 3 Spin_Up_Time POS--K 173 171 021 - 4316 4 Start_Stop_Count -O--CK 100 100 000 - 131 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 077 077 000 - 17418 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 127 192 Power-Off_Retract_Count -O--CK 200 200 000 - 125 193 Load_Cycle_Count -O--CK 198 198 000 - 7064 194 Temperature_Celsius -O---K 114 104 000 - 33 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-- 200 200 000 - 17 ||||||_ 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 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb7 GPL,SL VS 1 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: 23 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 23 [22] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 55 d8 40 00 Error: UNC at LBA = 0x3b3355d8 = 993220056 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 03 e0 00 00 00 00 3b 33 55 d0 40 00 2d+14:42:36.987 READ FPDMA QUEUED 61 00 28 00 00 00 00 3b 33 51 a8 40 00 2d+14:42:36.987 WRITE FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 40 00 2d+14:42:36.987 READ LOG EXT 60 04 00 00 00 00 00 3b 33 51 d0 40 00 2d+14:42:33.488 READ FPDMA QUEUED 60 01 b8 00 00 00 00 3c 70 bc 90 40 00 2d+14:42:33.477 READ FPDMA QUEUED Error 22 [21] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 51 f8 40 00 Error: UNC at LBA = 0x3b3351f8 = 993219064 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 04 00 00 00 00 00 3b 33 51 d0 40 00 2d+14:42:33.488 READ FPDMA QUEUED 60 01 b8 00 00 00 00 3c 70 bc 90 40 00 2d+14:42:33.477 READ FPDMA QUEUED 60 00 08 00 00 00 00 3c 65 22 68 40 00 2d+14:42:33.465 READ FPDMA QUEUED 60 00 18 00 00 00 00 3a 38 93 80 40 00 2d+14:42:33.459 READ FPDMA QUEUED 60 00 20 00 00 00 00 3a 38 8c 70 40 00 2d+14:42:33.453 READ FPDMA QUEUED Error 21 [20] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 74 82 39 a8 c0 00 Error: IDNF at LBA = 0x748239a8 = 1954691496 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 00 08 00 00 00 00 74 82 39 a8 c0 00 2d+14:42:26.458 WRITE FPDMA QUEUED 60 00 08 00 00 00 00 3a 38 83 d8 40 00 2d+14:42:26.458 READ FPDMA QUEUED 60 00 08 00 00 00 00 3a 38 83 c0 40 00 2d+14:42:26.447 READ FPDMA QUEUED 60 00 08 00 00 00 00 74 82 39 a8 40 00 2d+14:42:26.432 READ FPDMA QUEUED 61 03 f8 00 00 00 00 3b 33 46 d8 40 00 2d+14:42:26.431 WRITE FPDMA QUEUED Error 20 [19] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 51 a8 40 00 Error: UNC at LBA = 0x3b3351a8 = 993218984 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 03 00 00 00 00 00 3b 33 4e d0 40 00 2d+14:42:22.922 READ FPDMA QUEUED 61 01 00 00 00 00 00 3b 33 45 d0 40 00 2d+14:42:22.922 WRITE FPDMA QUEUED 61 00 20 00 00 00 00 3a 38 22 c0 40 00 2d+14:42:22.922 WRITE FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 40 00 2d+14:42:22.893 FLUSH CACHE EXT 60 04 00 00 00 00 00 3b 33 4a d0 40 00 2d+14:42:22.879 READ FPDMA QUEUED Error 19 [18] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 46 d8 40 00 Error: UNC at LBA = 0x3b3346d8 = 993216216 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 04 00 00 00 00 00 3b 33 46 d0 40 00 2d+14:42:19.386 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 40 00 2d+14:42:00.934 FLUSH CACHE EXT 2f 00 00 00 01 00 00 00 00 00 10 40 00 2d+14:42:00.934 READ LOG EXT 60 04 00 00 00 00 00 3b 33 42 d0 40 00 2d+14:41:57.056 READ FPDMA QUEUED 61 03 d8 00 00 00 00 3b 33 3b 10 40 00 2d+14:41:57.055 WRITE FPDMA QUEUED Error 18 [17] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 45 d0 40 00 Error: UNC at LBA = 0x3b3345d0 = 993215952 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 04 00 00 00 00 00 3b 33 42 d0 40 00 2d+14:41:57.056 READ FPDMA QUEUED 61 03 d8 00 00 00 00 3b 33 3b 10 40 00 2d+14:41:57.055 WRITE FPDMA QUEUED 61 03 20 00 00 00 00 3c 70 b9 70 40 00 2d+14:41:57.054 WRITE FPDMA QUEUED 61 00 08 00 00 00 00 3c 61 91 c8 40 00 2d+14:41:57.054 WRITE FPDMA QUEUED 61 00 08 00 00 00 00 3a 3a 23 00 40 00 2d+14:41:57.054 WRITE FPDMA QUEUED Error 17 [16] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 3b 10 40 00 Error: UNC at LBA = 0x3b333b10 = 993213200 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 04 00 00 00 00 00 3b 33 3a e8 40 00 2d+14:41:53.538 READ FPDMA QUEUED 60 03 20 00 00 00 00 3c 70 b9 70 40 00 2d+14:41:53.532 READ FPDMA QUEUED 60 00 08 00 00 00 00 3c 61 91 c8 40 00 2d+14:41:53.528 READ FPDMA QUEUED 60 00 08 00 00 00 00 3a 3a 23 00 40 00 2d+14:41:53.522 READ FPDMA QUEUED 60 00 20 00 00 00 00 3a 38 8c 50 40 00 2d+14:41:53.502 READ FPDMA QUEUED Error 16 [15] occurred at disk power-on lifetime: 17405 hours (725 days + 5 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 00 3b 33 39 58 40 00 Error: UNC at LBA = 0x3b333958 = 993212760 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 04 00 00 00 00 00 3b 33 36 d0 40 00 2d+14:41:28.748 READ FPDMA QUEUED 60 04 00 00 00 00 00 3b 33 32 d0 40 00 2d+14:41:28.741 READ FPDMA QUEUED 61 03 e8 00 00 00 00 3b 33 2e e8 40 00 2d+14:41:28.740 WRITE FPDMA QUEUED 60 00 20 00 00 00 00 3a 38 22 c0 40 00 2d+14:41:28.724 READ FPDMA QUEUED 61 02 c8 00 00 00 00 3b 33 2c 08 40 00 2d+14:41:28.722 WRITE FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 17418 62425728 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: 33 Celsius Power Cycle Min/Max Temperature: 24/35 Celsius Lifetime Min/Max Temperature: 16/43 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 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 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 (206) Index Estimated Time Temperature Celsius 207 2019-06-01 08:45 31 ************ ... ..( 38 skipped). .. ************ 246 2019-06-01 09:24 31 ************ 247 2019-06-01 09:25 32 ************* ... ..( 85 skipped). .. ************* 333 2019-06-01 10:51 32 ************* 334 2019-06-01 10:52 31 ************ ... ..( 31 skipped). .. ************ 366 2019-06-01 11:24 31 ************ 367 2019-06-01 11:25 32 ************* ... ..(240 skipped). .. ************* 130 2019-06-01 15:26 32 ************* 131 2019-06-01 15:27 ? - 132 2019-06-01 15:28 32 ************* ... ..( 4 skipped). .. ************* 137 2019-06-01 15:33 32 ************* 138 2019-06-01 15:34 33 ************** ... ..( 11 skipped). .. ************** 150 2019-06-01 15:46 33 ************** 151 2019-06-01 15:47 30 *********** ... ..( 34 skipped). .. *********** 186 2019-06-01 16:22 30 *********** 187 2019-06-01 16:23 31 ************ ... ..( 18 skipped). .. ************ 206 2019-06-01 16:42 31 ************ 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 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 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 4569620 Vendor specific server01-diagnostics-20190601-2045.zip Edited June 1, 20197 yr by deviani marked as solved
June 1, 20197 yr Community Expert you should always Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.
June 1, 20197 yr Community Expert 16 minutes ago, deviani said: added the diagnostics to the post Just a bit of forum advice on this. Since you did, in fact, make a new post then I did see this thread had something new in it so I came back to it. If instead you had simply put the diagnostics in the original post without making a new post then I may not have ever visited your thread again. This is why I said 4 hours ago, trurl said: attach the complete diagnostics zip file to your NEXT post Now, on to your question. Since the disk is disabled, it must be rebuilt. And, in general, it is better to replace a disabled disk than to simply rebuild to the same disk, since it allows you to keep the original disk in reserve in case there is any problem with the rebuild. Many people elect to rebuild to the same disk simply due to the expense of replacing a disk that may, in fact, not be bad. Connection problems are by far more frequently the cause of a disabled disk than an actual bad disk. However, SMART attribute 200 has been mentioned as one that should trigger notifications for WD Red disks, and in fact, I have several WD Reds in my array and I have added that attribute to the notification list for those disks (click on a disk to get to its settings page). So, that is also an argument in favor of replacement. There are also a lot of these in your syslog: Jun 1 03:06:02 server01 kernel: print_req_error: critical medium error, dev sdd, sector 993216216 Jun 1 03:06:02 server01 kernel: md: disk2 read error, sector=993216152 Jun 1 03:06:02 server01 kernel: md: disk2 read error, sector=993216160 ... So, I would say replacement is in order. By the way, impressive uptime in your syslog. You really should upgrade your Unraid version though.
June 1, 20197 yr Author Thanks a lot for the information. gonna order a replacement for the drive then. I also updated unraid now, though i'll probably do the reboot when i replace the drive. I usually don't do updates unless there is a specific reason for it, hence the older version
Archived
This topic is now archived and is closed to further replies.