Lilo Error Messages
Contents |
Haritası Araçlar Sayfa Bağlantıları İlğili Değişiklikler Özel Sayfalar Sponsors Diğer Diller Deutsch Español SDBtartışmaKaynağı görgeçmiş SDB:LILO fails: Error messages and their interpretation tagline: openSUSE sitesinden Konu başlıkları 1 lilo lil Symptom: 2 Interpretation 3 Solution: 4 Data for support: Symptom: When booting
Eileen Pollock
with LILO, the machine hangs after displaying a part of the word LILO on the screen. Interpretation The LILO start-up code consists of two parts: The "first stage" in a boot sector and the "second stage" in /boot/boot.b. During the installation of LILO, a map file is created, usually /boot/map, where LILO finds the necessary pointers (sector addresses) to the operating systems (Linux kernel, etc.) that should be started. (The following is taken from section 5.2.1 of the original LILO User's Guide by LILO author Werner Almesberger) When LILO loads itself, it displays the word LILO Each letter is printed before or after performing some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem. (nothing) No part of LILO has been loaded. Either LILO isn't installed or the partition on which its boot sector is located is not active. L error 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. This condition usually indicates a media failure or a geometry mismatch. LI 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. 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 geometr
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 https://tr.opensuse.org/SDB:LILO_fails:_Error_messages_and_their_interpretation 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 http://wiki.wlug.org.nz/LiloErrorCodes 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, 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 pro
/ November22, 2015; 10 months ago(2015-11-22) Repository lilo.alioth.debian.org/ftp/sources/ Development status discontinued Type Bootloader License BSD license Website lilo.alioth.debian.org LILO (LInux LOader) is a boot loader for Linux https://en.wikipedia.org/wiki/LILO_(boot_loader) and was the default boot loader for most Linux distributions in the years after the popularity of loadlin. Today, many distributions use GRUB as the default boot loader, but LILO and its variant ELILO are still in wide use. Further development of LILO was discontinued in December 2015 along with a request by Joachim Weidorn for lilo error potential developers. Contents 1 Overview 2 LILO files 2.1 lilo.conf 2.2 /boot/ 3 Master boot record 4 Output 5 Error codes 6 ELILO 7 See also 8 Notes 9 References 10 External links Overview[edit] LILO does not depend on a specific file system, and can boot an operating system (e.g., Linux kernel images) from floppy disks and lilo error messages hard disks. One of up to sixteen different images can be selected at boot time. Various parameters, such as the root device, can be set independently for each kernel. LILO can be placed in the master boot record (MBR) or the boot sector of a partition. In the latter case, the MBR must contain code to load LILO. At system start, only the BIOS drivers are available for LILO to access hard disks. For this reason, a very old BIOS access area is limited to cylinders 0 to 1023 of the first two hard disks. For a later BIOS, LILO can use 32-bit "logical block addressing" (LBA) to access the entire capacity of the hard disks the BIOS has access to. LILO files[edit] lilo.conf[edit] The lilo.conf file is typically located at /etc/lilo.conf. Within lilo.conf there are typically two section types. The first section, which defines the global options, contains parameters which specify boot location attributes. The second section(s) contain parameters associated with the operating system images to be loa