December 14, 201213 yr Didn't know where else to post this. But I wanted to thank you for your hard work. Past week I have noticed a drive in my array degrading. Throwing errors and pending relocated sectors increasing. This is my first drive failure in 25+ years of playing with PCs. I went out and bought a new drive. Took out the bad drive (WD-EARX) and put in the new one (SEAGATE). (all the time feeling sick to my stomach I could lose data by removing this drive). Crossed my fingers, booted up the server. Headed over to my PC, hit up the Web Interface and saw the blue ball next to the drive. I then nervously clicked Start Array. The ball went orange and I saw Rebuilding Array. Sigh of relief, but still nervous as to another drive failing during the rebuild. As of this morning, new drive was rebuilt (11 hours). No issues. Thank you Lime Tech!!!! So glad I found you. I look forward to Official Release of 5. I really want some 3TB+ drives. Cheers! - Chuck
December 14, 201213 yr Glad it worked so well for you, and I hate to throw a wet rag on you, but I have to. You made the assumption the new drive was good, and probably 90% of the time, that's fine. However, new drives have a bad habit of failing early in life, and unraid uses 100% of the drives capacity during rebuild events, so best practice is to thoroughly thrash a new drive before adding it to the array. Joe L's preclear script does a pretty good job at weeding out early failure drives, so even though clearing a drive isn't necessary when replacing a current array slot, it's still a good idea to run a couple preclear passes before trusting a new drive with your data. If you can afford it, I'd pick up another new drive the same size as your parity drive, and run 2 or more preclear passes on it and put it aside for the next drive failure. You also need to run a non-correcting parity check to make sure the new rebuilt disk can be read properly.
December 17, 201213 yr Author Actually. I just failed to mention the pre-clearing. It was done. Always pre-clear new drives. Thanks for the tip on Non-Corrective parity check.
Archived
This topic is now archived and is closed to further replies.