Hello guys, Tuesday, July 2, 2013, 5:53:04 PM, Nick Holland wrote:
NH> "RAID5 rebuild is still not there" -> there's no RAID5 rebuild. I'm not NH> sure how to make it more clear... NH> Ok, let's try this... NH> Today, you take four 1TB disks, and make a 3TB RAID5 volume. You can do NH> that. Works great. NH> Now, a lot of people might call this "Job Done". Not me. The point of NH> RAID isn't to build complicated systems, but to have the system keep NH> your butt out of the fire when things go wrong. NH> Next month, one of those drive fail. That's ok, RAID5 is designed to NH> keep your data usable with one drive down. THAT is the point of RAID. NH> You pat yourself on the back and say, "I'm glad I am using RAID5". NH> You replace the failed drive and... NH> ... NH> um... now what? NH> You have a three drive degraded RAID5 system with no remaining NH> redundancy...and a new drive that is currently unused. You have no NH> ability to rebuild the function of the failed drive into the new NH> drive...because the RAID5 rebuild is not there. NH> Oh, poo. NH> Your options? Well, NH> * you can build a NEW array on other disks (hope you have enough ports NH> to plug them into), copy the data from the old one to the new one NH> * you can hope your backup system is perfect, and rebuild the entire NH> array and reload from backup NH> * you can hope a second drive doesn't fail in your array... for the life NH> of the system. NH> Not much else I can think of. If the softraid is so raw yet, why the old good RAIDFrame was removed starting the 5.2? It works just fine for me. Big volumes rebuilds take a long while, but it's something working. -- Best regards, Boris mailto:bo...@twopoint.com
