Firstly, my BIOS is set up to autodetect. I tried the LILO trick. I ran lilo -U and
lilo. This time I did get LIL-. Doesn't that mean something about corrupt descriptor
table or something? How do I find out which one? Let me try to be a little more
specific in what I've done, and what I'm
> If say your root drive is sda1 which is RAIDed to sdb1 then all you
> need to do is change the boot= & root= lines once.
> boot=/dev/sdb
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> image=/boot/vmlinuz
> label=linux
> root=/dev/sdb1
> initrd=/boot/initrd
On Thu, 10 Jun 1999, David Robinson wrote:
Hi,
> If you put lilo in the MBR (someone correct me if I'm wrong) I don't
> think you need to make the root partition bootable using fdisk as LILO
> runs from the MBR before even the partitions get looked at.
It depends on the compute
How I deal with root-mirror and two boot-partitions:
/etc/lilo.conf:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
default=linux
timeout=50
root=/dev/md1
read-only
image=/boot/vmlinuz
label=linux
# see /sbin/lilo, /sbin/lilo.real! - osma 1999-04-10
image=/boot.alt/vmlinuz
Hmm So your saying you can't disconnect any drive without LILO stuffing up... bad..
Umm Have you got your BIOS setup to autodetect the HD's?
A very simple way of putting LILO in both drives is to edit your /etc/lilo.conf:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/b
