top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Fedup fails on upgrade of F18 system on encrypted partition

+1 vote
192 views

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?

posted Jul 15, 2013 by anonymous

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

1 Answer

+1 vote
 
Best answer

Did you try using yum? I have always been successful with it (you may need to remove obsolete packages or ones that generate complaints, temporarily). I have never been successful with fedup (including F18->F19 in the only instance I tried in the 18 to 19 case -- everything went through w/o complaint but the system did not come up).

Look at the following: really three commands:

https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_18_-.3E_Fedora_19

answer Jul 15, 2013 by anonymous
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?

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

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

0 votes

I tried to encrypt the disk (option in Fedora) and failed because /boot can not be in encrypted partition. I have only one HDD and it appears that the encrypted option is for the entire HDD. Is there any place in the new Anaconda where encryption can be done for selected partitions? Where? Do I have other options (beyond getting rid of encryption, which may be just too esoteric for me in the first place)?

+1 vote

I have a running Fedora 21 system. I would like to make a backup of it to a USB drive, a clone that can be booted. I know how to do all the "normal" stuff (partition, LVM, mkfs, rsync, and GRUB), but I'd like the USB drive to be encrypted, and I don't know how to set that up manually (I haven't messed with encrypted filesystems under Linux before).

The system I'm backing is also headless, so no GUI tools. Any Pointers, tips, suggestions?

...