Differences between version 8 and revision by previous author of LiloErrorCodes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Tuesday, October 19, 2004 1:28:49 am | by VeraHansper | Revert |
| Older page: | version 6 | Last edited on Monday, October 18, 2004 10:39:24 am | by PerryLorier | Revert |
@@ -3,9 +3,9 @@
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]. Definitely check to see if the disk is seen by the BIOS first
.
|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.
|0x06|__Change line active__: This should be a transient error. Try booting a second time.
