SuSE Linux: All versions
LILO
on the screen.
The LILO start-up code consists of two parts: The "first stage" in a boot
sector and the
"second stage" in /boot/boot.b
. During the installation of
LILO, a map file is
created, usually /boot/map
, where LILO finds the necessary
pointers (sector addresses)
to the operating systems (Linux kernel, etc.) that should be started.
(The following is taken from section 5.2.1 of the original LILO User's Guide by LILO author Werner Almesberger)
When LILO loads itself, it displays the word
LILOEach letter is printed before or after performing some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem.
(nothing)
No part of LILO has been loaded. Either LILO isnīt installed or the partition on which its boot sector is located is not active.
L error
The first stage boot loader has been loaded and started, but it canīt load the second stage boot loader. The two-digit error codes indicate the type of problem. This condition usually indicates a media failure or a geometry mismatch.
LI
The first stage boot loader was able to load the second stage boot loader,
but has failed to execute it. This can either be caused by a geometry mismatch
or by moving /boot/boot.b
without running the map installer.
LIL
The second stage boot loader has been started, but it canīt load the descriptor table from the map file. This is typically caused by a media failure or by a geometry mismatch.
LIL?
The second stage boot loader has been loaded at an incorrect address. This is typically caused by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer.
LIL-
The descriptor table is corrupt. This can either be caused by a geometry mismatch
or by moving /boot/map
without running the map installer.
LILO
All parts of LILO have been successfully loaded.
The most frequent causes for a geometry mismatch are not physical defects or invalid partition tables but errors during the installation of LILO. Often these are caused by ignoring the 1024 cylinder boundary (1024_Zylinder.html).
In most cases, the solution is to apply one of the three procedures given below:
/boot
and the boot sector that
will contain LILO's start-up code.
/sbin/lilo
.
Tip:/sbin/lilo
can provide a detailed log
if you enhance verbosity and redirect the output to
appropriate log files. To do so, proceed like this:
/sbin/lilo -v -v -v >/boot/lilo.log 2>/boot/lilo.logerr
/boot/lilo.logerr
should contain nothing at all (if the
boot configuration is correct). /boot/lilo.log
will
tell you precisely which geometries and BIOS device
numbers LILO will use.
disk =
option for
lilo.conf
. Refer to the LILO section in your
SuSE Linux manual, the original LILO documentation, or
http://sdb.suse.de/sdb/en/html/ke_eide-scsi.html.
/var/log/boot.msg
or (maybe) the output
of the dmesg
command)./sbin/fdisk -l
.fdisk
Expert commands. Very dangerous for your data!
Previous full backup strongly recommended! Really for
experts only!
In case of inconsistencies, the way of least resistance will often be the best method for adjustment.
When you contact any kind of support about LILO, your chances for success will be significantly better if you include the following in your request:
/etc/lilo.conf
fdisk -l
(partition layout)