Anesthaesia Posted June 17, 2016 Share Posted June 17, 2016 Hi All, I recently posted about a parity drive that developed errors and went offline. I have replaced this and all is working fine, however I would like to try and clear the old disk and see what errors it has. I have run the preclear script using -A both with and without the jumper installed but each time it ends with the following: ================================================================== 1.6 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 10:46:23 ========================================================================1.6 == == SORRY: Disk /dev/sde MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.6367e-05 s, 0.0 kB/s 0000000 root@unRAID:/boot# Each time the server needs to be restarted to bring the disk back online. I have read related posts about the message "SORRY: Disk /dev/sde MBR could NOT be precleared" which state to check hardware connections and server memory. I have been unable to find any hardware issues. I precleared the new disk without issues a few days ago - 2 runs, both successful. Could anyone guide me on what I can do to clear this or run smart checks to see what state the disk is in? Regards, D Quote Link to comment
JorgeB Posted June 17, 2016 Share Posted June 17, 2016 http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report Quote Link to comment
Anesthaesia Posted June 17, 2016 Author Share Posted June 17, 2016 I've run a short SMART test and following the wiki guide it seems there are some attributes that are indicating the drive has issues. Reallocated_Sector_Ct & Current_Pending_Sector Could these be causing a preclear to fail? If it is not possible to run a preclear on the drive, do I need to do anything to return it to a "Windows" compatible state, or simply format it in a Windows PC? If the drive is faulty I will use it for non-critical data following a format. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 162 162 051 Pre-fail Always - 64682 3 Spin_Up_Time 0x0027 253 169 021 Pre-fail Always - 1016 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1601 5 Reallocated_Sector_Ct 0x0033 194 194 140 Pre-fail Always - 123 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 038 038 000 Old_age Always - 45460 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 114 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 63 193 Load_Cycle_Count 0x0032 129 129 000 Old_age Always - 213692 194 Temperature_Celsius 0x0022 123 107 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 170 170 000 Old_age Always - 30 197 Current_Pending_Sector 0x0032 198 197 000 Old_age Always - 976 198 Offline_Uncorrectable 0x0030 197 197 000 Old_age Offline - 1180 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 174 166 000 Old_age Offline - 7194 Quote Link to comment
JorgeB Posted June 17, 2016 Share Posted June 17, 2016 Too many pending sectors, disk is done, to use in Windows you need to go to disk management, if there is one delete the existing partition, create a new one and format it, but doubt you'll be able to get any use of such a damage disk. Quote Link to comment
testdasi Posted June 17, 2016 Share Posted June 17, 2016 ... If the drive is faulty I will use it for non-critical data following a format ... 5 Reallocated_Sector_Ct 0x0033 194 194 140 Pre-fail Always - 123 ... 197 Current_Pending_Sector 0x0032 198 197 000 Old_age Always - 976 ... My approach (which may or may not be too drastic) is to replace any drive with more than 0 reallocated sector as soon as possible. Reallocation means something is wrong with the original sector => I can't trust that my data won't be corrupted. In your case, 123 suggests the drive is dying. I also think any data that is non-critical should be deleted. Storing it on a failing drive is defeating the purpose because you might not be able to access it the next time you need. And if you actually will never need it then what's the point of keeping. Quote Link to comment
Fireball3 Posted June 17, 2016 Share Posted June 17, 2016 The preclear script is no diagnosis tool. It's more kind of a stress-test/endurance tool. If you have a drive, that is not passing the preclear you should revert to the vendor specific testing tools. I got a pair of drives a couple of weeks ago and one of them quit with exactly the same message during the preclear. It was a WD drive. DataLifeguard didn't pass even the short test. No need to waste more time with that thing. RMA'd it. Quote Link to comment
Anesthaesia Posted June 17, 2016 Author Share Posted June 17, 2016 Thanks for the reply guys - I guess the drive served its purpose running 24/7 for 5+ years. Quote Link to comment
RobJ Posted June 17, 2016 Share Posted June 17, 2016 I have run the preclear script using -A both with and without the jumper installed but each time it ends with the following: ================================================================== 1.6 = unRAID server Pre-Clear disk /dev/sde That's a really old Preclear script, version 1.6. You really should be using the latest, 1.15. But I hope you will also consider Upgrading to UnRAID v6. 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.