Well This Sucks! **FIXED**

[Damaged]

Somehow I just hosed LILO on my Debian distro. Don't know what happened there, recompiled the kernel, cp'd System.map bzImage, installed modules, edited the /etc/lilo.conf file correctly, ran /sbin/lilo, double checked everyting again, ran /sbin/lilo again, rebooted and it pukes out at LIL-.

What this means is that it can't find the map file, or that there's a drive geometry problem Argh! I must admit that fdisk shows some funky drive geometry. I don't recall having set the parameters in that manner and I did have to manually configure the CHS, etc. Checked the BIOS recognition of the drive and that looks just peachy. I let it auto detect just in case and saved the new settings. Same problem.

I've tried a recue disk but I can't seem to get lilo to install that way, after much fscking around might I add. Fatal errors on me says it can't open device and give me a hex number, which seems to apply to the /dev/hdxx I'm trying to write to.

I doubt there's a fix at this point, but...if anyone knows of one, please let me know.

Cool thing is is that I have another drive in the system which is nearly empty, and I have been successful in mounting the paritions, so I guess I can copy over anything I need to other drive.

Thanks.

 

[Damaged]

Hah! Fixed it. I made a boot disk on my Debian box at work, uninstalled LILO from everywhere that I could think of then rebuilt a new kernel, part of the problem, then edited /etc/lilo.conf and noticed this:

boot=/dev/hda5
roo=/dev/hda5

Hmm, fdisk /dev/hda, print. Hmmm, hda2 is marked as bootable. So I changed that parameter, reinstalled LILO and all is well.

I have no idea where that line came from cause I don't muck with that once it's setup.

I'm just happy it's fixed

 

[Ag97yellow94]

Yeah, this happened to me recently - also, the next lilo upgrade ( I am running Sid) broke me as well - I had to remove lba32 and compress? from my lilo.conf. Pain in the a$$...

 

[BOFH]

This is why it pays to follow the kernel-cousin list ;-) This and the changes in tar get covered w/o you getting flooded even worse with email

 

[Damaged]

I recall from my last apt-get upgrade that lilo was replaced, but I'm sure I told it NOT to install a new lilo.conf file. Well, I am running Debian 2.3, which is the unstable tree, so....