On Mon, 7 May 2001 11:13:02 -0700, you wrote:
>The boot hanging at "LI" seems to be a "feature" of the LILO which shipped
>with RedHat 6.2.
>The simple workaround for it is to add a "default=" line to your lilo.conf
>file.
>I haven't heard of more recent versions of lilo having this problem, but
>have not tried any of them myself (or later RH versions).
I've tried rh71 21.4.4, and even 21.7.
Yes, adding "default = linux" made the * near hdc "linux" image to appear, but
LI was still still there.
I made some tests (maybe the following is something very obvious, but since the
howto is not updated to the boot=/dev/md0 setup I missed it):
it seems that for the single lilo.conf with boot=/dev/md0 to work you need to
use the same HS (CHS) for the 2 disks, and start the boot /dev/mdX device at the
same C (CHS).
Otherwise you need the 2 lilo.conf.hdx setup that Al suggested in the previous
email and/or use CHS values in lilo.conf.
Basically, the 2 lilo.conf's setup will _always_ work, the boot=/dev/md0 has
more initial requirements (CHS, "default" in lilo.conf, ...).
The problem is that fdisk/bios/linux like to assign different default CHS even
to equal HDs. Today I tried with 2 _identical_ 10GB IDE disks: didn't pay
attention to CHS (I made MB based partitions) and hda was recognized as
H255,S63,CX, while hdc was something like H63,S63 or similar. Raid1 worked, boot
did not. Had to force the hdc disk to be H255,S63, and then both raid1 and boot
off raid1 worked.
I was able to make my initial setup (2 completely different HDs) to work with
boot=/dev/md0 by forcing the 2nd HD to H128,S63,C311 (it was H63,S63,C622 while
the 1st is H128,S63,C615).
Thanks.
--
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
