Search the Community

Hope this makes sense... 2 days ago StableBit Scanner and WHS 2011 reported that a drive was failing....and a brand new 6TB WD Red drive of all things! So I shutdown the server, physically removed the drive and backed up the data to another 6TB drive. I mostly backed up the Server Folders that I don't have duplication turned on for - as the duplicated server folders should be ok (dupe copies on the other drives) - correct? So I was all set to add the NEW 6TB drive into the pool and then follow the instructions in this posting: http://wiki.covecube.com/StableBit_DrivePool_Q4142489 to move the backed up data back into the pool. If I understand that process, once I do that, all of the non-duplicated files should be back in the pool and DrivePool will do it's thing to re-populate the new drive with dupe copies of anything that was on the failing drive.... But then it hit me - I haven't removed the failing drive from the pool yet...it still shows as "missing" - so I'm guessing DrivePool won't actually start duplicating the dupe copies of stuff that was in duplicated folders on the missing drive until I remove it from the pool via the dashboard? I don't want to screw this up - so what is the proper approach for this scenario I have? Here's the facts summarized: * 6TB failing drive ("failing") physically removed from the server and non duplicated folders backed up to a new 6TB drive ("new") * NOTE: I also backed up some other "more critical" folders that ARE in fact already setup for duplication in the pool - just in case (probably didn't need to do this - but figured that if I had as much of the duplicated files backed up, I could use the instruction in the link above to move the data from the backed up folders back into the pool once that "new" disk was added, and save DrivePool some work/time - is that a correct assumption? * I have already added the "new" drive to the pool (ne with the backed up files noted above) and was about to go through the instructions in the link above to move that data back into the pool * I still haven't removed the "failing" drive from the DrivePool yet If you folks can please advise on the best way to approach this - that would be most appreciated. Let me know if anything is not clear LATE ADDITION: - Forgot to mention I'm running WHS 2011 on an HP N40L. AND since I had to do some work on this drive issues, I decided to take the time to swap out my external drive enclosure, install a NEW PCIe card (6GB/s eSATA card with 4 ports) and also upgrade my memory (none of which has anything to do with the drives) - BUT - I now have the origirnal eSATA port on my N40L free - as well as a second external eSATA port - So it just dawned on me that I could drop the "failing" drive in a single external drive enclosure I have - plug it into one of the free eSATA ports - and then REMOVE the "failing" drive in the Dashboard - and let DrivePool do it's thing to migrate the data over to the "new" drive I added. I only have about 2TB of data on the "failing" drive - and have about 3TB free on the "new" 6TB dirve (rest is the backed up data in a separate folder NOT in the "ServerFolder" - so not in the pool. So enough space to let DrivePool do it's thing - and worst case if something doesn't get pulled off the failing drive - I have the backed up data. So this would seem to be the best approach based on what I've read - correct? If not - let me know... And then I need to update my version of DrivePool ;-)