RAID Controller possible strange issue

[musicmag.ca]

Hi, I have a Silicon Image Inc. PCI0680 Ultra ATA-133 RAID controller with 2x80 gig drives attached to the same IDE cable.

When my box boots I see the RAID bios and have set for the two drives to be a mirrored set, all looks good there.

When I get into KDE and fire up qtparted, I see the two drive separatelly.

example:
hda(primary)
hdb(80gig #1)
hdc(80gig #2)

I would have thought that I would only seen one drive in here... Does this mean that Linux is not understanding the mirrored set? I checked in kinfocenter and I do see that the raid controller has been installed. thank you in advance.

[nlkrio]

your Silicon Image Inc. PCI0680 Ultra ATA-133 RAID controller is not a real hardware raid controller,its a software raid controller.Linux and fedora do not need software raid controllers in order to provide raid they have their own raid software.For more read
http://linux.yyz.us/sata/faq-sata-raid.html

[musicmag.ca]

for real? bummer...

[nlkrio]

visit http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-software-raid.html
to setting raid is almost the same with fc4

[musicmag.ca]

ok so if I am following correctly, if i install dmraid I should be able to use the controller? I attempted an in stall but i get an error


[root@localhost Desktop]# rpm -ivh dmraid-1.0.0.rc10-1.i386.rpm
error: Failed dependencies:
libdevmapper.so.1.02 is needed by dmraid-1.0.0.rc10-1.i386
libdevmapper.so.1.02(Base) is needed by dmraid-1.0.0.rc10-1.i386
[root@localhost Desktop]#


so then I try to do this...


[root@localhost Desktop]# rpm -ivh device-mapper-1.02.02-3.2.i386.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.4) is needed by device-mapper-1.02.02-3.2.i386
[root@localhost Desktop]#


Then I am stuck again cause I can't seem to find an rpm for libc.so.6(GLIBC_2.4)

[musicmag.ca]

ok so that is because I was trying to install something for FC5.... fun.
I have found and downloaded dmraid-1.0.0.rc8-FC4_5.i386.rpm, when I ran it i got an already installed message... which i suppose is good. Now I am going to try to figure out how to use it :-) from what I have read it updates my kernel?