cat /proc/mdstat does it for me.
Code:
[root@qpak mnt]# cat /proc/mdstat
Personalities : [raid0] [raid1]
md0 : active raid0 hdb1[1] hda2[0]
154207744 blocks 256k chunks
md1 : active raid1 sda1[0] sdb1[1]
104320 blocks [2/2] [UU]
md2 : active raid1 sda2[0] sdb2[1]
156183808 blocks [2/2] [UU]
unused devices: <none>
This shows a RAID 0 array (striped) using 2 IDE hard drives and two RAID 1 arrays (mirror) using 2 SATA drives.
If you want to dig further then fdisk -l will show how the drives are partitioned:
Code:
[root@qpak mnt]# fdisk -l /dev/hda
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 9612 77103967+ fd Linux raid autodetect
[root@qpak mnt]# fdisk -l /dev/hdb
Disk /dev/hdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 9599 77103936 fd Linux raid autodetect
/dev/hdb2 9600 9729 1044225 82 Linux swap
[root@qpak mnt]# fdisk -l /dev/sda
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 fd Linux raid autodetect
/dev/sda2 14 19457 156183930 fd Linux raid autodetect
[root@qpak mnt]# fdisk -l /dev/sdb
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104384+ fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sdb2 13 19457 156183967 fd Linux raid autodetect
[root@qpak mnt]#