recovering lilo

eRJe · 07-07-2008, 05:35 AM

Hi,

After recovering a slackware image, my system would not boot anymore. LILO got corrupted and was giving me 99 99 99 ... etc.

I used slackware boot dvd to boot by entering

Code:

boot: huge26.i root=/dev/hda1 noinitrd ro

I had to use huge26 because other would freeze at "freeing unused kernel menory"

So I managed to boot and now I would like to reconfigure lilo using the excisting /etc/lilo.config file. Though when I run lilo I get the following error message

Code:

fatal: illegal 'root=' specification: /dev/fd2

What is going wrong here? I've read how-too's how to install lilo but none of them mention such an error message.

Thanks in advance!

Robbert

pinniped · 07-07-2008, 06:18 AM

Have a look at the actual lilo.conf file and find out what is going on. '/dev/fd2' usually means the third floppy device - which usually doesn't make sense.

samac · 07-07-2008, 06:20 AM

Change the root line to

Code:

root="/dev/hda1"

My /etc/lilo.conf is below

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:

append="vt.default_utf8=0"
boot = /dev/hda

# Linux bootable partition config begins

image="/boot/vmlinuz"
initrd="/boot/initrd.gz"
root="/dev/hda6"
label="Slackware-12.1"
read-only

other="/dev/hda3"
label="Slamd64"

# Linux bootable partition config ends

Remember to run

Code:

/sbin/lilo

as root after any changes to lilo.conf

samac

tdos20 · 07-07-2008, 06:43 AM

Also be sure that your bios isn't accidentally setup to boot from any usb drives you may have attached - sometimes an old lilo install on one of these can cause the 99 99 99 ... problems you saw - its pretty unusual for lilo to become corrupted

eRJe · 07-07-2008, 09:12 AM

I must be getting blind... or stupid!

I found the problem. It was indeed the lilo.conf which must have been changed sometime last night during my attempts recovering slack.

Thanks to all who have replied! It is really apreciated!!!

Robbert