> > One quick question, did you patch the 2.2.16 kernel with:
> > http://people.redhat.com/mingo/raid-patches/raid-2.2.16-A0 ?
>
> No, but thank you very much!! I would like to know where you got
> that information. I snooped around and the most I could figure out
> is that the patches on kernel.org stop at 2.2.11. Even the raidtools
> pointer is dead in the kernel docs.
This is where I got it from:
http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/Software-RAID.HOWTO.html
It took me a while to find too. Look in "Introduction" for the link
Tamas.
> > > Hello.
> > >
> > > To start, I installed RedHat 6.1 with root on RAID1. /boot is non-RAID.
> > > It's using RedHat's 2.2.12-20 kernel which seems to have extra RAID stuff in it.
> > > RAID1 is actually built as a module so it loads an initrd that has only
> > > raid1.o, sh, and insmod in it.
> > >
> > > I tried to upgrade to 2.2.16 by building the proper RAID support but to no
> > > avail. Basically, it does not seem to autodetect the RAID devices. So, I read
> > > md.txt and it says I need to pass md=x,x,x,x,x but it doesn't work for RAID1.
> > > Well, I tried it anyway and it gets close but complains that the devices are
> > > not linear or striped. Well, duh.
> > >
> > > I'm left wondering why redhat's hacks to 2.2.12 have seemingly not made it into
> > > the kernel after all this time. Am I missing some obvious or obfuscated step?
> > > Are there any plans for RAID1 boot/autodetect support?
> > >
> > > I don't see us moving our production systems to 2.4 before the end of the year,
> > > so I don't care about 2.4's support. If there are no other plans to do this
> > > integration into 2.2 then I wouldn't mind spending a day or two patching in
> > > redhat's changes.
> > >
> > > Ideas?
> > >
> > > For shits and giggles, here is what I have experienced so far:
> > >
> > > RedHat 2.2.12 booting:
> > > md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
> > > md.c: sizeof(mdp_super_t) = 4096
> > > partition check:
> > > hda: hda1 hda2 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
> > > hdc: hdc1 hdc2 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 >
> > > autodetecting RAID arrays
> > > (read) hda5's sb offset: 524544 [events: 0000001f]
> > > (read) hda6's sb offset: 2097536 [events: 0000001f]
> > > (read) hda7's sb offset: 2097536 [events: 0000001f]
> > > (read) hda8's sb offset: 524544 [events: 0000001f]
> > > .
> > > .
> > > .
> > > (read) hdc10's sb offset: 7307392 [events: 00000008]
> > > autorun ...
> > > considering hdc10 ...
> > > (and so on... although I don't understand why the version number is 0.90.0)
> > >
> > >
> > > 2.2.16 booting:
> > > md driver 0.36.6 MAX-MD_DEV=4, MAX_REAL=8
> > > raid1 personality registered
> > > partition check:
> > > hda: hda1 hda2 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 >
> > > hdc: hdc1 hdc2 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 >
> > > Oops! md0 not running, giving up!
> > > hdc: hdc1 hdc2 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 >
> > > 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!
> > > Bad md_map in ll_rw_block
> > > isofs_read_super: bread failed, dev=09:00, iso_blknum=16, block=32
> > > kernel panic: VFS: Unable to mount root fs on 09:00
> > >
> > > --
> > > Robert Dale
> > >
> > > Digital Mission
> > >
> > >
> > >
> > >
> >
>
