300 lines
5.0 KiB
HTML
300 lines
5.0 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>LILO boot error codes</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="The Linux Bootdisk HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="The Linux boot process"
|
|
HREF="x1440.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Sample root filesystem listings"
|
|
HREF="listings.html"></HEAD
|
|
><BODY
|
|
CLASS="APPENDIX"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>The Linux Bootdisk HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x1440.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="listings.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="APPENDIX"
|
|
><H1
|
|
CLASS="APPENDIX"
|
|
><A
|
|
NAME="AEN1483"
|
|
>B. LILO boot error codes</A
|
|
></H1
|
|
><P
|
|
>Questions about these codes are asked so often on Usenet that we include
|
|
them here as a public service. This summary is excerpted from Werner
|
|
Almsberger's <A
|
|
HREF="http://www.ibiblio.org/pub/Linux/system/boot/lilo/lilo-u-21.ps.gz"
|
|
TARGET="_top"
|
|
>LILO User Documentation</A
|
|
>.</P
|
|
><P
|
|
> When LILO loads itself, it displays the word
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>LILO</TT
|
|
>. 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.</P
|
|
><DIV
|
|
CLASS="INFORMALTABLE"
|
|
><A
|
|
NAME="AEN1492"
|
|
></A
|
|
><P
|
|
></P
|
|
><TABLE
|
|
BORDER="1"
|
|
CLASS="CALSTABLE"
|
|
><THEAD
|
|
><TR
|
|
><TH
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>Output</TH
|
|
><TH
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>Problem</TH
|
|
></TR
|
|
></THEAD
|
|
><TBODY
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>(nothing)</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> 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.
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>L</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> 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).
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>LI</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> 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 <TT
|
|
CLASS="FILENAME"
|
|
>/boot/boot.b
|
|
</TT
|
|
>
|
|
without running the map installer.
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>LIL</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> 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.
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>LIL?</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> The second stage boot loader has been loaded at an incorrect
|
|
address. This is typically caused by a subtle geometry mismatch or
|
|
by moving <TT
|
|
CLASS="FILENAME"
|
|
>/boot/boot.b</TT
|
|
> without running the
|
|
map installer.
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>LIL-</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> The descriptor table is corrupt. This can either be caused by a
|
|
geometry mismatch or by moving /boot/map without running the map
|
|
installer.
|
|
</TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="96"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
>LILO</TD
|
|
><TD
|
|
WIDTH="100%"
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
> All parts of LILO have been successfully loaded.
|
|
</TD
|
|
></TR
|
|
></TBODY
|
|
></TABLE
|
|
><P
|
|
></P
|
|
></DIV
|
|
><P
|
|
>If the BIOS signals an error when LILO is trying to load a boot image, the
|
|
respective error code is displayed. These codes range from
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>0x00</TT
|
|
> through <TT
|
|
CLASS="LITERAL"
|
|
>0xbb</TT
|
|
>. See the LILO User
|
|
Guide for an explanation of these.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x1440.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="listings.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>The Linux boot process</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Sample root filesystem listings</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |