Excerpt from the Linux Bootdisk HOWTO.
Ever want to know why LILO stops processing at a certain letter, for instance:
LIL (and then it hangs there)
Well here's a table! (found at http://www.tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html)
Ever want to know why LILO stops processing at a certain letter, for instance:
LIL (and then it hangs there)
Well here's a table! (found at http://www.tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html)
When LILO loads itself, it displays the word
LILO. Each 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.
| Output | 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 | 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. (See also section ``Disk error codes''.) This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters). |
| 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. |
