Quote:
Originally Posted by TeMpUs_FuGiT
I am going to end up reconfiguring my RAID. And doing a complete reinstall of both xp 64 and debian amd 64 bit
|
Did you look in /dev/mapper
That's where they usually show up for RAID or LVM...
FYI, unless you purchased a motherboard that has an actual RAID controller with it's own processor and RAM ($500 at least), it's a pseudo-software RAID. All it really does is hook into the disk BIOS and map disk sectors alternately on one drive or the other. In linux you can get better performance using a Logical Volume with striping because LVM can manage the disk. With a motherboard hardware switch it can't anticipate disk needs.
Bottom line on RAID, if you expect better performance from an onboard RAID controller, don't. They aren't any faster. If you want security, it's a dubious proposition for the reasons you've already run into.
An actual RAID controller is a complete disk subsystem with an embedded processor, it's own RAM (16mg to gigabytes) and firmware. As a result it can cache local disk writes very quickly to it's ram, then prioritize disk writes to they are efficient and help prevent fragmentation, plus it can keep more data in memory, thus allowing it to manage the overall disk writes so they are far more efficient. A motherboard chip is not an raid controller, it's a RAID partitioner (for lack of a better word).
A real RAID controller is actually a completely separate computer mounted on a card that simulates an actual hard drive. It's faster because it has a separate interface for each device, IDE does not (single cable, shared bus). SATA has the potential to be fast if it's not bottlenecked by a stupid on-board $Vehicle$ $for$ $Profit$ to dupe you into buying the board.
See:
here for an example of an actual RAID controller.
-tom