Red Hat Bugzilla – Bug 133761
Upgrade of ICH6 based systems fail due to ATA->SATA move
Last modified: 2014-03-16 22:48:42 EDT
Description of problem:
Fedora Core 2 has no knowledge of ICH6M serial ATA and installed the
system using the generic IDE driver. In the fstab it decided that swap
was /dev/hda3. When I try and upgrade it can't find /dev/hda3 as it is
now /dev/sda3. If I fix this then it reports that it cannot find the
boot loader to upgrade.
This is a little bit wider spread than just being an anaconda problem
(and more than just ICH6, too). Assigning to distribution and leaving
myself on the cc list.
Bill -- any thoughts here?
I'm not sure I see any reliable way to tell on upgrade
which-FS-became-this-other-device. Especially before booting said
1. The real swap partition will have a swap header on it
2. 99% of the time it'll be on the same physical disk as the root fs
we found by label
3. If we can't mount it we can advise the user and not mount it
Ditto grub - you can look for a boot sector
For 1), we *should* be doing swapon --look-for-swap anyway. (Not that
that exists, but you get the idea.)
For #3, I assume you mean in the installer? swapon already prints
errors, of course.
Will this be an issue of RHEL3 U3 to RHEL4 upgrades? What device
nodes does U3 use for SATA?
CC'ing mkinitrd maintainer.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information. This bug was
originally filed against FC3 and has remained in NEEDINFO state for quite some
time. Many packages and bugfixes have been made since the last substantive bug
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.