Red Hat Bugzilla – Bug 66561
installer cannot upgrade boot loader in root partition
Last modified: 2007-04-18 12:43:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-3custom i686)
Description of problem:
When LILO is in / partition, the installer apparently cannot find it, since it
doesn't give the option of upgrading the current boot configuration, during an
When you choose to create a new boot configuration in an Upgrade install, or you
choose to do a new install, Red Hat Linux installations list the / partition as
one of the two places that the boot loader can be installed into.
Because your installer ( RH 6.1, in my case) suggested the / partition, I think
the Upgrade installer should look there for a boot configuration, and allow
Version-Release number of selected component (if applicable):
(the first time RH 7.3 install got this, I cancelled the install and openned a
service request. Rerunning the 7.3 Upgrade install got the same results. I
have not tried installing a new 6.1 and then putting another 7.3 on top of it,
Steps to Reproduce:
1.Install Red Hat Linux 6.1 into empty partitions ( / /home /var /temp /opt )
2.When asked where to put LILO, select the root partition
3.Install Red Hat Linux 7.3 as a Upgrade
4.Observe that when it gets to locating the boot loader, the choice to upgrade
the current boot configuration is greyed out
Actual Results: RH 7.3 installer would not allow upgrading the current boot
configuration. When I selected create a new boot configuration, it offered me
the choice of putting LILO in the MBR or the / partition (i.e. where it already
Expected Results: Since it understands installing into the / partition, I
expected it to look there, find the existing LILO install, and offer the choice
Update existing boot configuration.
This was originally Service Request 206001. The technician there said that it
should be reported here.
OS/2 Boot manager is installed in the MBR
This probably won't cause serious difficulty to users with enough experience to
maintain their own LILO or GRUB configurations, but will likely stump users who
never go anyplace that menus can't take them. This is the sort of user which
Linux will have to be able to draw, in order to have a large desktop presence.
Assigning to an engineer.
What did you lilo.conf look like before the upgrade?
Created attachment 61988 [details]
lilo.conf prior to running RH 7.3 install
I've attached the the last lilo.conf before the install.
When I reran the RH 7.3 install and selected create a new boot config, it
offered the choice between the MBR on /dev/hda and /dev/hda10 .
And am I correct in assuming that you don't have /boot as a separate partition?
That's correct. Here's df -T output. The first group of partitions are
mounted R/W by default:
[root@PII450DMW new]# df -T
Filesystem Type 1k-blocks Used Available Use% Mounted on
/dev/hda10 ext2 427796 190776 214933 48% /
/dev/hdc7 ext2 979450 639559 289288 69% /home
/dev/hdc9 ext2 2035606 1219739 710643 64% /opt
/dev/hda14 ext2 2016016 1791392 122212 94% /usr
/dev/hdc8 ext2 1018298 119806 845881 13% /usr/local
/dev/hdc6 ext2 349910 65680 266159 20% /var
none tmpfs 127888 0 127888 0% /dev/shm
/dev/hda2 hpfs 313266 191344 121922 62% /C:
/dev/hda6 umsdos 120204 84364 35840 71% /D:
/dev/hda7 hpfs 160618 67552 93066 43% /E:
/dev/hda8 hpfs 208812 164834 43978 79% /F:
/dev/hda9 hpfs 64228 40756 23472 64% /G:
/dev/hda12 hpfs 32098 21183 10915 66% /I:
/dev/hda13 hpfs 3076416 1620550 1455866 53% /J:
/dev/hda16 hpfs 5767302 4940999 826303 86% /L:
/dev/hdc12 hpfs 5245190 1290309 3954881 25% /M:
These additional partitions aren't normally mounted. They're used for backups
and disaster recovery:
/dev/hda11 umsdos 24002 12838 11164 54% /H:
/dev/hdd5 umsdos 513776 0 513776 0% /N:
/dev/hdd6 hpfs 38917430 24762379 14155051 64% /O:
/dev/hdc11 ext2 101075 13357 82499 14% /altslash
/dev/hdc5 ext2 5065710 3900780 902671 82% /home/backups
The /?: partitions are shared with OS/2.
I've tweaked this code some and it gets it right for me in our current internal
Time tracking values updated
I'm going through Bugzilla closing some bugs that have been marked as Modified
for some period of time. I believe that most of these issues have been fixed,
so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists,
please reopen this report and mark it as Reopened.