Very Computer

> Interesting. I didn't know one could have a raides boot these days. Is
> it raid1?

> :    However, after compiling 2.2.13, mkinitrd, lilo and such, it paniks
> : at the following point:

> Probably a bug that should be reported! I am also playing with the new
> raid patches (on 2.2.10 - the unpatched kernel seems to have been
> faulty on raid1).

> : RAMDISK: Compressed image found at block 0
> : VFS: Mounted root (ext2 filesystem).
> : Loading raid1 module
> : raid1 personality registered

> Ah yes.

> : Bad md_map in ll_rw_block
> : EXT2-fs: unalbe to read superblock
> : Kernel panic: VFS: Unable to mount root fs on 09:00.

> : The kernel is based on the standard 2.2.13 source with raid0145-
> : 19990824-2.2.11 applied (I get the same error message without).

> I have 2.2.10 and that patch.

> : I did a 2.2.12 recompile just to see and it worked fine (no error).

> Excellent. Prima facae bug. Report it.

> Peter

> I am not sure what the exact workaround is for a non autodetecting
> kernel. One probably can still get it to work using the right boot
> options..

> > Hi.

> >    I am trying to compile the 2.2.13 kernel on a machine that is
> > running software raid and has / mounted to a raid device. The
machine
> > is basically a vanilla RedHat 6.1 install. Two disks (IBM 13 GB)
with
> > various raid partion. /boot is not 'raided'. Everything runs fine
with
> > 2.2.12.

> >    However, after compiling 2.2.13, mkinitrd, lilo and such, it
paniks
> > at the following point:

> > RAMDISK: Compressed image found at block 0
> > VFS: Mounted root (ext2 filesystem).
> > Loading raid1 module
> > raid1 personality registered
> > Bad md_map in ll_rw_block
> > EXT2-fs: unalbe to read superblock
> > Kernel panic: VFS: Unable to mount root fs on 09:00.

> > The kernel is based on the standard 2.2.13 source with raid0145-
> > 19990824-2.2.11 applied (I get the same error message without).

> > I did a 2.2.12 recompile just to see and it worked fine (no error).
> > I mounted both initrd's and don't see a difference (2.2.13 has the
> > newer raid1.o of course).

> > Any help?

> With the stock 2.2.13 kernel there is no option of auto-
> detect RAID.

> thanks,

> geoff nordli

> > I found the solution myself...
> > I used 'make menuconfig' to configure the kernel. I did select the
> > 'Autodetect RAID option'. However, somehow it did not work. I had to
> add
> > a line '#define CONFIG_AUTODETECT_RAID' to
> > /usr/src/linux/drivers/block/md.c to make things work. This is the
> only
> > file that uses the option. The raid patch is still necessary to get
> the
> > version of md.c that includes autodetect raid..

> > I am not sure what the exact workaround is for a non autodetecting
> > kernel. One probably can still get it to work using the right boot
> > options..

> > > Hi.

> > >    I am trying to compile the 2.2.13 kernel on a machine that is
> > > running software raid and has / mounted to a raid device. The
> machine
> > > is basically a vanilla RedHat 6.1 install. Two disks (IBM 13 GB)
> with
> > > various raid partion. /boot is not 'raided'. Everything runs fine
> with
> > > 2.2.12.

> > >    However, after compiling 2.2.13, mkinitrd, lilo and such, it
> paniks
> > > at the following point:

> > > RAMDISK: Compressed image found at block 0
> > > VFS: Mounted root (ext2 filesystem).
> > > Loading raid1 module
> > > raid1 personality registered
> > > Bad md_map in ll_rw_block
> > > EXT2-fs: unalbe to read superblock
> > > Kernel panic: VFS: Unable to mount root fs on 09:00.

> > > The kernel is based on the standard 2.2.13 source with raid0145-
> > > 19990824-2.2.11 applied (I get the same error message without).

> > > I did a 2.2.12 recompile just to see and it worked fine (no
error).
> > > I mounted both initrd's and don't see a difference (2.2.13 has the
> > > newer raid1.o of course).

> > > Any help?

> Sent via Deja.com http://www.deja.com/
> Before you buy.