Differences between version 5 and revision by previous author of LiloErrorCodes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Thursday, May 13, 2004 8:29:15 am | by StuartYeates | Revert |
| Older page: | version 4 | Last edited on Thursday, May 13, 2004 7:07:05 am | by AlexKirk | Revert |
@@ -3,19 +3,19 @@
eg: L 01 01 01, L 07 07 07 etc..
|Code|Reason
|0x00|__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 re-building the map file. Another possible cause for this error are attempts to access cylinders beyond 1024 while using the LINEAR option.
-|0x01|__Illegal Command__: This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS.
+|0x01|__Illegal Command__: This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the [
BIOS]
.
|0x02|__Address mark not found__: This usually indicates a media problem. Try again several times.
|0x03|__Write-protected disk__: This should only occur on write operations.
-|0x04|__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 or a large IDE disk, you should check, whether LILO has obtained correct geometry data from the kernel or whether the geometry definition corresponds to the real disk geometry. Removing COMPACT may help too. So may adding LBA32 or LINEAR.
+|0x04|__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 or a large IDE disk, you should check, whether LILO has obtained correct geometry data from the kernel or whether the geometry definition corresponds to the real disk geometry. Removing COMPACT may help too. So may adding LBA32 or LINEAR.
|0x06|__Change line active__: This should be a transient error. Try booting a second time.
|0x07|__Invalid initialization__: The BIOS failed to properly initialize the disk controller. You should control the BIOS setup parameters. A warm boot might help too. (Boot a rescue disc and rerun LILO.)
-|0x08|__DMA overrun__: This shouldn't happen. Try booting again.
+|0x08|__[
DMA]
overrun__: This shouldn't happen. Try booting again.
|0x09|__DMA attempt across 64k boundary__: This shouldn't happen, but may inicate a disk geometry mis-match. Try omitting the COMPACT option. You may need to specify the disk geometry yourself.
|0x0C|__Invalid media__: This shouldn't happen and might be caused by a media error. Try booting again.
-|0x10|__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.
-|0x11|__ECC correction successful__: A read error occurred, but was corrected. LILO does not recognize this condition and aborts the load process anyway. A second load attempt should succeed.
+|0x10|__[
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.
+|0x11|__[
ECC]
correction successful__: A read error occurred, but was corrected. LILO does not recognize this condition and aborts the load process anyway. A second load attempt should succeed.
|0x20|__Controller error__: This shouldn't happen, then again, none of these errors should happen eh?
|0x40|__Seek failure__: This might be a media problem. Try booting again.
|0x80|__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.
|0xBB|__BIOS error__: This shouldn't happen. Try booting again. If the problem persists, removing the COMPACT option or adding/removing LINEAR or LBA32 might help.
@@ -39,9 +39,9 @@
[1]-excerpted from Werner Almesberger's LILO Users Guide.
__Helpful note for those stuck with only "L" appearing on the LILO screen: __
-This can be caused by a buggy BIOS which does not properly match up BIOS disks with OS disks. This can be fixed by using the __disk__ parameter in /etc/lilo.conf, which when used with the bios keyword allows you to map BIOS disks to Linux disks. For example, I was just able to recover a server where an IDE CD-ROM, /dev/hda, was the primary master and an IDE hard disk, /dev/hdb, was the primary slave, with this entry in /etc/lilo.conf:
+This can be caused by a buggy BIOS which does not properly match up BIOS disks with OS disks. This can be fixed by using the __disk__ parameter in /etc/lilo.conf, which when used with the bios keyword allows you to map BIOS disks to Linux disks. For example, I was just able to recover a server where an [
IDE]
CD-ROM, /dev/hda, was the primary master and an IDE hard disk, /dev/hdb, was the primary slave, with this entry in /etc/lilo.conf:
__disk=/dev/hdb bios=0x80__
This may or may not require further tweaking for your setup. All I know is that if I'd seen this option on the web instead of extracting it from a Mandrake /etc/lilo.conf, I'd have saved a day's work. :-)
