did you patch the kernel 2.2.16 with the raid patch?
take a look at the file /proc/mdstat
if that file has the word 'inactive' in it, then you need to patch your
kernel.
look at www.redhat.com/~mingo/
for patches.
allan
Jordan Wilson <[EMAIL PROTECTED]> said:
> I have a few problems regarding my software RAID0 solution. I have two
> disks, hdb and hdd, on a raid0 array. Everything was working fine until I
> upgraded my kernel (from 2.2.12 to 2.2.16). Yes, support for RAID is
> compiled in the kernel. On bootup, I get :
>
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> EXT2-fs error (device ide1(22,1)): ext2_check_blocks_bitmap: Wrong free
> blocks count for group 888, stored = 7613, counted = 7901
> EXT2-fs error (device ide1(22,1)): ext2_check_blocks_bitmap: Wrong free
> blocks count in super block, stored = 1672643, counted = 1672931
> Oops ! md0 not running, giving up !
> Bad md_map in ll_rw_block
> EXT2-fs: unable to read superblock
> Oops ! md0 not running, giving up !
>
> and I am dumped to a maintenance shell. When I try and manually start the
> raid, I get the error
>
> [root@****** /etc]# /sbin/mkraid /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdb, 12714912kB, raid superblock at 12714816kB
> /dev/hdb appears to contain an ext2 filesystem -- use -f to override
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> The above is with persistent-superblock set to one. When I set it to 0, I
> get the following :
>
> [root@***** /etc]# /sbin/mkraid /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
>
> The contents of my /etc/raidtab :
>
> raiddev /dev/md0
> raid-level 0
> nr-raid-disks 2
> persistent-superblock 1
> chunk-size 4
>
> device /dev/hdb
> raid-disk 0
> device /dev/hdd
> raid-disk 1
>
> I am using mkraid version 0.90.0
>
> Sorry for the long message, but if you can help at all, I would appreciate
it.
>
> Thanks,
> Jordan
>
--
