LILO User Guide MBR Root Dezo Lilo.conf Error Analysis Forgot Password

LILO User Guide

LILO Usage Guide 2001-05-01 10:30 Publisher: NetBull Readings: 252 Hubertzou hubertzou@linuxAid.com The original startup of the computer is controlled by the BIOS, initialization in some hardware (eg, memory, keyboard, etc.) Thereafter, it will try to load the main boot record (MBR) of the hard disk or the boot sector of the floppy disk. The MBR can operate in two ways, which is positioned to the active partition and load the corresponding guiding sector, and then complete the loading of the basic components of the operating system within the partition; second, it is loaded directly from a designated partition. Information, and through which the operating system such as LILO, GURB, OS / 2 Boot loader and PartitionMagic can be configured in this way. The boot sector of the floppy is equivalent to the boot sector of the hard disk activity partition, which is usually used to load the operating system on the floppy disk. Just install the multiple guides such as LILO on the MBR, active partition, or boot floppy disk, you can take over the control of the computer, and then the successor boot process is completed by the multiple guides. It is built in LILO to include a list of tabs, where it can be positioned to Linux kernel files, which can be linearly linear of LBA according to the cylindrical / head / sector (CHS) mode. Block mode, therefore, even if some SCSI control program LILO can operate well. First, MBR or the root partition of Linux first encountered LILO, and it is estimated that when you install Linux, you will be asked to choose Lilo installation, which is MBR or the root partition of Linux. If you have other boot management programs such as boot magic or system commander, and want to use them, then you should install lilo to the root partition of Linux. If you choose to use Lilo as a startup manager, you can choose MBR. If you want to pass parameters to the kernel during start, you should use MBR. After using LILO as the startup program, there will be a LILO: prompt after the machine starts, press the Tab key to see the list of operating systems that can be selected. Enter the operating system tag name to start to the corresponding operating system, or enter the carriage return to the default operating system directly. The images mentioned in lilo.conf can be more than 16. Second, LILO.CONF usually explain let us see a LILO boot profile (/etc/lilo.conf) instance: boot = / dev / hda3 map = / Boot / Map Install = / Boot / Boot.b Prompt Timeout = 50 Message = / Boot / Message Default = New Image = / Boot / VMLinuz-2.4.3 Label = New Read-Only Root = / dev / hda3 image = / Boot / vmlinuz-2.2.19 label = linux read-only root = / dev / hda3 other = / dev / hda2 label = DOS This profile specifies that LILO uses the main boot record on the / dev / hda path. When startup, the boot loader will wait for 5 seconds to let you press the Shift key. If not pressed, the first core image (VMLinuz-2.4.3) mentioned above will be started. If you press the SHIFT key, the boot loader will ask which image you want to start. In case you forgot this choice to start which image, press [Tab] there will be a menu to choose from.

You can choose or start this new core, or start a reliable kernel (VMLinuz-2.2.19) or start a different operating system. As can be seen, a configuration file begins with a series of global options, which is a description of the different image options. The options in the image description will overwrite the content set by the global option. The global option section Boot = boot-device setting the name of the device that includes the boot sector (such as a partition of a hard disk). If this keyword boot sector is not specified, it will be read from the device installed as a root file system (or may also write). Compact Attempts to combine multiple read requests of adjacent sectors into one read request. This greatly reduces the read time and makes the system description (MAP) smaller. In particular, use the Compact option when reading from the floppy drive. DEFAULT = Name uses specially specified images as the default startup image. If the defaul option is not set, the image that the earliest appearing in this configuration will be used as the startup image. DISC = Device-Name Defines non-standard parameters for a particular hard disk. It is especially useful for defining the BIOS = parameter. If your hard disk's BIOS data is 0x80, 0x81 (sixteen), etc., it will not be able to determine which Linux disk corresponds to which BIOS disk (because this is determined in the BIOS settings and the type of BIOS). So if you use a non-general installation, you need to explain the corresponding relationship between the Linux disk and the BIOS disk. For example: Map = MAP-FILE Location Disk Description (MAP) file. If the MAP option is not specified, the / boot / map file will be used. Message = message-file Specifies a file that contains information displayed before running the startup prompt. There will be no information display in the time of waiting for the button after the LILO is displayed. In the information, the local display is emptied with FF characters ([Ctrl L]). The size of the information file is limited to 65535 bytes. If the information file is changed or canceled, you must rebuild the Disk Description (MAP) file. PROMPT does not wait for any button events to enter the launch prompt mode directly. If you set the PROMP option without setting an IMEOUT option, you cannot start itself. Timeout = Tsecs Sets a timeout option (in 10 minutes) for the keyboard input. If there is no button in the specified time, the first image will be automatically started. Similarly, if the user pauses too long, the password input will be canceled. The default timeout value is unlimited. In addition, both kernel configuration parameters append, ramdisk, read-only, read-write, root, and VGA can be set in global options. If it is not specified in the configuration bar of the corresponding core image, this setting value will be used to do the default default. Single Image Some a single image or starts with a row image = pathname (to prompt the file or device with a Linux kernel, or to start other independent systems with a row other = pathname to prompt to start other independent systems. The Label = NAME boot loader uses the main file name (without path) of each image description (not included). Different names can be used by setting variables label. Alias ​​= Name can use the second name to the same directory by specifying an individual name. Password = password with password protection image. Restricted If the parameters are specified at the command line, only the image is entered only if the image is started. The kernel option section If the started image is a Linux kernel, you can transfer the command line parameters to the kernel.

Append = string increases the specified options to the parameter line transmitted to the kernel. Its typical use to designate parameters that cannot be completely self-test or thoroughly investigating it. For example: append = "hd = 64, 32, 202" ramdisk = size This option specifies the size of the optional RAM disk. 0 indicates that any RAM disk should not be created. If this parameter is not specified, the RAM disk size created in the root file system is used. Read-Only When using the Read-Only option, the system is histed to read-only mode, and this option is recommended because the FSCK program requires only the file system read only. But don't worry that your root partition will not be written. In contrast, once the system starts, it will hister the root partition to read and write. Read-Write It specifies that the root file system should be loaded in a readable write. Root = root-device This parameter specifies the device that should be loaded as a root file system. If currently uses the specified name, the root drive is located on the device currently in the root file system. If the root device is modified by the -R parameter, use the appropriate device. If the OOT parameter is not specified, use the root device settings containing the core image (this setting is set to the root_dev variable in the Makefile file in the kernel, and can be modified by the RDEV (8) program later) VGA = MODE It specifies the VGA text mode that should be selected at startup. The following values ​​can be identified (ignore the case): Normal: Select the normal 80x25 text mode. EXTENT (or ext): Select 80x50 text mode. Ask: Stop and require the user's input (at startup): Use the appropriate text mode. A list of available modes can be obtained with VGA = ASK options or press [ENTER] when starting. If this parameter is not specified, the VGA text environment obtained in the core image is used. (This setting is to compile the kernel time in the kenfile file in the kernel's Makefile file) LILO can also make you manually passed these parameters in the LILO prompt. For example: LILO: Linux Single is to tell Linux to start Linux to enter a single user mode. When the boot area is damaged, you can start from the floppy disk, then specify the root of the hard disk to repair the hard disk boot sector. LILO: Linux root = / dev / hda3 LILO boots other types of operating systems and boot Linux as the same configuration, but simpler: other = / dev / hda3 label = dos table = / dev / hda Other Indicates the partition where the operating system is located, the same The image under Linux also needs to give a label (label), the Table option points to the device containing the partition table, this option is essent, because Lilo will look for the corresponding partition information from this partition table, then pass him Give the operating system to be started. Any changes to lilo.conf require re-run / sbin / lilo to ensure that the latest changes can be written to the partition. Also, if you upgrade the kernel or reconstruct the Initrd image, you also need to re-run / sbin / lilo. After running / sbin / lilo, you can see the following information: Added Linux * Added DOS indicates that the various images have been written to the partition, with * partitions are current default guidance partitions.

The default boot partition can be changed with the -d parameter: / sbin / lilo -d dos added Linux Added Windows * You can see the default partition has become Windows. Install = boot-file will install the specified file as a new boot sector. If the INSTALL option is not set, boot / boot.b is used as the default default value. LINEAR generates a linear sector address rather than a "sector / head / cylindrical" address. The linear address does not rely on the partition structure of the disk, and is translated during runtime. Note If the Linear option may make the boot disk cannot be transplanted, this is because the role of the service to determine the disk partition structure in the BIOS is unstable. When using the Linear option for the big hard drive, since the 3D sector address is unknown before startup, / SBIN / LILO may generate a reference to the unacceptable disk area. The LOCK allows the automatic recording of the boot command line as the default default value that is started later. This way, LILO will lock an option before manual cancellation. Loader = chain-loader This parameter specifies the chain loader that will be used. Use the default default /boot/chain.b. If it is from other devices instead of the first hard disk or floppy disk, you must specify a chain loader. Third, about LILO's question , first installed Windows, then install LILO when loading Linux. This is a problem of most Linux novices; some BIOS cannot recognize a hard disk greater than 8.4G, and the old LILO cannot identify the system kernel (kenel) that is greater than 1024 cylindrical. It is therefore possible that the problem is: LILO is loaded into the MBR, and the hard disk partition prepared for Linux is far outside 1024 cylinder, so Linux can't boot; LILO is loaded into the Linux root partition (root partition), and it happens to be 8.4 Outside G, hang up! Solution: Maybe you have already installed Linux, don't delete it, you can use it! Ok, now start: 1. Use partitionMagic5.0 to start a 10M EXT2 partition, format it in the beginning of the first hard disk. It is best to prepare the partition prepared for Linux, and save the trouble. 2. Boot and RESCUE disk boot system with loadlin or linux. Mount 10m partition - / dev / hda1, suppose I use boot and rescue disk, Mount to / MNT / TMP. Copy / Boot / * and kernel image files to / dev / hda1 in the same directory, edit /etc/lilo.conf, plus the / dev / hda1 MOUNT path before all directories, and install LILO to / DEV / HDA1. Change to boot = / dev / hda1 in boot / map image = / boot/mlinuz-2.2.13 in lilo.coot/boot.b mess Install = / mnt/tmp/boot/boot.b message = / mnt / tmp / boot / bootmsg map = / mnt / tmp / boot / map image = / mnt/tmp/boot/vmlinuz-2.2.13 call lilo command, Reinstall LILO. After the system, it is over. Remember, to uninstall Linux, you can clear the LILO in the MBR with FDISK / MBR under DOS.

, multiple guidance NT, 9X and Linux, and want more than LILO, there is a detailed introduction in Linux NT-Loader-Mini-HOWTO; the main problem is how to write Linux's boot record Bootsect. ??? file, here you have successfully installed Windows9x with NT. (Here, it is assumed that Linux is installed in the first logical partition, under Linux / dev / hda5, Windows 9x is installed in the first primary partition, under Linux / dev / hda1, WindowsNT is installed in the second primary partition, in Linux Next to / dev / hda2.) Solution: Use loadlin or linux's boot and rescue disk (referring to the boot option of the BluePoint CD, it seems that there is no) to boot the Linux system. (Loadlin is better, there may be no mtools on the rescue disk, only mount cp umount "created this file: DD if = / dev / hda5 of = / root / bootsect.lix BS = 512 count = 1 Insert floppy disk , McOPY / ROOT/bootsect.lix A: Reboot the system, enter the DOS will quickly see your results, enter the root directory of the hard disk partition of NTLDR, or the root directory of the hard disk partition bootable before Windows "(here is here Windows9x). Copy the bootsect.lix file on the floppy disk. Remove Boot.ini's read-only, hide properties. At the end, add C: OOTSECT.LIX = "Go to Linux". The storage is exited, add Boot.ini's read-only, hide attributes. Reboot the system, try again! Note that after any modification of the Linux kernel, you must work with the above steps to guide the Linux system correctly. , install excess Linux system; the main problem is still if multiple Linux LILO or root partitions cannot be found by BIOS, the system will hang! Here, BluePoint Linux is installed in the first logical partition, under Linux / DEV / HDA5, Redhat Linux is installed in the second logical partition, under Linux / DEV / HDA6. Solution: We have the same 10M partition. Multi-copy to this partition, usually everything under / boot, there may be / vmlinuz - kernel files, depending on Linux distribution. It is recommended to separate it into two directories. Assume that is / bootblurpoint and / bootredhat.

Edit Lilo.conf file: Original boot = / dev / hda install = /boot/boot.b message = / boot / bootmsg map = / boot / map image = /boot/vmlinuz-2.2.13 label = linux root = / dev / hda1 modified to boot = / dev / hda1 install = / mnt/tmp/bootbluepoint/boot.b Message = / mnt / tmp / bootbluePoint / MAP image = / mnt / tmp / bootbluePoint / VMLinuz -2.2.13 label = bluepoint root = / dev / hda5 image = / mnt / tmp / bootredhat / vmlinuz label = redhat root = / dev / hda6 , drum from the main boot record and reuse the original Windows MBR 1. C:> fdisk / MBR 2. # / sbin / lilo -u / dev / hda 3. #dd if = / boot / boot.0300 of = / dev / hda bs = 446 count = 1 4. #cat / Boot / boot.0300> / dev / hda Note: Only when you install Windows 95, then install Linux, / boot / boot.0300 is your original Windows 95 MBR. <5>, Reissue LILO to MBR 1. Start with the installation floppy disk or disc to boot: boot: vmlinuz root = / dev / hdxy (such as: hda1) start completion, run # / sbin / libo 2. Start with two floppism After: #mount -t ext2 / dev / hda1 / mnt #Ln -s / mnt / boot boot #LN -S /MNT/Etc/Lilo.conf /etc/lilo.conf # / MNT / SBIN / LILO <六> , Copy lilo to floppy disk 1. / sbin / lilo -b / dev / fd0 2. Boot to boot: boot: vmlinuz root = / dev / hdxy (HDXY) Update / etc / lilo with redHat installation disk. CONF root = / dev / fd0 boot = / dev / fd0 Run: # / sbin / lilo -v , make a redhat linux boot disk #mkbootdisk - Device / dev / fd0 2.2.19 , Copy the kernel to the floppy disk, let the floppy disk directs Linux and hang the root file system on the hard disk. #fdformat / dev / fd0h1440 #dd if = / boot / vmlinuz of = / / fd0 #RDEV / DEV / FD0 / DEV / HDA1 four, LILO startup error display analysis <1> When Lilo is loaded with it, Display words "LILO": A letter is displayed for each completion of a specific process. If LILO has failed in some place, there are several letters on the screen to indicate where the error occurred. There is a more detailed description in the technical documentation. (Note: LILO is not a program, but a group of programs) Note that if the disk is instantaneous malfunction, some hexadecimal numbers may be inserted after the first letter "L". Unless LILO stops there, there is no serious problem.

<2> () LILO is not loaded at all. LILO may not be installed, or the partition is not activated. <3> L ... LILO's first part has been loaded and running, but it cannot be loaded into the second part of the boot program. The two-digit error code indicates the type of problem (see later " Disk error code "). This is usually not matched in media access failure or hard disk geometry (CHS, CHS). The first phase of LI LILO has been loaded into the second part of LILO, but does it fail. The error is that the hard disk geometric parameter does not match or /boot/boot.b does not have a reincarnation (MAP) installer after being moved. The second phase of the LIL has been launched, but it cannot read the descriptor table from the Map file (the Descriptor Table) is the medium error or the hard disk geometry does not match. The second part of the LIL? LILO is loaded into the wrong address. Typical reason is that hard disk geometric parameters are subtle or /boot/boot.b move without running a mapping installer. The LIL-descriptor table is destroyed. This may be that the / boot / map is not running the mapping installer or geometric parameter does not match. All parts of LILO LILO are successfully loaded. 1010101010 The partition has changed until reinstalling LILO, it is said that overclocking will also come. Disk error code: 0x00 "Internal Error". Generated from the LILO sector reading subroutine. It may be a crucial file to rebuild the Map file. Another reason is perhaps, when using the linear parameter, the cylindrical plane exceeding 1024 is available. 0x01 "illegal order". It should not happen, if it appears, means lilo to visit the hard drive that the BIOS does not support. When I finished this document, my friend met the L010101 ... of the mist, because he put Linux on the second IDE port (/ dev / hdc), plus the Disk parameter. 0x02 "Did not find address tag". Usually a media problem, try a few times. 0x03 "Write protection". The appearance is only when the write operation is written. 0x04 "Sector is not found". Typical causes is that the hard disk parameters do not match. 0x06 "Activation Sequence Change". This should be a short error, try again. 0x07 "invalid initialization". BIOS is not properly initialized, and the hot start may be helpful. 0x08 "DMA beyond limit". This should not occur, restart. 0x09 "DMA is trying to cross the 64K boundary". This should not occur, it is recommended to ignore the Compact parameter. 0x0c "invalid media". This should not happen, restart to see. 0x10 "CRC Error". The medium error was detected. It is recommended to start multiple times, run the MAP installer, write the MAP file from the bad block to normal media. 0x11 "ECC correction success". Read the error occurs and then correct, but LILO does not know this situation and terminates the startup process. 0x20 "Controller error". Should not happen. OX40 "Location Failure". This may be a media problem and try again. 0x80 "Disk timeout". Disks or drives are not ready. The medium is broken or the disk is not turned, and if it is started from the floppy disk, it may not be closed. 0xBB "BIOS error". This should not happen. If it occurs repeatedly, consider remove the Compact parameter or add / cancel the linear parameter. If an error occurs during the write operation, there is a prefix "W" before the error code. Although write errors do not affect the startup process, they indicate some errors because they hints that there is an error in the system, and a good suggestion is to reconfigure LILO into read-only. 5. Forgot your password? After the system starts, you will see a login screen based on the console or XDM-based login screen.