Description of problem: Version-Release number of selected component (if applicable): How reproducible: Happens always. Steps to Reproduce: 1.run sudo fedup --network 20 2.reboot when finished how instruction said 3.choose upgrade kernel Actual results: boot stops at "Mounted /boot" and doesn't go further. Expected results: booting into fedora 20 upgrade Additional info:
check which version of fedup you have---the latest is 0.8, and I had similar problems with v.0.7 so if you have the old one, you need to 'yum update fedup'. The upgraded fedup 0.8 might get you into another error, the GPG check problem, in which case you need to read https://fedoraproject.org/wiki/Common_F20_bugs#fedup-18-gpg
I'm already using version 0.8. I already solved all GPG problems, so it runs through without any GPG error.
Encountered this same symptom (boot stops at "Mounted /boot" and doesn't go further) last night. My system: Linux 3.12.5-200.fc19.i686.PAE #1 SMP Tue Dec 17 22:35:54 UTC 2013 i686 i686 i386 GNU/Linux Also have LVM + luks encryption: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 298.1G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 297.6G 0 part └─luks-07d509ee-3885-4934-a3fe-86d9b0910409 253:0 0 297.6G 0 crypt ├─fedora-root 253:1 0 50G 0 lvm │ └─luks-85eac55a-cdae-4da1-9309-844917316a71 253:4 0 50G 0 crypt / ├─fedora-swap 253:2 0 3.1G 0 lvm │ └─luks-ba545f8b-4831-4d72-8314-5db8bf1dc1d0 253:3 0 3.1G 0 crypt [SWAP] └─fedora-home 253:5 0 244.5G 0 lvm └─luks-d570f5f2-e10b-4027-8bd4-4719a0530b43 253:6 0 244.5G 0 crypt /home 11:0 1 1024M 0 rom
I also use a LVM + luks encryption. Linux 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 119,2G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 118,8G 0 part └─luks-bd257c33-8807-49d6-b3d5-7c0018fedd71 253:0 0 118,8G 0 crypt ├─fedora_jktsa660160-root 253:1 0 31,2G 0 lvm │ └─luks-06629bcd-6f71-4a7b-85b8-d0fa835be368 253:3 0 31,2G 0 crypt / ├─fedora_jktsa660160-swap 253:2 0 3,8G 0 lvm │ └─luks-1421a980-c05d-45c7-ad5d-5511fa3f0412 253:4 0 3,8G 0 crypt [SWAP] └─fedora_jktsa660160-home 253:5 0 83,7G 0 lvm └─luks-794c7deb-bae7-4dac-862e-60e5e948b96e 253:6 0 83,7G 0 crypt /home sr0 11:0 1 1024M 0 rom
I was able to work around the issue by going to a VT and running systemctl list-jobs, then cancelling the "stuck" jobs (asking for a password prompt). I have not experienced any issues with the upgraded system.
*** This bug has been marked as a duplicate of bug 1045864 ***