burnaby_boy

Thanks so much for your prompt reply. I'll upgrade to 4GB of RAM and try updating again.

I attempted to update Unraid from 6.9.2 to 6.11.3 using Update in the Tools section. A popup window opened showing the progress of the download and when it reached about 70% it stopped and showed "download failure (File I/O error)". I have successfully used this update method in the past, but it doesn't seem to be working now. I'd certainly appreciate some help with this issue. The diagnostics file is attached. media-diagnostics-20221112-1029.zip

Sorry, upon further reading, I realized that I neglected to install the Unassigned Devices app in advance of Unassigned Devices Preclear.

I am running Unraid 6.9.2. After uninstalling the old preclear plugin and rebooting the server, I attempted to install the Unassigned Devices Preclear app. When I clicked on the install button a popup appeared saying "Requirements not met - The requirements for this upgrade have not been met on your system". Any ideas as to what this means? Thanks

The PSU's in both computers, that this HDD has been connected to, both seem to be sound. In the main unRaid unit (using a Corsair TX650W PSU) there are 11 other HDD's that seem to be free of the issues that this one has. In terms of vibration, when it was a part of the main array it was secured using silicone grommets. As you suggest, I will RMA, but include a note mentioning the continual sectors pending re-allocation. Thanks again for the assistance. Cheers

I ran preclear 2 more times - on the first, the current pending sectors dropped by one, but then this is what I got on the second: ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 96 --- 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 132 63c63 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5682 --- 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5683 65c65 197 Current_Pending_Sector 0x0032 200 197 000 Old_age Always - 9 --- 197 Current_Pending_Sector 0x0032 200 197 000 Old_age Always - 46 ============================================================================ It seems to be getting worse. Do I just keep running preclear until the drive fails? - and then RMA it? Cheers

OK, well I will try a couple more rounds with preclear and see what the results are. Thanks again for your analysis.

Thanks for the feedback, Joe. It's a relatively new WD 1.5TB EARS (jumpered). Sounds like I should start an RMA. I certainly wouldn't feel comfortable putting it back in the array.

Greetings, Last week I started to get errors on one drive in the array. There were no errors in the parity check, but the drive itself was showing errors - 67 and then 98. I replaced the drive with a new one and the data was rebuilt successfully. I put the questionable drive in an test unRaid server and did a preclear. These are the results: ============================================================================ 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 42 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 78 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5673 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5674 197 Current_Pending_Sector 0x0032 200 197 000 Old_age Always - 10 197 Current_Pending_Sector 0x0032 200 197 000 Old_age Always - 1 ============================================================================ Do I have any reason to be concerned? Cheers