I had this same problem a week ago. You still need to apply the appropriate
patches to the kernel to get things to work properly. The latest one from
ftp.kernel.org/pub/linux/daemons/raid/alpha/raid0145-19990108-2.2.0-pre5.gz
should apply. I haven't tried patching 2.2.0pre8 myself, but It patched
2.2.0pre7 OK with a bunch of offsets.
Question: Is there a set of raidtools which doesn't require patching of the
kernel? It would be VERY nice to either get these patches integrated into the
main kernel for 2.2.0 or at least get some docs in there.
-Dave
On 20-Jan-99 Danny Yee wrote:
> I've set up a 2.2.0pre8 system (with raid in the kernel) and built and
> installed raidtools-0.90. When I run mkraid, I get the follow
> results. (I've tried this for raid-1 and raid-5 devices, too.)
>
> [root@tekelili]# mkraid /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/sdb1, 1028128kB, raid superblock at 1028032kB
> disk 1: /dev/sdc1, 1028128kB, raid superblock at 1028032kB
> disk 2: /dev/sdd1, 1028128kB, raid superblock at 1028032kB
> disk 3: /dev/sde1, 1028128kB, raid superblock at 1028032kB
> disk 4: /dev/sdf1, 1028128kB, raid superblock at 1028032kB
> mkraid: aborted
>
> My /etc/raidtab looks like:
>
> raiddev /dev/md0
> raid-level 0
> nr-raid-disks 5
> nr-spare-disks 0
> chunk-size 64
>
> device /dev/sdb1
> raid-disk 0
>
> device /dev/sdc1
> raid-disk 1
>
> device /dev/sdd1
> raid-disk 2
>
> device /dev/sde1
> raid-disk 3
>
> device /dev/sdf1
> raid-disk 4
>
> Any hints?
>
> Danny.
