Red Hat Bugzilla – Bug 56452
Need to handle invalid data in lilo.conf better on upgrades
Last modified: 2007-04-18 12:38:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4)
Description of problem:
I tried to upgrade a laptop running 7.1 booting with lilo
to 7.2 booting with grub All went ok until the last pkg was being written
and I got a crash and I saved to floppy for you
Version-Release number of selected component (if applicable):
The laptop is an IBM A22 mod 2628
I tried again to install. I only needed to upgrade 1 pkg and it went fine
and I got to install the boot loader and it is running now.
Created attachment 37903 [details]
anaconda dump to floppy from failed upgrade
katzj, any ideas here?
You don't happen to have a copy of the /etc/lilo.conf from prior to the upgrade
would you? (it would have been /etc/lilo.conf.rpmsave, but that probably got
overwritten on the second upgrade)
Created attachment 39104 [details]
lilo.conf from before upgrade
lilo.conf from before backup is available. I was using lilo and had made a
custom 2.4.8 kernel. With the install I took RedHat's advice and migrated to
grub -- still keeping grub on the 1st sector of boot partition, not the MBR due
to sharing with Win2000
I will also show you the lilo.anaconda
Created attachment 39105 [details]
A similar problem is when doing a "fresh" install over a previous install.
If you used lilo on the previous redhat, and install grub, the MBR doesn't
get wiped, grub goes into the first partition, and at boot it hangs on half
a lilo (LI).
The last thing reported we can't do anything about (though we handle upgrade
bootloader stuff differently now). The others are due to quotes in the
lilo.conf and we handle that better now in CVS
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.