Richard,
Thanks for the response.
Even if I can get the map information using the INT
0x13h disk interrupt, I would still need some way of
knowing if sda has indeed failed.
What I am thinking of if it is possible to make the
"boot" option in lilo.conf variable. Or better,
introduce a serial# option and the serial# can be
scanned for on startup. Or make use of a lun# option.
I was also thinking if BIOS id's for the disks can be
used here. Are BIOS id's assigned for all drives?
Thanks
Manish
--- "Richard B. Johnson" <root@chaos.analogic.com>
wrote:
> On Fri, 10 Jan 2003, Manish Lachwani wrote:
>
> > In my current setup, I am having 12 ide drives
> > connected to a 3ware controller labelled sda to
> sdl.
> > Suppose sde is the drive we want the system to
> boot
> > off. What I do is modify the lilo.conf on sda,
> sdb,
> > sdc etc. to have the "boot" entry point to
> /dev/sde.
> >
> > This way when the controller is transferred to
> lilo on
> > sda, it will load the kernel from sde.
> >
> > consider this. If sda is bad and is not exported
> to
> > the OS or is not detected in the BIOS due to a bad
> > cable etc. In this scenario, the OS mappings would
> > change. Now, sdb will become sda. The lilo.conf on
> sdb
> > (now sda) would have "boot" parameter still point
> to
> > sde, which is now sdd.
> >
> > When the control is transferred to lilo on sda
> (sdb
> > actually), is there a way for me to boot off sdd
> now
> > (which was previously sde)? I mean, is there any
> way
> > that lilo can load the appropriate kernel image?
> >
> > One of the ways I was thinking of was to modify
> the
> > lilo sources to scan for drive serial# and we boot
> off
> > that drive for which the serial# matches. But,
> does
> > anyone have a better alternative?
> >
> > Thanks
> > Manish
> >
>
> When LILO boots, there is no file-system (anywhere)!
> The
> boot-record of LILO contains a table which points to
> the
> contents of the map file. This file exist only when
> LILO is being configured, i.e., when Linux is up
> with a
> mounted file-system. The contents of this file
> describe
> the location of all of the pieces of the operating
> system,
> the boot message, and any RAM-disk data. All of
> these
> pieces, plus the data of this file, itself, must be
> accessible
> from the INT 0x13 disk software interrupt when the
> machine
> is being booted.
>
> Since these pieces are known just as:
> BIOS device;
> device_offset;
> data_length;
>
> ... not as file-system directory entries that can be
> "scanned for",
> you will not be able to substitute anything. LILO
> recommends that
> all of the boot components be put on one physical
> drive so you
> don't have problems with controllers or the BIOS
> rearranging
> things.
>
> If you want to perform a "smart" boot, then you boot
> an initial
> RAM disk. This allows you to configure the system in
> way you
> want, rearranging disk-drives, even mounting network
> file-systems
> for the root file-system or even falling-back to
> alternative
> file-systems when certain ones are off-line.
>
>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.18 on an i686 machine
> (797.90 BogoMips).
> Why is the government concerned about the lunatic
> fringe? Think about it.
>
>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:35 EST