>A. Khattri wrote:
I think you need to heed my earlier advice (which was to read the RAID HOWTO docs at tldp.org) so you understand what the different RAID levels mean.
I've read the docs, and there's nothing new for me; I just knew the meaning of "RAID levels". The raid and relative partitions were created by Windows using the Sil3512 driver (the Silicon SATA-RAID controller is integrated in my MB); before installing Winsucks I simply configured the Raid in the Bios of that controller (i.e. not in the Bios of the MB) and used windows to make the partition table. With dmraid and devfs there weren't problems in detecting the raid and creating the right devices, but I suppose that with udev dmraid works no more, because it did not create the devices. I've posted my "fdisk -l" output, and I know there's something wrong about it because simply the sizes of partitions doesn't match; I repeat, dmraid was able to build the raid devices in the right way, why I can't do this using mdadm?
This is the output of "dmraid -s": *** Set name : sil_afabcfabdecgb size : 796588032 stride : 32 type : striped status : ok subsets: 0 devs : 2 spares : 0 This means dmraid detect the raid in the right way. Output of "dmraid -ay -t": sil_afabcfabdecgb: 0 796588032 striped 2 32 /dev/sda 0 /dev/sdb 0 -- gentoo-user@gentoo.org mailing list
