F17: Worst upgrade ever?

[RupertPupkin]

I just upgraded my main machine from F16 to F17, and it has been an unmitigated disaster. The issues are too numerous to list, but the underlying theme is a shocking carelessness (like not even installing the F17 version of the kernel!) that I never expected to see from Fedora. The result is a system that's almost unusable. I can't even update the packages because yum seems thoroughly busted. Core packages like zlib are stuck on the F16 version. When I try to reboot the system hangs because it can't find the shutdown and other basic commands. X won't start. The grub configuration is completely screwed up. The list goes on.

Has anyone else here done an upgrade from F16 to F17? Has it worked OK for you? I almost always do upgrades instead of fresh installs, and I've never had problems like this, not even with the infamously terrible F8.

[neur0]

How did you perform the upgrade? Using the install CD?

[jsn255]

Pretty bad. First issue was to get anaconda's black screen out of the way. Solved via nomodeset to boot options.

After upgrade (preupgrade method) I'm in some sort of working fedora. The yum repolists shows fedora 16 and is quite stuck in there.

cat /etc/issue atleasts shows Fedora 17.

[steelaworkn]

Haven't done it yet. I'm waiting for y'all to pioneer it for me...Father's Day weekend is my traditional upgrade time. Hope it all works then.

[StyxD]

Originally Posted by jsn255

The yum repolists shows fedora 16 and is quite stuck in there.

I had to reset the computer while anaconda was running (one packet would not get upgraded, not even after half an hour). I managed to get all packages installed eventually, but yum still thinks it's Fedora 16 and preupgrade offers me an update to 17.

I thought it may be because the installation was borked because of the reset, but if other people have it too... could you please check if preupgrade offers you an update, too?

[beaker_]

Not yet. But, from what I see, maybe I'll install another debian instead.

[RupertPupkin]

Originally Posted by neur0

How did you perform the upgrade? Using the install CD?

I used the install DVD.

I figured out that there were several packages that yum was choking on (e.g. nfs-utils), and removing those has let me at least run yum update. But that still bombed and I have had to go into the /var/cache/yum directories and manually install the downloaded RPMs and resolve dependencies. And the update still doesn't complete (though it seems to have updated most of the crucial stuff). This is going to take a while to fix.

[jsn255]

Originally Posted by StyxD

I had to reset the computer while anaconda was running (one packet would not get upgraded, not even after half an hour). I managed to get all packages installed eventually, but yum still thinks it's Fedora 16 and preupgrade offers me an update to 17.

I thought it may be because the installation was borked because of the reset, but if other people have it too... could you please check if preupgrade offers you an update, too?

When i run preupgrade now, it does say: "Available fedora releases: Fedora 17 (Beefy Miracle)".

[Finalzone]

Originally Posted by RupertPupkin

Has anyone else here done an upgrade from F16 to F17? Has it worked OK for you? I almost always do upgrades instead of fresh installs, and I've never had problems like this, not even with the infamously terrible F8.

It looks like a cycle. Did you verify the DVD? Sometime the borking is due to the bad iso file from mirror server. I will attempt to reproduce the issue through Boxes.

[firefly1201]

I did a preupgrade, and it quit the install while cleaning up the vala package. I ran it again after using "yum reinstall vala", which worked, but the Fedora 17 kernel won't come up on grub, and there isn't a initramfs-3.3.7-1.fc17 image in /boot, just the one for fc16. It's a shame, I haven't had issues with upgrading since I started using Fedora at 11, and I really can't work out how to boot into the fc17 kernel.

[RupertPupkin]

Originally Posted by Finalzone

Did you verify the DVD?

Yes, I always verify the checksums. This DVD had the correct checksum.

I don't think it's a fluke. I had a similar issue when upgrading my 32-bit F16 machine to 32-bit F17 today (which I'm using right now, though it still needs more work to fix completely). So I've had the same problem upgrading both the 64-bit and 32-bit F16 systems I have, using DVDs that I downloaded from different sites and with verified checksums. I've seen reports of this from others as well, so I don't think I'm alone in this. Maybe fresh installs work better, but the upgrade method for F17 seems very broken.

[YeOK]

I followed the guide here: https://fedoraproject.org/wiki/Upgra...-.3E_Fedora_17.

This worked OK for the most part, my only issue is grub2 throwing a missing files error when booting, I'm guessing its related to a grub2 theme as my machine still boots fine.

[StyxD]

I forgot to mention: I also have kernel 3.3.7-1.fc17 installed, but it doesn't show up in grub menu.

It looks like it's gonna be a fresh install on the weekend for me. I've already grabbed the image.
Terrible mess.

[sesso]

Originally Posted by YeOK

I followed the guide here: https://fedoraproject.org/wiki/Upgra...-.3E_Fedora_17.

This worked OK for the most part, my only issue is grub2 throwing a missing files error when booting, I'm guessing its related to a grub2 theme as my machine still boots fine.

I think it has to do with how grub2 checks for files. It looks in one dir first and when it cant find what it needs, it goes to another.

[mmix]

grub2 throwing a missing files error when booting

4 weeks ago, i had this problem, then boot with slitaz usb, opened grub.cfg with vim on HDD, no modification(ZZ).
and reboot with F17, it shows boot menu again. weird.

BTW, fresh install with latest version is best method, IMHO.