Re: Lilo trouble

Hi Ian

The culprit was me...
Here is the post you are after.:-

On Tue, 26 Oct 1999, you wrote:
> From: Dan Falck <dfalck@...>
> This might be totally off but here's something to check- look at the
> lilo.conf file (/etc/lilo.conf). I screwed mine up one time and got LI
> instead of LILO. It should probably look something like:
>

Hi Dan
Here's an extract from my manual that may be of interest.

When LILO is launched, it displays the word LILO. Every letter signifies a
certain state. If LILO cannont be launched, the output letters give a clue to
where the error occurred :

none - No part of LILO has been loaded. Either LILO is not installed at all or
the partition with LILO's boot sector has not been started.

L error - The first step has been loaded and started but the second step (
/boot/boot.b ) could not be loaded. This normally points to a physical error on
the boot device or a faulty disk geometry.

LI - The second step has been invoked but could not be started. This can be due
to a faulty disk geometry or moving /boot/boot.b without reinstalling LILO.

LIL - The second step of LILO has been started but could not allocate needed
data from it's map file. This is typically due to a physical error of the boot
device or a faulty disk geometry

LIL? - The second step has been loaded at a wrong memory address. This can be
due to a faulty disk geometry or to moving /boot/boot.b without reinstalling
LILO.

LIL- - Data in the map file is invalid. This can be due to a faulty disk
geometry or to moving /boot/boot.b without reinstalling LILO.

LILO - Every part of LILO has been loade successfully.

The most common causes of geometry errors are not physical defects or invalid
partition tables but errors in LILO installation, including ;

* disregard of the 1024 cylinders limit
* an unsuccessful attemp at starting LILO from a logical partition.

{End of quote}
Hopefully this will be of interest to someone, if not yourself.

Regards, Paul.