[lug] LILO becomes LI...
fredrick at acd.ucar.edu
Wed Nov 15 05:17:14 MST 2000
Just a note -- some of the more recent versions of LILO now have
an ability to locate the image beyond the first 1024 blocks of your
hard drive -- the version that comes with Redhat 7 for instance
allows you to add an option to /etc/lilo.conf, "lba32", alone on
a single line (that is do not use the append= construct). This doesn't
get around other BIOS limitations -- we had some problems locating Linux
beyond 8GB on some older systems for instance, but it does fix the 1024
problem. As a result, we haven't thrown away our copies of Partition
An RPM for the more recent LILO is located at:
Hope that helps, --Tim Fredrick (fredrick at acd.ucar.edu)
NCAR/ACD Computer Systems Administration
> Sounds like the problem is that you didn't create a /boot directory that is
> located on the fist 1024 blocks of your Hard Drive..
> To view the "Contents" of the 1024 partition is to run fdisk -l /dev/hda
> (for instance) not sure exacty how you have linux installed.. but this kind
> of a problem normaly happens when you have a dual boot system and you
> installed both OSes on the same Hard Drive or something like this and linux
> is installed on after the fists 1024 blocks of the HD.. then you're gonna
> need partitioning software like Parition Magic and actually move your data
> back (not sure how else to explain this but that's how the Graphical Part of
> Partition Magic works and move it back so about 10MB of free space appears
> at the begining of the disk and then when you install linux you're gonna
> have to mount /boot to that 10MB partiton that you created using Parition
> Magic.. this is just a stab in the dark as to what's going on I've
> experienced this problem before..
> Brian Carpio - MCP + I, MCSE, SCSA, (working on RedHat Certification just
> wait hehehe)
> ----- Original Message -----
> From: "John Starkey" <jstarkey at advancecreations.com>
> To: <lug at lug.boulder.co.us>
> Sent: Tuesday, November 14, 2000 9:45 PM
> Subject: Re: [lug] LILO becomes LI...
> > Ok. I gave myself a couple days to think on this. Still clueless.
> > > LI indicates a geometry mis-match with your hard drive. According to
> > > the lilo documentation:
> > >
> > > LI The first stage boot loader was able to load the second stage
> > > 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.
> > >
> > > Check to make sure the kernel you are trying to boot is on a partion
> > > that exists entirely under 1024 partitions.
> > What is the mapping software? man -k map returns no hits that seem
> > relevent to my newbie mind.
> > How can I view the contents of the first 1024 of the drive? The kernels
> > I've tried to boot are the 2 kernels I was running before I did the RH CD
> > install. Why would RH have moved those two kernels?
> > TIA,
> > John
> > _______________________________________________
> > Web Page: http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
More information about the LUG