Please look at http://sunsite.auc.dk/linux-newbie/FAQ.htm#LILO_stops�for
lots of info on how to fix this, esp section 4.1.2.� If you can boot off a
rescue disk, try fscking (e2fsck -cp /dev/hdXX) the boot partition (and
maybe the others, too) to see if somehow the system map was fragmented and
then run lilo to rewrite the MBR.� While you are at it, try running hdparm
as described in the aforementioned doc.� If the drive worked before, the
geometry *should* be OK.� If you have a large disk, it might be worth a
quick try to see if the linear option helps, but I doubt it since it ran
previously.
-----Original Message-----
From: Darrin Lajoie [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 18, 2000 7:57 AM
To: linux group
Subject: recent HD crash
Does anyone have an idea on this one.
�
A couple evenings ago, my Debian 2.1 box crashed due to a faulty power
supply. It had crashed in the same way a time or two before, I put it on a
UPS so I've got the problem narrowed down to the power supply. But that's
not the problem.
�
Now on boot up, I get the following:
�
LIL-
�
Then nothing. The LILO manual.txt says the LIL- means a descriptor table is
corrupt either by a geometric mismatch or by moving /boot/map without
running the map installer. I've re-run LILO, but still no luck getting it to
boot without my boot floppy.
�
>From the fdisk menu I've done a v to verify the partition table and it says
I have 62 unallocated sectors. My other Debian box has unallocated sectors
too, so I'm not sure if this is a problem.
�
Can someone tell me if having unallocated sectors is related to my possible
geometric mismatch and/or how do I fix my hard drive so it can boot by
itself again?
�
Thanks
Darrin
