Description of problem: I have a Fedora system with two disks (one has the OS, other has data). I wish to upgrade this to Fedora 14 using the install DVD. The dialogue goes something like (and this is from memory so apologies if the details are incorrect): Select "install or upgrade" from the boot menu Welcome Select language and keyboard Use basic storage devices? (yes) Install new system or upgrade existing system? (upgrade please) Which system to upgrade: Fedora 12 on /dev/sda5 I then get a dialogue which asks me to select "which devices you'd like to use as data devices (these will not be formatted, only mounted) and which devices you'd like to use as installation target devices (these may be formatted)." Followed by a list of the model numbers and sizes of the two disks. I'd rather neither of them were formatted, thanks! However, it insists I pick one. In order to choose which one I have to switch to the shell console and use fdisk and/or smartctl to print out the serial numbers of my disks (see Bug 574120) - this despite the fact that it called one of them /dev/sda earlier when it asked me which installation to upgrade. It tries to reassure me that my filesystems "will not be reformatted unless you choose to do so during customization" - but there is no customization step when doing an upgrade, and this doesn't really negate the fact that it asked me to choose a disk which "may be reformatted". So my question really is: is this dialogue necessary during an upgrade? If it is, it needs to be reworded to remove *any* implication that the disks might be reformatted. Thanks
That screen is not meant to show up on upgrades, no. I'll take a look.
This will be fixed in the next build of anaconda for rawhide. However, this seems like a prime candidate for an F14 common bug. Here's the fix in case someone would like to make an updates.img: http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=31e6bd7091750737976462563038ede8661f4c74
*** Bug 655426 has been marked as a duplicate of this bug. ***
*** Bug 656533 has been marked as a duplicate of this bug. ***
*** Bug 605251 has been marked as a duplicate of this bug. ***