Description of problem: Upgrade from FC4 to FC5 fails with an Anaconda exception. My system contains an HPFS pertition. However, even mount disabling of that partition in /etc/fstab (sort of derived from bug 186998) did not solve the problem. How reproducible: I tried to upgrade my FC4 installation through the standard FC5 CDs. Actual results: Anaconda still fails in grahical and text mode. Expected results: Enable update of existing FC4 system. Additional info: Due to extensive customization, I would appreciate if a completely new installation could be avoided. My system is currently using a custom-built kernel (2.6.16-1.2108) with enabled Software Suspend2 and HPFS support.
Created attachment 129033 [details] Dumpfile created by Anaconda
Could you please attach a complete list of your partitions and what type each is? Also, do you have an operating system suspended while you're trying to upgrade?
Created attachment 129579 [details] Partition layout of hdd where CD upgrade fails The layout was created by the partioning software DFSEE. The forth column (this is a bit abbreviated) gives the partion IDs under Linux. In case it helps: The notebook is booted through an alternative boot manager called AiR-Boot which resides in the MBR. When booting FC from AiR-Boot, grub in /dev/hda1 is called. The IBM-boot manager in /dev/hda2 is not used anymore. And no, there were are no suspended other operating systems active during the attempted upgrade.
Sorry, I was imprecise: "no other suspended operating systems active" should of course mean that no other OS was suspended at that time. Furthermore, after rechecking the Anaconda dump file, I noticed that it complained about duplicate partition labels. I find this strange because I believe that there are no such duplicate names left. Indeed there were at first such duplicates as a result of a relocation of / and /home partitions. However, I believe that they have been long since cleared by using: e2label /dev/hda17 "" (one sample, /dev/hda17 being - iirc - the old / partition) Besides the / resp. /home label was applied to the new (current) such partitions. If I overlooked something here, please let me know!
It looks like somehow, a device on your system has been given an invalid label. You're getting a traceback because we are trying to print a string that contains some invalid characters. Unfortunately, we don't have the debugging information here to tell what device has the problem. I've added an additional dialog to catch this error and display the device in question. Please try an upgrade to F7 when it comes out and see if you still run into problems. If so, you should at least have an idea of what device needs to be fixed. Thanks for the bug report.