Re: Boot on "RAID 1" with "LILO" and "mdadm"
Dear Arnt,
Thank you very much for your reply!
Could you send me your lilo.conf configuration to compare it with mine?
Agustín
----- Original Message -----
From: "Arnt Karlsen" <arnt@c2i.net>
To: <debian-isp@lists.debian.org>
Sent: Tuesday, September 07, 2004 3:10 PM
Subject: Re: Boot on "RAID 1" with "LILO" and "mdadm"
On Tue, 7 Sep 2004 14:25:49 -0300, Agustín wrote in message
<[🔎] 01ad01c494ff$b83a3410$6800a8c0@Agus>:
> Hi Everybody!
>
> I'm trying to run a bootable RAID 1. I'm using mdadm and everything
> goes fine. All the partitions are completely synchronized and the
> problem comes in the last step:
>
> I edit lilo to boot from the RAID and reboot. The system hangs up
> saying "LIL". I've read something in the LILO documentation as:
> LIL (The descriptor table could not be read.)
> LIL (This is typically caused by media failure or geometry mismatch)
>
> I have two SATA WD800 disks. I'm running debian with the kernel 2.4.19
> and LILO 22.2
..chk out backports.org
> My LILO configuration looks like this:
>
> boot=/dev/md1
..these are known to lilo as such?
I used '/dev/hda', '/dev/hdc' etc,
and with a "fallback" to try boot the
"other" drive on each. Also throw
in panic options.
> root=/dev/md2
> raid-extra-boot=/dev/hda,/dev/hdc
> default=RAID
> image=/vmlinuz
> label=RAID
> read-only
>
> The other options are as they come in the one disk installation.
>
> I'll appreciate any comment! Thanks in advance,
>
> Agustín
>
>
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
Reply to: