Hide Forgot
Description of problem: After executing fedup --network 20, it executes with no erros, asking for a reboot to continue After rebooting,a new grub option is presented, to upgrade. After choosing that option, it starts booting and preparing for upgrade (i assume), but fails with a prompt to emergency mode Version-Release number of selected component (if applicable): fedup-0.7.3-4.fc19.noarch How reproducible: Every time Steps to Reproduce: 1. Execute fedup to prepare to upgrade 2. reboot 3. choose upgrade grup option Actual results: emergency mode prompt Expected results: start upgrade process to Fedora 20 Additional info: [root@nightraider ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/fedora_nightraider-root 50G 9.3G 38G 20% / devtmpfs 9.8G 0 9.8G 0% /dev tmpfs 9.8G 840K 9.8G 1% /dev/shm tmpfs 9.8G 1012K 9.8G 1% /run tmpfs 9.8G 0 9.8G 0% /sys/fs/cgroup tmpfs 9.8G 260K 9.8G 1% /tmp /dev/sda2 477M 137M 311M 31% /boot /dev/mapper/fedora_nightraider-home 161G 14G 139G 10% /home /dev/sda1 200M 9.4M 191M 5% /boot/efi uname -a Linux nightraider.hal.min-saude.pt 3.11.10-200.fc19.x86_64 #1 SMP Mon Dec 2 20:28:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
I also experience this issue on one machine. Several others have worked well. I tried rebooting into the upgrade several times with different kernel options, mainly selinux=0 noselinux audit=0, to see if it was selinux related. The issue was the same. I have difficulty capturing logs, but the upgrade seemed to complain a bit about "binfmt" errors of some kind. The machine later rebooted into fedora 19 without problems.
I encountered the same issue but was able to resolve it by using fedup 0.8 instead, following the instructions here: https://fedoraproject.org/wiki/Common_F20_bugs#fedup-07-fail
I can confirm fedup 0.8 worked for me as well!
I'm trying now with fedup 0.8 . I'll post any results as soon i can verify the upgrade.
I can confirm fedup 0.8 works perfectly ! I'll close this bug whit the solution to upgrade to fedup 0.8 using the solution provided by Eric Logan. https://fedoraproject.org/wiki/Common_F20_bugs#fedup-07-fail
Can i close the bug ? Or some else will ? Cheers
I believe I'm hitting this bug. I've got 0.8.0-3.fc20 installed. I'm attempting to upgrade from f19 to f20, and when I reboot into 20, dracut boots into emergency mode. The failing kernel is 3.13.6-200.fc20.x86_64. 3.13.6-100.fc19.x86_64 works, however. Note that this machine is using LVM encryption.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.