Re: booting RAID partitions

Rob Hagopian (hagopiar@vuser.vu.union.edu)
Tue, 25 Aug 1998 16:21:25 -0400 (EDT)


RAID 1 shouldn't be too hard, if the first device doesn't work, just look
for the same kernel (same location) on the second/third/nth drive. RAID
0/4/5 are a bit tougher since you actually have to get the stripes from
each drive to assemble the kernel in memory. And that doesn't even include
having to recreate stripes if there's a drive failure... ugg...
-Rob

On Tue, 25 Aug 1998, Jeff Garzik wrote:

> Rob Hagopian wrote:
> > Yes, lilo can't read the kernel from more than one drive, but that's not
> > the issue. The problem was getting your root drive to be RAID, since you
> > needed /sbin/mdadd, /sbin/mdrun, /etc/mdtab, and possibly /sbin/ckraid to
> > make the RAID devices. Some of these were integrated into the kernel for
> > RAID 0/1 by passing kernel parameters, now it can be done for all RAID
> > devices.
> > Yes, you'll still need to put your kernels on a floppy or something.
>
> Being a lucky Alpha owner, I can add RAID1/5 boot support to MILO
> (hopefully!), which I can then blow into flashROM. Excellent solution
> for booting my future RAID1 system partition.
>
> Thanks for everything (especially the links in the other msg). This
> gives me something new to play with... :)
>
> Jeff
>
>
>
>
> > On 24 Aug 1998, Michael Shields wrote:
> > > Jeff Garzik <jgarzik@pobox.com> wrote:
> > > > Can you expand that URL? :) I may be missing a patch or something
> > > > obvious, but the 2.1.117 linux/drivers/block/md.c lists linear, RAID0,
> > > > RAID1, and RAID5 under the CONFIG_MD_BOOT section, with the RAID1/5
> > > > code commented out... (line 1250 or so)
>
> > > Apparently because lilo cannot read the kernel from more than one disk.
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html