Upgrade to F16 using preupgrade fails..

[esbennn]

Hello all

I am trying to upgrade from F15 to F16 via preupgrade.
The first part goes fine, with all the right files getting downloaded.

When i hit the reboot button, it reboots just fine, bypasses grub, and enters the installer dialogue just fine.

But when it's examining the filesystem (the small progress bar going back and forth really fast), it stops and opens a window, that says an unexpected error has occurred. It tells me it's probably a bug (with the possibility to see a lot of details), and asks me to report it to bugzilla.
After doing so succesfully, my only option is to close the bug-window, which then terminates the entire upgrade screen, and takes me to a blue screen with some text at the buttom. Bummer.

Then i can ctrl+alt+F2 and type 'anaconda' to restart the upgrade, but then it gives me the same install wizard, as it would if i were installing from live media - with only options to reinstall, not upgrade.

What to do??

Any help much aprreciated

[thom12]

Hej

Did you read "How to use PreUpgrade" (http://fedoraproject.org/wiki/PreUpgrade) before you started?

[esbennn]

Originally Posted by thomas nalbach

Hej

Did you read "How to use PreUpgrade" (http://fedoraproject.org/wiki/PreUpgrade) before you started?

Yes, that's the procedure i used.
After my first two failed attempts, i tried to clean orphans before rebooting, but the result was the same.

I have a slight feeling it has to do with my hard drive, since the error occurs when the setup is examining filesystem?

Oh, and thanks for the quick reply

[liderbug]

I had problems too - new computer - burned a fc16_64 iso - it loaded and ran with a large fubar. So I took an old fc14(64)-live dvd, booted live, install to disk and had fc14 running just fine - then tip-toeing on thin ice reloaded my fc16 dvd and did an upgrade. - ran fine - 3.1.1-1.fc16.x86_64 running just great. But like I said a new virgin install of fc16_64 on clean disks ... did not go well. Hope this helps.

hardinfo blowfish = 2.07

c

[esbennn]

Originally Posted by liderbug

I had problems too - new computer - burned a fc16_64 iso - it loaded and ran with a large fubar. So I took an old fc14(64)-live dvd, booted live, install to disk and had fc14 running just fine - then tip-toeing on thin ice reloaded my fc16 dvd and did an upgrade. - ran fine - 3.1.1-1.fc16.x86_64 running just great. But like I said a new virgin install of fc16_64 on clean disks ... did not go well. Hope this helps.

hardinfo blowfish = 2.07

c

Interestingly strange ...
So maybe i should just grab the F16 live-dvd and upgrade from that?
Will that also remove the 'upgrade to F16 (Verne)" entry in my grub?

[Mariusz W]

Originally Posted by esbennn

After my first two failed attempts, i tried to clean orphans before rebooting, but the result was the same.

How did you do that? By booting from a Live CD?

So you tried to reboot a couple of times now and the anaconda installer each time behaves the same way?

[esbennn]

Originally Posted by Mariusz W

How did you do that? By booting from a Live CD?

So you tried to reboot a couple of times now and the anaconda installer each time behaves the same way?

Well i just did

package-cleanup --orphans

which you are actually supposed to do after the upgrade has finished.

I didn't boot from a live cd, but using the "Upgrade to F16" entry, that preupgrade puts in grub

[nyjetshead]

The live CD is not an upgrade path
Did you try the DVD, that can be used to upgrade a system.

Preupgrade has issues when it finishes but (I had a mess to fix when I used it)
The DVD is supposed work better.

Can you boot your system with the F15 kernel still?

[esbennn]

Originally Posted by nyjetshead

The live CD is not an upgrade path
Did you try the DVD, that can be used to upgrade a system.

Preupgrade has issues when it finishes but (I had a mess to fix when I used it)
The DVD is supposed work better.

Can you boot your system with the F15 kernel still?

I'm downloading the dvd media right now - hopefully it will do the trick.
But yes, i am still able to boot into all the F15 kernels. They're listed in grub below the upgrade-entry.

I will let you know when i get to try the dvd

---------- Post added at 06:22 PM ---------- Previous post was at 02:38 PM ----------

Okay, tried the dvd upgrade. No luck.

When booting into dvd, checking install media goes fine.
Then i select language, keyboard layout, and it examines filesystem.
Then i get to choose between upgrading current fedora and install fedora.
And when i choose 'upgrade', the exact same thing happens, as when trying to upgrade with preupgrade. A very long error message, that i can either close or file as a bug.
Either way, it eventually shuts down the installer.

Unfortunately i'm unable to copy-paste the error report, and i cant seem to find it at bugzilla.redhat, though i filed it.

Any ideas?

[nyjetshead]

Too bad it didn't work for you.
We we need to know more information about the error to help you though.
Did you start out with F15 or did you upgrade to F15 from a previous release?

[esbennn]

This is a fresh install of F15.
Ill try an see if i can somehow get the data from the error message, and ill post it here.

[AdamW]

you say you filed the bug as requested, right? Can you like to the bug report? It should contain some of the information we need.

[esbennn]

I did file the report, twice now. But when i log in at bugzilla.redhat.com, it doesn't show up under 'my bugs'

But it's like a long list, that mentions all my hardware a couple of times ..

[esbennn]

Okay, so i decided to simply do a fresh install to solve this.
So i put in my brand new f16 dvd, and proceeded to the install section.
And after customizing my partition layout and clicking 'write changes to disk', guess what ...?
Same error shows up!

Fortunately, i have been able to locate the bug: https://bugzilla.redhat.com/show_bug.cgi?id=693095

Is this an anaconda problem, or do i have some incompatible hardware??

Please help

[smellslikefries]

I am seeing this problem as well

FC15 doing preupgrade, rebooting and getting "this is probably a bug".

Any workarounds discovered?