I'm not sure how to fix it, but I'm suspicious that some portion of the data
which LILO should have written to both mirrors is only being written to the
"first" drive in the mirror; which in your case is your second physical
drive. Note that LILO says its working on /dev/sdb1 first, then /dev/sda1.
On my test system, the boot disk is listed first in the array and it works
fine as advertised.
Its a bit scary, but you can change the order of the drives in /etc/raidtab
and rerun the mkraid command to change the order to what you'd like it to
be; with /dev/sda1 as raid_disk 1 and /dev/sdb1 as raid_disk 2, without
affecting any of the data actually stored on the drives. If you need more
explicit instructions we can take it off of the list.
Rich B
----- Original Message -----
From: "Chance Reschke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, May 08, 2000 4:25 PM
Subject: Lilo RAID-1 woes
> Hi,
>
> I've been trying to get Lilo to work with Linux software RAID-1. I'm
> using the patches from Richard Bollinger's post from 5/4/2000, and
> things almost work. I can use lilo to update the boot sector and
> maps, but lilo will not boot unless I enter a valid kernel label at
> the boot time lilo prompt.
>
> When I run lilo it appears to update the boot sector and maps;
> however, after rebooting the lilo prompt appears, followed after the
> timeout period by the message "Error 0x80". The lilo prompt then
> reappears, and the pattern repeats. At any point while the lilo
> prompt is being displayed I can enter a valid lilo label and the
> corresponding kernel will boot. Pressing <TAB> at the lilo prompt
> does not list the configured labels. Running 'lilo -R labelname'
> before rebooting doesn't help.
>
> While I'm aware that the 0x80 error is supposed to refer to "Disk
> timeout", I'm confident both disks in my array are up and running.
>
> My lilo.conf:
>
> boot=/dev/md0
> root=/dev/md0
> install=/boot/boot.b
> prompt
> timeout=50
> image=/boot/vmlinuz-2.2.14smp
> label=2.2.14
> read-only
>
> I'm using the raid-2.2.14-B1 patches to a clean 2.2.14 source tree,
> and lilo version 21 with patches from:
>
> http://www.elliott-turbo.com/lilo/lilo.raid1
> http://www.elliott-turbo.com/lilo/lilo.raid1.also
>
> Running 'lilo -v -v' I get:
>
> LILO version 21, Copyright 1992-1998 Werner Almesberger
>
> boot = /dev/sdb, map = /boot/map.0811
> Reading boot sector from /dev/sdb
> Merging with /boot/boot.b
> Secondary loader: 8 sectors.
> Boot image: /boot/vmlinuz-2.2.14smp
> Setup length is 4 sectors.
> Mapped 1298 sectors.
> Added 2.2.14 *
> /boot/boot.0810 exists - no backup copy made.
> Map file size: 10240 bytes.
> Writing boot sector.
> boot = /dev/sda, map = /boot/map.0801
> Reading boot sector from /dev/sda
> Merging with /boot/boot.b
> Secondary loader: 8 sectors.
> Boot image: /boot/vmlinuz-2.2.14smp
> Setup length is 4 sectors.
> Mapped 1298 sectors.
> Added 2.2.14
> /boot/boot.0800 exists - no backup copy made.
> Map file size: 10240 bytes.
> Writing boot sector.
>
> Any help fixing this would be great.
>
> Thanks,
> Chance
>
> --
> Chance Reschke
> UW Astronomy
>
>
