linux boot trouble?? "boot failure": the image your trying to boot is corrupt, either a bad disk or a bad origional image "2FA" its not an error code its a prompt, press 2, F (floppy) or A (advanced) sometimes just pressing enter will continue the boot LILO trouble: L ... 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. 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. 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. See also ``Warning: BIOS drive 0x number may not be accessible'' in section 5.1.2. 0x02 ``Address mark not found''. This usually indicates a media problem. Try again several times. 0x03 ``Write-protected disk''. This shouldn't happen. 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. (See section 3.4.) Removing compact may help too. So may adding 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. Make sure you dont have two harddrives, both set to master, on the same cable. 0x08 ``DMA overrun''. This shouldn't happen. Try booting again. 0x09 ``DMA attempt across 64k boundary''. This shouldn't happen. Try omitting the compact option and report this problem to the author. 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. 0x20 ``Controller error''. This shouldn't happen. Usually interperted as "your hard drive is fried" 0x40 ``Seek failure''. This might be a media problem. Try booting again. run any manufacturers disk check utilities you can find. If you are using an old Motherboard that cant do harddrive geometry translation, and the drive your using is larger than 500M, you'll need to create a 5M to 10M partition on the start of your drive and mount /boot to it. This will solve any 1024 cylinder problems. This problem only shows up when you try to boot the drive, Origional installation will work fine. 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 might help. Generally, invalid geometry and attempts to use more than two disks without a very modern BIOS may yield misleading error codes. Please check carefully if /sbin/lilo doesn't emit any warnings. Then try using the linear option (see section 3.2.2). This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters, see section "Disk geometry"). LI you may be able to fix this by adding lba32 to your lilo.conf (and re-running lilo) (I encourage you to look up all options suggested before/while using them) 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 /boot/boot.b without running the map installer (/sbin/lilo). 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.