Description of problem:
when installing RH Linux 9.0 on a harddisk
aside to a former installation of RH Linux, e.g. version 7.3,
then it is quite likely that the former installation will
no longer boot after the install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install RH 7.3 on /dev/hda1
2. install RH 9.0 on /dev/hda3, try mounting any e2/e3 partition.
3. try to boot into RH 7.3
the old system does not boot.
the old system and the new system should both be able to boot.
the problem is possibly related to the way the e2labels are done.
when RH 9.0 installer runs, it forefully sets new labels on all
partitions so that the setup in /etc/fstab of RH 7.3 using the
LABEL=... stament will fail in finding the partitions on the next
I mean, if there are already existing labels on e2/e3 partitons
then the installer should take greatest care in order to preserve
them. I really specified "do not format" - but the installer still
feels entitled to change something significantly to the current
format data of the already existing partitons.
There might be further a problem for the GRUB boot loader when the
previously existing Linux system has installed its boot loader into
the MBR - i am not totally sure, so please watch out for that as well.
related bug is 89786
Did you mount the 7.3 partition during your Red Hat Linux 9 install? Where did
you mount it? What were the labels on the 7.3 partition before and after
all labels were the default labels of the respective install.
the system was removed from that disk
in the meantime for other testing,
so i can not check it's latest state,
but to my best knowledge i specified
the first partitions to be mounted
on the second install to something like /mnt/hda1 and alikes.
the labels were changed by the 2nd installation to match only
the second installation - it should have been the default label names.
We no longer change the label on filesystems which already have a label.
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.