<quote who="Cameron Kerr">
> mdadd complains about the individual partitions, saying that the
> device does not exist (_not_ `no such file or directory', that's
> simple to fix).
my experience with software raid5 on linux (2.2.19+raid 0.90
patches) is that raid5 seems to require the ENTIRE disk. only
1 partition, and you cannot make partitions of the array
(e.g. /dev/md0p1) even though fdisk allows you do, there aren't
the major/minors to format them(/dev entries).
i only have 1 system in software raid 5 and it looks like:
i tried several times to get it to partition but it did
not come out right, so i gave up and just gave it the whole
disks. i had to install another disk for my swap partition.
this is contrary to raid0 and raid1 which i have used
several times and work fine with partitions.
so, I have 1 26GB / partition(/dev/md0) and my /boot
partition is on the other disk (/dev/sda). as is my
swap partition(1.1GB swap partition).
thats my experience ....
- From: Cameron Kerr <firstname.lastname@example.org>