cantharides Posted July 13, 2011 Share Posted July 13, 2011 I've removed a 2TB WD20EARS drive from my windows Xp machine, removed the jumper and have precleared it for use in my unraid config, but got following error message: drive succesfully preceared 1 sector pending reallocation before preclear 1 sector pending reallocation after writing zero's and preclear process 0 sectors reallocated after preclear process I've repeated this step twice and the result stays the same I've read the topic on preclear process but hesitate to put it in my unraid machine. Can someone be clear at this as to use this disk or not and if usage is ok whether it should be safest to use it as parity or data disk ? Link to comment
lionelhutz Posted July 13, 2011 Share Posted July 13, 2011 Someone else had that happen a while ago. I can't recall the solution or if there even was a solution besides RMA'ing the drive. A forum search might get you the answer. Peter Link to comment
SSD Posted July 13, 2011 Share Posted July 13, 2011 I would not RMA a disk with one pending sector that held constant through 2 preclear cycles. Just monitor it as you do any disk. If you see the reallocated or pending counts creeping upward on each parity check, it's time to RMA the disk. Link to comment
cantharides Posted July 13, 2011 Author Share Posted July 13, 2011 OK, so I can use it then. But which option holds the least riks, use it as a data disk or as the parity drive ? I was hoping to use it as parity drive (cause it's a 64 MB cache drive), but I think data drive is safer (less rewrites to the disk) ? What I did'n try yet is to use the jumper and then preclear the drive with -A option. Is there anyway to see which sector is affected ? Link to comment
Joe L. Posted July 13, 2011 Share Posted July 13, 2011 OK, so I can use it then. But which option holds the least riks, use it as a data disk or as the parity drive ? I was hoping to use it as parity drive (cause it's a 64 MB cache drive), but I think data drive is safer (less rewrites to the disk) ? What I did'n try yet is to use the jumper and then preclear the drive with -A option. Is there anyway to see which sector is affected ? don't mess with the jumper. You might be able to run a "long" smart test and have it list the sector. Joe L. Link to comment
cantharides Posted July 14, 2011 Author Share Posted July 14, 2011 Ok, but how do can I run a "long" SMART report ? Link to comment
Joe L. Posted July 14, 2011 Share Posted July 14, 2011 Ok, but how do can I run a "long" SMART report ? If you know the linux device name, type: smartctl -t long /dev/sdX where sdX = your drive. Then, wait about 5 or so hours and then run smartctl -a /dev/sdX to get the output Joe L. Link to comment
cantharides Posted July 21, 2011 Author Share Posted July 21, 2011 Thx for the smart long test command (never used this before) . Smart test executed today in short these are the results: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY2623713 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: (0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (43980) seconds. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE DATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 3 Spin_Up_Time 0x0027 145 142 021 Pre-fail Always - 9750 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 537 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 099 099 000 Old_age Always - 746 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 - 19 192 Power-Off_Retract_Count0x0032 200 200 000 Old_age Always - 60 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3808 194 Temperature_Celsius 0x0022 122 104 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 327 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 12 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error So the test didn't report any errors though there is an extensive list of vendors smart attributes where 197 indicates "current pending sector : 1". Does ths mean anything, or can I simply use the disk since the has passed and no errors logged status ? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.