January 31, 20179 yr Hi everyone, One of my WD Red 3TBs red-balled tonight and I am not sure how to proceed. On the /main page there are 4 errors. In the syslog.txt there are read and write errors. This appeared to happen around the same time that I updated a Docker image but that shouldn't have any effect because Docker runs on my cache SSD. Attached are the syslog and the SMART report for the disk. These were both just output from the Diagnostics screen a few minutes ago. Please take a look - any input would be greatly appreciated. Thanks! syslog.txt WDC_WD30EFRX-68EUZN0_WD-WCC4N7CVA9LF-20170130-2044.txt
January 31, 20179 yr Author Just looked up the warranty status of the drive - it's covered until December!
January 31, 20179 yr The drive looks fine: 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 - 0 3 Spin_Up_Time 0x0027 192 173 021 Pre-fail Always - 5366 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 558 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 080 080 000 Old_age Always - 15264 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 - 41 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1440 194 Temperature_Celsius 0x0022 133 118 000 Old_age Always - 17 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 I expect you have some type of connection issue - normally bad or loose cable.
January 31, 20179 yr Author The drive looks fine: I expect you have some type of connection issue - normally bad or loose cable. Hmm, interesting. Makes sense as I moved the server two weeks ago to the basement after getting a cat5e down there... Odd that it would be fine for a while then "act up." I'll check it now! Is there anything I should run after re-seating the connector? Parity check?
January 31, 20179 yr It is not odd at all. Very normal to have intermittent connection to a drive. If it was unplugged it would never have worked in the first place! Once a drive is "kicked", it is not going to be readmitted to the array without manual intervention. So rebooting is still going to show a red X. And you are not going to know if you fixed the problem. If you feel certain you have addressed any connection issue to all drives, you can rebuild it onto itself. You unassign the disk from the array (via the dropdown for the slot in unRAID GUI), select none. Start the array. The disk will be simulated using parity and all the other disks. Check to make sure that you can access the failed disk being simulated, and that the contents look normal. If what you saw simulated appears unformatted or is gibberish, DO NOT PROCEED. Post back for additional support. If the simulated disk looks good, now is an opportunity to copy anything priceless on that disk to your workstation for safe keeping. Chances of data loss is low at this point, but now is a good time to save off those baby pictures your wife will kill you for if you lost! When ready, stop the array, reassign the original disk to the slot, restart the array, and unraid will rebuild the disk. What you saw simulated is going to be written to the disk. Good luck!
February 6, 20179 yr Author Thanks bjp, after some delay I was able to verify the simulated contents and the dozen or so files I checked looked fine. Nothing "mission critical" was on the disk so that helps. Rebuild is going now, should be done later today. I'll post again with a final update.
February 7, 20179 yr Author Thanks bjp, after some delay I was able to verify the simulated contents and the dozen or so files I checked looked fine. Nothing "mission critical" was on the disk so that helps. Rebuild is going now, should be done later today. I'll post again with a final update. Rebuild was a success. No errors. Running another parity check now, at 70% with no errors. Hopefully it was just a loose cable. When I opened up the case I took the time to blow out all the dust and re-seat all the HDD cables. Thanks again!
February 9, 20179 yr Glad your back up and running. Consider locking cables and drive cages! Enjoy your array.
Archived
This topic is now archived and is closed to further replies.