Lilo Error Li
will ever be answered. You can be published anonymously - just let us know! Help on LILO stopping at LI From Alessio Frenquelli Answered By Heather Stern Hello, I start thanking you for any help ... I am stuck at this stage, I am not a GURU on LINUX and I cannot overcome the problem. Therefore I cannot really point to what has been changed or went wrong. Under the Internet I found many, many errors entries pointing to LILO not being able to load in a disk that is above the 1024 cylinders [Heather] Yes, it used to be LILO's biggest bug, though not its loudest (that one is people using it wrong and then wailing what are they going to do now that their MBR is mangled). But ever since the new version those are old messages. The normal solution until it came out, was to create a tiny /boot near the beginning of the free space - even most dual booters could manage to slip a 20 Mb partition below the boundary. This works because on the kernel and bootmap needs to be below the line; once the kernel is loaded you are no longer working with real mode BIOS issues at all, you are fully in protected mode and can access everything the kernel is built for. In my case LILO always worked so far, and I did not surely changed the disk size, done any repartitioning under Windows NT nor under Linux. Under Windows, I have run Program => PartitionMagic =>PartitionInfo and I am attaching the output of the command to this email in case you need to see in details my machine's partitioning. [] So you normally use partition magic for your dual boot menu, I'm guessing. If so, that is what is presently in your MBR, and would be overwritten (***warning warning danger will robinson*** or at least look real carefully that you've set up stanzas for NT also first!) if you change boot = /dev/hda ENVIRONMENT Dual bootable Laptop, Toshiba Tecra 8100; one partition is Windows NT workstation, the other is Linux RedHat 6.1. PROBLEM Linux 6.1 LILO does not longer boot properly. Just stop at the word "LI". SOME TROUBLESHOOTING INFO Fortunately I have the boot diskette, and booting from it, I can successfully get to Linux. When running : << /sbin/lilo >> I got messages: [root@afrenquelli /etc]# lilo Warning:
July 26, 2007 in Linux, TroubleshootingQ. My Linux system says LI while booting system and then boots procedure freezes or halts. How do I solve this problem?
A. LILO is a generic boot loader for Linux. This error means few things. LI characters indicate that LILO is having problems. It cannot boot the system.a) Goto BIOS and set LBA mode for hard disk and reinstall Linuxb) Make sure /boot partition created below the 1023rd cylinder on the hard drive, if not repartition and reinstall Linuxc) See this page for more information. http://www.tldp.org/LDP/LG/issue65/tag/4.html Share this tutorial on:TwitterFacebookGoogle+Download PDF version Found an error/typo on this page?About the author: Vivek Gite is a seasoned sysadmin and a trainer for the Linux/Unix & shell scripting. Follow him on Twitter. OR read more like this:Linux reset forgotten root passwordError /dev/hdX does not have any corresponding BIOS drive and Solutiongrub.conf for Windows vista or xp dual bootWhat do I do http://www.cyberciti.biz/faq/lilo-stops-at-li-error/ if my Linux Server / Workstation does not boot?HP-UX: Boot Into Single User ModeLinux create an installation boot diskBoot Linux Grub Into Single User ModeBoot Ubuntu Linux into Rescue mode to fix systemLinux: How to delete a partition with fdisk commandDual boot 2 or 3 different Linux distributions on a laptop{ 0 comments… add one } Security: Are you a robot or human?Please enable JavaScript to submit this form.Cancel replyLeave a Comment Name Email Comment You can use these HTML tags and attributes: Receive Email Notifications? no, do not subscribeyes, replies to my commentyes, all comments/replies instantlyhourly digestdaily digestweekly digest Or, you can subscribe without commenting. Tagged with: boot partition, error messages, freezes, generic boot loader, hard disk, lba mode, lilo, Linux, linux systemNext FAQ: Create / modify keyboard shortcuts in Gnome under Linux / UNIXPrevious FAQ: Howto: Backup CentOS / Fedora Linux / Red Hat Enterprise Linux server system Featured Articles:30 Cool Open Source Software I Discovered in 201330 Handy Bash Shell Aliases For Linux / Unix / Mac OS XTop 30 Nmap Command ExaError 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 http://wiki.wlug.org.nz/LiloErrorCodes 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 http://www.justskins.com/forums/dual-boot-problems-lilo-90754.html 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 lilo error 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 lilo error li 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, 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
LILO stops at LI - Linux Setup, Configuration & Administration On Wed, 25 Jun 2003 08:28:44 -0600, Brian Myers wrote: > I know this is a common problem in setting up dual-boot systems. I've > searched through the newsgroups; apparently the likely cause is some > mismatch in disk geometry. But I've tried messing with those settings in > lilo.conf without succeeding. So here's the relevant information; maybe > one of you can diagnose it better than I. > > > > By default, my lilo.conf came this way: > > # Support LBA for large hard disks. > # > lba32 > #linear > > # Specifies the ... Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode June 26th,02:50 PM #1 Re: dual boot problems: LILO stops at LI On Wed, 25 Jun 2003 08:28:44 -0600, Brian Myers wrote: > I know this is a common problem in setting up dual-boot systems. I've > searched through the newsgroups; apparently the likely cause is some > mismatch in disk geometry. But I've tried messing with those settings in > lilo.conf without succeeding. So here's the relevant information; maybe > one of you can diagnose it better than I. > > > > By default, my lilo.conf came this way: > > # Support LBA for large hard disks. > # > lba32 > #linear > > # Specifies the boot device. This is where Lilo installs its boot > # block. It can be either a partition, or the raw device, in which > # case it installs in the MBR, and will overwrite the current MBR. > # > boot=/dev/hde2 > > > > Brian > The boot loader can be either on the MBR or on a partition BIOS parameter block,"BPB." [url]http://www.tldp.org/HOWTO/mini/LILO-2.html#ss2.1[/url] From your lilo.conf, it looks like the loader is on the BPB, and not on the MBR. I think in this case, you would 1.Fix lilo.conf: boot=/dev/hde 2.Install LILO on the MBR of hde 3.Save that MBR as a file (as I presume you have been doing.) BTW, I switched to grub as the loader