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.
Anecdote, possibly informative to someone: When I first encountered
this problem I thought that I might have just somehow hosed my boot
loader; I had just installed a new kernel before the shutdown to install
the new disk (it was from an NT machine and I don't normally have an
NTFS-ready kernel). Not having instructions on how to properly use the
rescue mode of the Red Hat CD, I decided to just do a minimal clean
install of the OS on a spare partition, and boot from that to try and
clean things up. Red Hat installer booted fine, saw both IDE disks,
including all the partitions as expected on each one. In Disk Druid I
set my spare partition (which already has a Linux filesystem) as root
and left all other filesystems as they were. Right after I hit the OK
button to continue from DiskDruid, something (it went by too quickly for
me to see) got what looked like a segfault, and the system went down
after printing a couple of quick errors to the screen. This was with
both drives still on the same IDE cable, in case that matters.
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
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
