"LILO boot problem detailed" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ------------------------------------ author: cherami Note: Fauci (19 12/12/2000 : 01) 1, LILO Output No Results 0101010101 ... Delivery core or launch image file on the drive of the BIOS inaccessible. 2, LILO stops LILO's first stage loader to find the second phase The loader. Generally it also returns a disk error code and records it in the / usr / doc / packages / lilo file. This is usually different from the current BIOS and LILO's understanding of the geometry of the disk. In the case of the BIOS support LBA, it can be activated and set the linear directive to / etc / l Ilo.conf, which is reversed, if it already in it, then remove, then run Lilo. To ensure that the boot partition is small enough In order to adapt to the cylindrical restrictions that the BIOS can access. 3, LILO stops the second phase loader in the LI, but cannot be loaded correctly, or because the disk's geometric fault or /boot/boot.b and the system The image is inconsistent, you can run Lilo and restart (Fosi installation discovery, using the DOS boot disk, using the fdisk / MBR option to recover this error) 4, LILO stops the second phase of the load code at the LIL is not At the address it finds or is difficult to read the image file of the system, run the LILO 5, LILO's demonstration in Lil_ stopped the indicator in the system image file, maybe the / boot / map file is broken or moved. (The four cases, you can use the Linux boot disk created when installing Linux, then type LILO to recover, there is no recovery, please use DOS's FDISK / MBR to try it, otherwise it can only be reloaded. 6, First Boot Sector Doesn't Have A Valid Lilo Signature is usually /boot/boot.b file early, the INSTALL = instruction in the /etc/lilo.conf file points to a LILO, not the launch thing. 7, Chain Loader Doesn't Have A Valid Lilo Sinature Description / Boot/chain.b file is destroyed or /etc/lilo.conf's loader = instruction points to LILO, think it is not a chain loader. Boot.b Auxiliary Launcher code is called by MBR's primary start program code and uses it to launch a Linux kernel image. All image = instructions in the lilo.conf file use this loader by default. The role of chain.b startup program is to boot the DOS and other similar operating systems. His usage is the use of other = sections in the lilo.conf file, which can set a single starter for the specified section to use the LOA DER = instruction. To avoid most of the LILO issues, it is usually always re-running LILO when installing a new kernel or change the drive. Be sure to pay attention to an error or warning message generated when the MBR and its boot image file. Use the -v option can be Get more details. When the LILO image file is destroyed (including the virus destroyed the partition table and MBR), keep a labette at any time, and back up the MBR and partition tables of the drive. Copy / etc / lilo.conf, the above MBR backup, and some small but important system files are saved on the emergency recovery disk, and they will keep them updated with the system.
