October 4, 20232 yr Hi, I just got HDD read errors this morning on my drive nb 9. What is your advice regarding that disk and the others ? Bellow is an abstract of the SMART info for that HDD (WDC_WD40EFRX-68WT0N0_WD-WCC4E2DCKH26-20231004-1912 sds), and attached my diagnostics file. I thank you very much in advance for your precious advice. Best, OP === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E2DCKH26 LU WWN Device Id: 5 0014ee 20da937f8 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 7.3/5417 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: Wed Oct 4 19:12:10 2023 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 [...] 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 - 13 3 Spin_Up_Time POS--K 179 173 021 - 8025 4 Start_Stop_Count -O--CK 094 094 000 - 6900 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 036 036 000 - 47206 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 099 099 000 - 1407 192 Power-Off_Retract_Count -O--CK 200 200 000 - 84 193 Load_Cycle_Count -O--CK 198 198 000 - 6938 194 Temperature_Celsius -O---K 116 104 000 - 36 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 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning [...] Edited October 16, 20232 yr by Opawesome
October 5, 20232 yr Author On 10/4/2023 at 8:29 PM, JorgeB said: SMART shows some issues, run an extended SMART test. The extended test completed without error (see attached). Edited February 24, 20242 yr by Opawesome
October 5, 20232 yr Author Since the drive looks fine, I took the chance of initiating a rebuild onto itself, as shown here: https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself Edited October 5, 20232 yr by Opawesome
October 5, 20232 yr Community Expert 2 hours ago, Opawesome said: Since the drive looks fine, I took the chance of initiating a rebuild onto itself 👍also good idea to replace/swap cables/slot to rule that out in case it happens again to the same disk.
October 5, 20232 yr Author 37 minutes ago, JorgeB said: 👍also good idea to replace/swap cables/slot to rule that out in case it happens again to the same disk. This is noted. Thank you very much for your help.
October 6, 20232 yr Author UPDATE: Data rebuild finished successfully (I think) but the parity check performed right after caused new read errors. As I still have 31 TB of free space available on my array, I have decided to scatter the 350GB of data from the failing drive (currently emulated thanks to parity) on another drive, then perform a shrink of the array (I will try the method that preserves parity first) and then dispose of the failing drive. Do not hesitate to let me know if I am making a mistake 🙂. In particular, I wonder if I should zero the failed drive while it is being emulated, or actually zero the drive after reassigning it in the config. Unless it makes no difference (which I think could be the case) ? Edited October 16, 20232 yr by Opawesome
October 6, 20232 yr Author 14 minutes ago, JorgeB said: If you've already replaced cables I would replace the disk. Noted. The disk is on a backplate connected to an HBA with SAS cables, so I kinda ruled out the cable issue (although I will order an extra cable to make the swap as you suggest). But the disk having been on 24/7 for more than 10 years, I think its time for replacement indeed. If the issue persists after I have put a new disk, then it means this slot of my HDD backplate is defective (which would suck...) Edited October 6, 20232 yr by Opawesome
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.