Description of Problem: Prior to installing and upgrade from 7.0 to 7.1 on
SCSI based HP system, I made a mirror backup of /dev/sda onto /dev/sdc.
Upgrade 'spotted' that /dev/sdc contained a bootable
drive with O/S on it, asked (with radio buttons) which drive I wanted to
upgrade. I chose /dev/sda and when upgrade was finished, all programs
(installed rpms) on /dev/sda were upgraded...BUT...the new
kernel was placed on /dev/sdc anyway (but not /dev/sda) and its MBR (but
not /dev/sda) was updated. This effectively left both /dev/sda and
/dev/sdc unbootable! /dev/sda had new O/S but old kernel and MBR; /dev/sdc
had old O/S but new kernel and MBR...
This is just a report of bug to try and be helpful, I am not requesting any
assistance on this.
Steps to Reproduce:
Thanks for the report.
I'm assigning it to the installer component.
this is because the installer uses 'mount by label' to mount your filesystems.
The last found label wins, so the "/" label on the sdc drive gets mounted.
Deferred to future release.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.