rhl04.htm

linux的初学电子书

</UL>

<BR>

<A NAME="E69E34"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>LILO Error Codes</B></FONT></CENTER></H4>

<BR>

<P>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. This is described in more detail in 
the technical overview.

<BR>

<P>Note that some hex digits may be inserted after the first L if a transient disk problem occurs. Unless LILO stops at that point, generating an endless stream of error codes, such hex digits do not indicate a severe problem. The following is the list of 
error messages you can see:

<BR>

<UL>

<UL>

<P>(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.

<BR>

</UL></UL>

<UL>

<UL>

<P>L&lt;error&gt; 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. (They are described in the next section.) This condition usually indicates a 
media failure or a geometry mismatch (that is, bad parameters in /etc/lilo/disktab).

<BR>

</UL></UL>

<UL>

<UL>

<P>LI The first-stage boot loader was able to load the second-stage boot loader but has failed to execute it. This can be caused either by a geometry mismatch or by moving /etc/lilo/boot.b without running the map installer.

<BR>

</UL></UL>

<UL>

<UL>

<P>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 a geometry mismatch.

<BR>

</UL></UL>

<UL>

<UL>

<P>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 /etc/lilo/boot.b without running the map installer.

<BR>

</UL></UL>

<UL>

<UL>

<P>LIL- The descriptor table is corrupt. This can be caused either by a geometry mismatch or by moving /etc/lilo/map without running the map installer.

<BR>

</UL></UL>

<UL>

<UL>

<P>LILO All parts of LILO have been successfully loaded.

<BR>

</UL></UL>

<P>There are also BIOS error codes that you might get while loading LILO. These are listed in Table 4.1.

<BR>

<BR>

<P ALIGN=CENTER>

<CENTER>

<FONT COLOR="#000080"><B>Table 4.1. BIOS error codes.</B></FONT></CENTER>

<BR>



<TABLE  BORDERCOLOR=#000040 BORDER=1 CELLSPACING=2 WIDTH="100%" CELLPADDING=2 >

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

<I>Code </I>

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

<I>Value</I></FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x00

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Internal error. This code is generated by the sector-read routine of the LILO boot loader whenever an internal inconsistency is detected. This might be caused by corrupt files; try rebuilding the map file.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x01

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Illegal command. This shouldn't happen.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x02

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Address mark not found. This usually indicates a media problem. Try again several times.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x03

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Write-protected disk. This shouldn't happen.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x04

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Sector not found. This typically indicates a geometry mismatch. If you're booting a raw-written disk image, verify whether it was created for disks with the same geometry as the one you're using. If you're booting from a SCSI disk, you should check whether 
LILO has obtained correct geometry data from the kernel or whether the contents of your /etc/lilo/disktab file correspond to the real disk geometry. Removing compact may help too.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x06

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Change line active. This should be a transient error. Try booting a second time.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x08

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

DMA overrun. This shouldn't happen. Try booting again.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x09

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

DMA attempt across 64KB boundary. This shouldn't happen. Try omitting the -c option.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x0C

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Invalid media. This shouldn't happen and might be caused by a media error. Try booting again.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x10

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

CRC error. A media error has been detected. Try booting several times, running the map installer a second time (to put the map file at some other physical location or to write good data over the bad spot), mapping out the bad sectors/tracks, and, if all 
else fails, replacing the media.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x20

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Controller error. This shouldn't happen.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x40

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Seek failure. This might be a media problem. Try booting again.</FONT>

<TR>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

0x80

</FONT>

<TD VALIGN=top  BGCOLOR=#80FFFF ><FONT COLOR=#000080>

Disk timeout. The disk or the drive isn't ready. Either the media is bad or the disk isn't spinning. If you're booting from a floppy, you might not have closed the drive door. Otherwise, trying to boot again might help.</FONT>

</TABLE><BR>

<A NAME="E68E27"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Using BOOTLIN Instead of LILO</B></FONT></CENTER></H3>

<BR>

<P>The BOOTLIN package uses the DOS MBR to boot off the hard drive. To install this package, you mus<A NAME="I2"></A>t take the following steps:

<BR>

<OL>

<LI>From within Linux, copy a bootable kernel to your DOS partition.

<BR>

<BR>

<LI>Edit config.sys on the DOS partition to include two files: BOOT.SYS and BOOTLIN.SYS. The README files for these packages tell you how.

<BR>

<BR>

<LI>Reboot.

<BR>

<BR>

</OL>

<P>Now when you reboot, the BOOT.SYS and BOOTLIN.SYS files will boot into Linux for you.

<BR>

<P>To get back to running only DOS, remove the BOOTLIN.SYS and BOOT.SYS from your config.sys file.

<BR>

<P>The disadvantage of this approach is that you are limited to having DOS on your hard drive.

<BR>

<BR>

<A NAME="E68E28"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Restoring the MBR</B></FONT></CENTER></H3>

<BR>

<P>If you want to restore the MBR to the original DOS MBR, you can use the following procedure:

<BR>

<OL>

<LI>Boot from a DOS floppy.

<BR>

<BR>

<LI>Run fdisk /MBR from the DOS prompt. (You can also use the command SYS C:.)

<BR>

<BR>

<LI>Reboot.

<BR>

<BR>

</OL>

<BR>

<A NAME="E68E29"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Summary</B></FONT></CENTER></H3>

<BR>

<P>This chapter covered the topic of installing, configuring, and using LILO. It also covered some of the basic errors you can face and how to set up LILO using the liloconfig utility. The information you have learned from this topic should get you started 
in setting up LILO to boot Linux on your machine off the hard drive.

<P ALIGN=LEFT>

<A HREF="rhl03.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl03.htm" TARGET="_self"><IMG SRC="purprev.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>

<A HREF="#I0" TARGET="_self"><IMG SRC="purtop.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purtop.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Page Top"></A>

<A HREF="index-1.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/index.htm" TARGET="_self"><IMG SRC="purtoc.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purtoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>

<A HREF="rhl05.htm" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/rhl05.htm" TARGET="_self"><IMG SRC="purnext.gif" tppabs="http://202.113.16.101/%7eeb%7e/Red%20Hat%20Linux%20Unleashed/purnext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>


</BODY></HTML>