> My Problem:
> First i tried to use root=/boot-hda1 in lilo.conf.hda below. But this
> doesn't work. I got the following error from lilo:
> Sorry, don't know how to handle device 0x0906
> ... but /boot-hda1 was mounted to /dev/hda1 which is a nonraid ext2
> partition.
> o.k. but when i mount /dev/hda1 on /boot lilo works
If lilo tells you it can't handle device 0x0906, that means somewhere in
lilo.conf you are telling lilo to read from /dev/md6. Do you really mean you
used root=/boot-hda1? This would make no sense as you want /boot-hda1 to be your
/boot filesystem, not your / filesystem. But your lilo.conf and shell script
imply that this is not what you are doing, so I hope this was just a typo. If
not, you know where your problem lies.
Assuming this was a typo, and you were actually going with a lilo.conf something
like:
append="console=ttyS1"
boot=/dev/hda
serial=1,9600n8
vga=normal
read-only
prompt
timeout=50
image = /boot-hda1/vmlinuz
root = /dev/md6
label = Linux
and this was throwing up the "can't handle device 0x0906" error, then you may
find that the problem is the absence of map= and install= lines. If these are
not included in your lilo.conf, lilo defaults to map=/boot/map and
install=/boot/boot.b. With /dev/hda1 mounted on /boot-hda1, /boot presumably
resides on the root filesytem, i.e. /dev/md6. Try adding the lines:
map=/boot-hda1/map
install=/boot-hda1/boot.b
below the boot= line in your lilo.conf and see whether that works.
Or better still, do away with /boot-hda1, and leave /dev/hda1 on /boot
permanently. Why do you want to have 2 copies of the /boot filesystem on each
disk anyway? This means that anytime you make changes to the kernel, you have to
copy from /boot to /boot-hda1 before you can run lilo. I can't see what this
gets you, apart from extra hassle.
> I changed my lilo script and now lilo installs the kernels on /dev/hda1
> and /dev/hdc1 and itself to the master boot record. Both partitions are
> marked as active.
> Booting from /dev/hda1 works fine. Then I simulated a error and removed my
> first disk. In my BIOS i use autodetection for the harddisks. When System
> reboots I think he tries to boot from /dev/hdc1, because the computer
> doesn't say "no system, press any key to reboot" (or something similiar).
> But I only got many alternating 010101010101 scrolling down my screen -
> which means that something is wrong with lilo....
> Is there something else to do, that lilo could boot from the second disk?
As James says, use a "disk=/dev/hdc bios=0x80" line after your boot= line in
lilo.conf.hdc to tell lilo that in the event that you boot from hdc, it will
actually be in the bios location of hda. You should be aware that this trick is
fine for when /dev/hda blows up so completely that it isn't even identified and
/dev/hdc slips to /dev/hda. But in the situation where /dev/hda fails but is
still recognized as present, you are stuck until you either pull the disk or use
a boot floppy.
Cheers,
Bruno Prior [EMAIL PROTECTED]
