top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Fedup upgrade from F17

+1 vote

I have a f17 x64 system that I want to upgrade to the latest Fedora. I found information indicating that I should use fedup. I have read further and gotten conflicting reports and suggestions. The project documentation says to use this method but user reports say it doesn't work. Could I get some clarification on this subject?

Can I actually use fedup to go to f19 from f17? Do I have to do an upgrade through f18? Is there a good "how to", step-by-step, on the subject for this scenario?

posted Aug 25, 2013 by Seema Siddique

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

+1 vote

I actually just upgraded my F17 to F18 mythtv box and it worked fine. One thing to note, I keep a couple of local repositories shared via NFS. For some reason, fedup assumes these packages will be available during the upgrade and does not copy them to the local disk. To make matters worse, when it cant find 800 ish of the upgrade packages, it doesnt quit, it upgrades anyway leaving an unusable system.
For me the trick was:

fedup --network 18 --disablerepo "local*" 

After the upgrade I just did a yum update and yum-distro-sync and that caught up the packages from my local repository.

answer Aug 25, 2013 by Deepankar Dubey
+1 vote

I've done this twice. My laptop went perfectly. My desktop hung at about 60%, requiring me to use the reset button and clean up from a CLI. Just remember that you're more likely to hear from people who's upgrades don't go well than from those who's do.

BTW, one of the reasons I skipped F18 is that there were so many complaints at about failed upgrades. There seem to be very few there with F19, suggesting that there aren't as many bugs as there used to be.

answer Aug 25, 2013 by Majula Joshi
Similar Questions
+3 votes

I upgraded to fedora 20 from fedora 19 using fedup. Everything went well except for some weird issues with Thunderbird. The latter is now giving me a pile of weird permission errors and disk space errors. There is 250GB free space, so I know that is not the problem. Obviously this has something to do with the permissions on the thunderbird folder, but I do not have the knowledge to rectify the problem.

Please suggest how to proceed?

0 votes

I don't quite understand this error that occurred during Fedora upgrade.

I did: fedup-cli --network 19, the result is:

Upgrade test failed with the following problems:

insufficient disk space
 need 150M free on / (1.2G free)
fedup ERROR: Upgrade test failed.

It needs 150 M but it states it has 1.2G available. So, is 150M > 1.2G ????

+1 vote

I tried to upgrade a system to fc18 using fedup. The root is encrypted. I first updated fc17 to the latest packages and rebooted, then run fedup using a locally mounted ISO image and "--network 18" which ran to uneventful conclusion. On reboot the password was supplied and the system ran for about five hours (was reading a book and checking every chapter or so), and after the next reboot the system crashed during boot.

On a reboot the list of boot options appeared, but none continued, unable to find a filesystem, and not ever asking for a LUKS password. A boot from recovery drive showed no usable data on the internal drive, it was not marked as LUKS (as far as I can tell), not password was requested, no filesystem was found, an
attempt to mount the partition manually resulted in no password prompt and no filesystem identified.

With no working way to upgrade and about 17 more to do, if I have to back up and hand install a new OS, it sure won't be Fedora, the upgrade process only works about 50% of the time on unencrypted systems, and there seems no working path on encrypted. The old "update" worked so reliably, can't the developers admit fedup was a bad idea and and return to a sane update procedure?

+5 votes

I installed Fedora 19 on my laptop, and it worked beautifully with the already installed Windows 8. When I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.

I disabled secure boot in the firmware.

I do not even know which version of grub was booting the UEFI system before; it just worked.

Can anyone suggest:

  1. What grub would the Fedora 19 installer have provided to boot it and Windows 8? (grub2, grub-efi,...)
  2. Can anyone point to any documentation on how to fix this?