Lilo Error 0x07
Error Codes eg: L 01 01 01, L 07 07 07 etc.. 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. Definitely check to see if the disk is seen by the BIOS first (and that the BIOS detail is complete). 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. 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. 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, rep
dynDNS.it - DNS dinamico gratuito - Free dynDNS
summary is excerpted from Werner Almsberger's LILO User Documentation.
When LILO loads itself, it displays the word LILO. Each letter is printed before or after http://www.tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html performing some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem.OutputProblem(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 lilo error 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 lilo error 0x07 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 is 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/map without running the map installer. LILO All parts of LILO have been successfully loaded.