Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Stephan Goeldi on April 23, 2001, 02:09:37 AM
-
I had a working 4.1.1 version on my server when I started the 4.1.2 upgrade. I had to left the server alone and came back some hours later. The screen was black, it seemed to be in stand-by mode. I hitted several key, without waking him up. After some minutes of hacking on the keyboard I pressed Ctrl-Alt-Del.
The server doesn't boot anymore and only shows me the
LI
I think, apm should be always disabled on hardware-side, when doing installations. But of course the software should disable power management too. I don't understand, why it was impossible to awake the computer.
-
"LI" indicates a problem with LILO. I don't know what problem, but it's very common if you wish to investigate it further.
-
Mike Stoddart wrote:
> "LI" indicates a problem with LILO. I don't know what
> problem, but it's very common if you wish to investigate it
> further.
From the LILO documentation:
" 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."
If the output is...
(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 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/boot.b without running the map installer.
LILO: All parts of LILO have been successfully loaded.
Hope this helps anyone...
--
Pierluigi Miranda