If I might comment on the RAID topic, be very wary of where you place your confidence. After multiple failures on a variety of "SOHO" type RAID implementations (low/moderate cost cards, motherboard built-in offerings, etc.) I've written them off and use non-realtime disk mirroring. As an added bonus you get some degree of versioning protection that way.I wouldn't use any raid level but MIRROR, for a couple of reasons:
The problem with the budget RAID solutions is that they won't rebuild. The failures I've had in RAID1 configs made the mirror drive unreadable. Since moving to a multilayer asynchronous drive mirror solution my file servers at work have been bulletproof. And from skimming Google's whitepaper on data protection they use a similar system.
- RAID-5 rebuilds are expensive, and might take an additional disk out when rebuilding. You can still only lose one disk without losing all your data.
- With non-mirror RAID levels, it can be difficult moving from one controller type to another (as in, virtually impossible).
- With mirroring, you can keep running from a single drive, if you want/need to.
for MIRRORing, just about any solution will work (100% software done on the OS, half-assed "hardware" solutions like onboard and most cards, and "real hardware"). If you're going to buy a "hardware raid" card, either get one with cache memory and a batteri-backup unit, or don't bother at all. And since you shouldn't be running the fancier RAID modes, don't bother

Now our enterprise level RAID systems recover well, especially when configured with a hotspare. The only RAID system I'd consider at home now though is a Drobo.What does drobo run internally? Linux w/kernel software raid?



- carpe noctem









