- Joined
- Jun 11, 2010
- Messages
- 6,849
- Location
- Powhatan, Virginia, United States
- Tagline
- WassupYa Mang?
So I thought with all the extra HD's I had acquired recently that I would turn on my motherboard's RAID feature. I have four HD's, 2 that are 1TB and another 2 that are 320G. So for the 1st two I "mirrored" them, which is when RAID takes two disks and keeps a complete copy of the data sync'd between the two,( so if one fails....). The last 2 I did a "stripe" which is basically splits the data between the two drives - theory behind that is it should take half as long to read/write since each disk has half of the "task".
I even made a slipstream windows 7 install that included the RAID drivers, so that I can do a full OS install on the raid "array" (that worked GREAT btw... ).
But... and this is probably why I did this before, and then promptly UNDID it, the so-called RAID I have isn't really a hardware-based process. Instead of a "proper" RAID controller that would normally do the needed processing outside and unknown, this (and probably most "consumer" level RAID-capable motherboards) type of RAID uses the main CPU for it's processing. The end result is any time I am doing anything halfway disk intensive (yeah, even listening to a FLAC or two), I get a good amount of CPU drain. Kills me... bummer..
Soooo... now the trick is to un-do it all. Which really IS a trick because there's no way to get rid of the RAID arrays without losing the data - at least with my motherboard there is not.
I gotta plan tho... I still have a few more HD's spare that can get me outta this mess. Then I'll use one or two for backup purposes and keep my backups manual.
I even made a slipstream windows 7 install that included the RAID drivers, so that I can do a full OS install on the raid "array" (that worked GREAT btw... ).
But... and this is probably why I did this before, and then promptly UNDID it, the so-called RAID I have isn't really a hardware-based process. Instead of a "proper" RAID controller that would normally do the needed processing outside and unknown, this (and probably most "consumer" level RAID-capable motherboards) type of RAID uses the main CPU for it's processing. The end result is any time I am doing anything halfway disk intensive (yeah, even listening to a FLAC or two), I get a good amount of CPU drain. Kills me... bummer..
Soooo... now the trick is to un-do it all. Which really IS a trick because there's no way to get rid of the RAID arrays without losing the data - at least with my motherboard there is not.
I gotta plan tho... I still have a few more HD's spare that can get me outta this mess. Then I'll use one or two for backup purposes and keep my backups manual.