top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

fedup-cli failed to upgrade from fedora18 to fedora19

0 votes
335 views

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 ????

posted Jun 4, 2013 by anonymous

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

1 Answer

0 votes

maybe it actually need 1.35G free to perform the update??

it probably needs to download lots of rpms, can you put /var/cache/yum onto a bigger partition??

answer Jun 4, 2013 by anonymous
I can't. Disk layout is fixed (but if all fails, I can try to mount /var/cache/yum on some USB disk). I'm doing massive cleanup now on my / (root).

This still does not explain this error message. It should tell me what is the actual disk requirement and what is available to fedup so I can compare and fix it. Now I read I have 1.2G but it failed because of not having 150M of free space.
You might have but did you
"df -h /"
Similar Questions
0 votes

Running the update from 17 to 18 failed after going 67% through, please see https://bugzilla.redhat.com/show_bug.cgi?id=972358 .

What can I do now so I'm not stuck with a mixture of 17 and 18?

+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?

+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?

+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?

...