You are changing the system geometry in a way that lilo does not like. Try
writing your boot kernel out to a floppy (dd if=/vmlinuz of=/dev/fd0) and
booting directly off of that rather than through lilo. Often this helps.
----------------
Warren Melnick
Director of Research and Development
Astata Corporation
-----Original Message-----
From: Mikkel L. Ellertson [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 2:20 PM
To: [EMAIL PROTECTED]
Subject: Re: second IDE drive causes the "LI" boot hang
On Mon, 5 Feb 2001, Michael Jinks wrote:
> Hi all. Got bitten by this today, have no idea why, and wondered if
> anybody has seen anything similar.
>
> A friend has a disk from a dead computer that she wants to retrieve some
> data from. Pop it in my machine set as slave alongside my existing
> master, BIOS sees it fine, but when I try to boot my machine hangs with
> "LI" where I would normally expect the LILO: prompt followed immediately
> by the GUI.
>
> First attempt was with both drives on the same chain. Removed friend's
> hard drive, system booted fine.
>
> Thinking it might be IDE chaining issues, detached both devices from the
> second IDE chain and attached friend's drive there, as master. Tried
> once again to boot from my own disk on the first chain. We hang with
> "LI" again.
>
> Both drives are relatively new (<3 yrs.); mine is an 8 gig which /proc
> reports as a Maxtor 90840D6. Hers has already left to go home but I
> believe that it's a 12 gig Western Digital.
>
> We did not attempt to boot from the "guest" disk alone.
>
[SNIP]
>
> The motherboard is a SuperMicro with an Intel 440Gx chipset.
>
>
> I realize this is a bit cryptic, but that's about all the information I
> have myself. I'd settle for an explanation of possible/likely causes
> for the "LI" problem itself; I know that this is a fairly common issue,
> and I know from experience that it can occur in a variety of situations,
> but I'm clueless as to the mechanics of the failure and I'm wondering if
> anybody can clue me in on why or how it happens.
>
> Thanks,
> -m
>
Just as a test, put the drive from the "dead" computer in by itself,
boot from a floppy, and see if you can access the drive. It sounds like
you have a hardware problem with that drive, and it is messing up the
IDE bus. Your friend may be out of luck when it comes to recovering
data, unless she wants to spend big bucks, or you are lucky enough to
have another drive of the same model that you can swap electronics.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
