Doug Ledford on Fri 23/06 15:21 -0400:
> > LILO is stock RH 6.2 build (which includes lilo.raid and other
> > patches according to the .spec)
> >
> > boot = /dev/md0
> > image = /boot/blah
> > label = something
> > root = /dev/md0
> > read-only
> >
> > boot and root are both on /dev/md0 which is sda1 and sdb1.
> >
> > LILO loads just fine booting off either sda or sdb. However, no
> > labels appear (that is, when hitting tab) when I boot off sdb; only
> > when booting off sda. [...]
> >
> > My current workaround is to just dd the boot sector of sda over to
> > sdb after LILO installs.
>
> How are you testing the sdb boot capability? Are you taking the sda
> drive entirely out of the picture (meaning are you powering it down or
> removing it)?
I just select the second disk's SCSI ID in the Adaptec's BIOS. I did
make sure changing this actually changed the boot disk before making any
claims.
> The raid.lilo patch wasn't intended to be highly flexible because it
> doesn't need to be. If you are doing truly redundant boots using
> software raid there is currently only one OS that you can do it with,
> linux,
How do you figure? You can have doubled, unmirrored boot partitions on
some other operating systems, and have all the rest of the data
mirrored.
> and the lilo setup need only concern itself with that.
> That bit of fact made the patch *far* simpler than it would have
> otherwise been, and the net result is that it will work fine (under
> our testing anyway) when the first drive is actually physically
> removed from the system.
I've actually tried that as well. That is to say, I've changed the
mirror to ID0, completely removed the first (real ID0) drive, and tried
booting off that. Same story, no images available. But I did not try
specifying the default image as another poster suggested; that should be
unnecessary as LILO defaults to the first image.
--
Scott
