Help convincing Anaconda to upgrade from Fedora 10

[quietdragon]

I'm trying to upgrade from Fedora 10.

I have a RAID1 system with the following partitions in the stated order:

1. a multiboot grub RAID1 partition
2. a RAID1 system partition
3. a swap partition
4. a RAID1 data partition (with /home, etc).

This used to be a Fedora 6 system, and I've upgraded to Fedora 7, then Fedora 8, Fedora 9, and then to Fedora 10 using the DVD installation image booting from a USB stick with no problem. The Fedora 10 installer detected my existing installation in the 2nd partition, and went to work.

I tried to get to Fedora 11, but Anaconda bailed with an exception complaining that FSSet had no attributes.

Thinking things might be better with Fedora 12, I tried going straight to Fedora 12 from Fedora 10. In this case Anaconda didn't get an exception, but doesn't give me the option to upgrade. Apparently it thinks this is a pristine system and is hell bent on a clean install.

What do I have to do to convince Anaconda to upgrade my Fedora 10 system?

---------- Post added at 07:52 PM CST ---------- Previous post was at 04:27 PM CST ----------

The problem is that the Fedora 12 installer (unlike the previous ones) does not start the RAID1 arrays prior to scanning for live systems. The RAID1 partitions have type 0xfd.

At the Welcome to Fedora splash screen (either in text mode or GUI mode), use the ALT-CTRL-Fn or ALT-Fn sequence to get a shell. I mounted the system partition as ext3 readonly and copied out /etc/mdadm.conf to /etc/. I then started the RAID1 system and data arrays manually (eg mdadm -A /dev/md1).

Then switch back to the splash screen and continue the installation. With the RAID arrays running, the installer can find the existing installation and offers the upgrade screen.

[madhavdiwan]

With the RAID arrays running, the installer can find the existing installation and offers the upgrade screen.

does this mean your issue is solved?

[quietdragon]

does this mean your issue is solved?

It means that I have a workaround as I've described.

I still consider this a bug because I believe the upgrade procedure (even on RAID1 systems) should work out of the box as it used to (eg the Fedora 10 installer). I've logged the issue as a bug:

https://bugzilla.redhat.com/show_bug.cgi?id=569098