jp777cmoe Posted June 18, 2011 Share Posted June 18, 2011 Hi, I'm in the process to make a unRAID server. I just bought two WD20EARS because the WD20EADS seems discontinued. There is data on the WD20EADS but the WD20EARS are brand new. My question is: Should I put a jumper on those two WD20EARS? I'm concerned because the EADS doesn't use the AFT. Thanks, Jp Quote Link to comment
wsume99 Posted June 18, 2011 Share Posted June 18, 2011 No jumper needed on EARS drives if you are using unRAID 4.7 or newer. Just make sure that you change the Default partition format option on the Settings page in the unRAID webGUI to MBR: 4k-aligned. And if you are going to preclear your disks (which I HIGHLY recommend) make sure you download the newest version of Joe L's preclear script and use the -A option as well to ensure that they are 4k-aligned. Quote Link to comment
jp777cmoe Posted June 19, 2011 Author Share Posted June 19, 2011 Should I just use my WD20EADS as parity drive then? Quote Link to comment
wsume99 Posted June 19, 2011 Share Posted June 19, 2011 Assuming you do what I said above, it won't matter where you use the EARS or EADS disks - they will all basically perform the same. If you want to keep the data on the EADS drive then I would use the two new EARS drives first, one as a data drive and the other as parity. Then you can move the data off the EADS drive onto your parity-protected 2TB unRAID array. Once you've got the data on the array then you can preclear the EADS drive (which will erase all the data on it) and then add it to the array as a second data disk. That would bump the capacity of the array up to 4TB. Quote Link to comment
jp777cmoe Posted June 19, 2011 Author Share Posted June 19, 2011 Alright, thanks for your help! Quote Link to comment
jp777cmoe Posted July 11, 2011 Author Share Posted July 11, 2011 I haven't got the time to test it but I'm about to. One more thing: The Joe L's preclear script is ran before the format? That is if the array isn't present I suppose? 1- run script on both drives 2- add the two WD20EARS to the array 3- transfer data from WD20EADS to WD20EARS then pre clear the WD20EADS to add it to the array Is this right? Quote Link to comment
wsume99 Posted July 12, 2011 Share Posted July 12, 2011 Yes - except depending on the results of #1 you may not want to proceed to #2. Quote Link to comment
jp777cmoe Posted July 12, 2011 Author Share Posted July 12, 2011 What could possibly happen? Both drives are brand new Quote Link to comment
wsume99 Posted July 12, 2011 Share Posted July 12, 2011 Just because the drives are brand new does not mean they are good drives. I have had several brand new drives that I had to send back for replacement. One of the drives would not even complete the preclear operation because it was generating so many errors. Take a look at this thread: Preclear.sh results - Questions about your results? Post them here. If you read through all 71 pages you'll see that there are lots of users who get new drives that turn out to be bad or at least they are highly suspect. Quote Link to comment
SSD Posted July 12, 2011 Share Posted July 12, 2011 Drives tend to fail early in their life or late in their life. The plotted curve looks something like a bathtub, and often referred to as such. Preclear helps induce some of the early failures such that they do not happen after being put in service. But I'm not sure there isn't more going on. It could be that the preclear is actually healthy for the drive, similar to the break-in period on a new car. This is not a fact, but anecdotal evidence seems to point to more failures on new drives added directly to the array than drives failing in preclear. Of course this could just be Murphy at work. Quote Link to comment
jp777cmoe Posted July 13, 2011 Author Share Posted July 13, 2011 I'll disable the Intellipark on the drives then test them. I will post back with the results here... I'm afraid thought. Anyway how often do you need to run the script to check for reallocated sectors? Quote Link to comment
jp777cmoe Posted July 18, 2011 Author Share Posted July 18, 2011 I ran the test on the first hard drive (WD20EARS). Still waiting on the second one because I don't have the camera right now. http://i394.photobucket.com/albums/pp27/jp777cmoe/IMG00125-20110714-2028.jpg Quote Link to comment
mr.sparkle Posted July 19, 2011 Share Posted July 19, 2011 Drives tend to fail early in their life or late in their life. Every drive fails precisely at the end of its life, no? I don't follow. Quote Link to comment
Joe L. Posted July 19, 2011 Share Posted July 19, 2011 Drives tend to fail early in their life or late in their life. Every drive fails precisely at the end of its life, no? I don't follow. That is why some PC parts have lifetime warranties. They are guaranteed to work until they no longer work. Quote Link to comment
dgaschk Posted July 20, 2011 Share Posted July 20, 2011 I'll disable the Intellipark on the drives then test them. I will post back with the results here... I'm afraid thought. Anyway how often do you need to run the script to check for reallocated sectors? Run it every day. Just kidding. The script takes more than a day to run but that is not the real issue -- the script writes zeros to your drive! Get a SMART report to check for reallocated sectors. smartctl -a -d ata /dev/sdX Where X is the drive letter of your drive. Quote Link to comment
jp777cmoe Posted July 20, 2011 Author Share Posted July 20, 2011 I used /dev/sda. I only have one HD connected to the motherboard. Quote Link to comment
jp777cmoe Posted July 24, 2011 Author Share Posted July 24, 2011 I'll disable the Intellipark on the drives then test them. I will post back with the results here... I'm afraid thought. Anyway how often do you need to run the script to check for reallocated sectors? Run it every day. Just kidding. The script takes more than a day to run but that is not the real issue -- the script writes zeros to your drive! Get a SMART report to check for reallocated sectors. smartctl -a -d ata /dev/sdX Where X is the drive letter of your drive. I ran smartctl -a -d ata /dev/sdX for a drive. Here is the result. The wierd thing is that it ran for like 1 second... smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA2989395 Firmware Version: 51.0AB51 User Capacity: 2,000,397,852,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Jul 24 13:49:10 2011 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enabled. === START OF READ SMART DATA SECTION === 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: (36000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 253 253 021 Pre-fail Always - 958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 11 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 100 100 000 Old_age Always - 232 10 Spin_Retry_Count 0x0032 100 253 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 - 9 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 22 194 Temperature_Celsius 0x0022 114 111 000 Old_age Always - 36 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Quote Link to comment
dgaschk Posted July 28, 2011 Share Posted July 28, 2011 That looks fine. It is usually run when the drive is having problems. Quote Link to comment
jp777cmoe Posted July 30, 2011 Author Share Posted July 30, 2011 That looks fine. It is usually run when the drive is having problems. You mean the script usually runs when the drive has problems? Quote Link to comment
dgaschk Posted July 30, 2011 Share Posted July 30, 2011 You run smartctl. It is not a script. The script is pre-clear. 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.