Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
LILO
appeared on the screen.
The LILO start-up code consists of two parts : The "first stage" in a bootsector and the
"second stage" in /boot/boot.b
. During the installation of LILO a "map-file" is
created (ususllay /boot/map
), where LILO finds the necessary pointers (sector-adresses)
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. LILO either isn't installed or the partition on which its boot sector is located isn't 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 follow the procedure given below :
/boot
and the bootsector which
will contain LILOs start-up code.
# /sbin/lilo
See also:
Keywords: BOOT, BOOT-PROBLEMS, LILO
Categories:
LILO
Feedback welcome: Send Mail to rb@suse.de (Please give the following subject: SDB-kgw_lilo_errmsg
)
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch