Bug 1044346

I see the same thing

From F19, I did this
# yum update
# sudo fedup --network 20 --debuglog /root/fedupdebug20.log
It downloaded everything successfully and asked me to reboot.

I did.  The loading screen shows for a few seconds before jumping to a terminal.  Everything goes south at "mount: unknown filesystem type 'vfat'" causing boot-efi.mount to fail, and subsequently 

-- Unit boot-efi.mount has begun starting up.
Dec 18 03:14:13 symonia.localdomain mount[768]: mount: unknown filesystem type 'vfat'
Dec 18 03:14:13 symonia.localdomain systemd[1]: boot-efi.mount mount process exited, code=exited status=32
Dec 18 03:14:13 symonia.localdomain systemd[1]: Failed to mount /boot/efi.
-- Subject: Unit boot-efi.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit boot-efi.mount has failed.
-- 
-- The result is failed.
Dec 18 03:14:13 symonia.localdomain systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit local-fs.target has failed.
-- 
-- The result is dependency.

Bug 1044086 describes a solution that addresses this problem.

Install fedup 0.8.x (e.g. using yum update --enablerepo=updates-testing fedup) and run that.  If you already ran fedup 0.7.x, then you might want to hardlink your files from /var/lib/fedora-ugprade to /var/tmp/system-upgrade/SOMEREPO/packages/.  I think /var/lib/fedora-upgrade/ just stored all RPMs regardless of repo in there, but /var/tmp/system-upgrade/ separates packages by REPO.  I hardlinked the contents of /var/lib/fedora-upgrade/ into each /var/tmp/system-upgrade/SOMEREPO/packages/ directory, because I don't have too much space in / to spare.

Everything seems to have gone well.  It complained that libreoffice didn't have updated packages, and grep has segfaulted on a rare case for me.

Richard Scharting Solution worked for me.

fedup --clean
yum update --enablerepo=updates-testing fedup

and everything was fine.
Thanks

(In reply to Nifty from comment #3)
> Richard Scharting Solution worked for me.
> 
> fedup --clean
> yum update --enablerepo=updates-testing fedup
> 
> and everything was fine.
> Thanks

I checked this again - it does not work, it makes something, and rebooted a fedora 20 Kernel, but no update at all.

So, this is not a working solution.

Nifty, using fedup 0.8 did fix my problem.  I didn't do fedup --clean first, though.  

- After you ran fedup again, did it download new F20 packages to /var/tmp/fedora-upgrade/REPOS/packages?
- Did it tell you it was done and you were ready to reboot (and not some other error) after running fedup?
- When you rebooted, did you still have a System Upgrade option in grub?
- When you go through it, does it show you the very minimal Fedora upgrade progress bar and Fedora logo?  If you press a key (e.g. an arrow key) does it show you a terminal with text that lets you follow what's happening? 
- Does it end up encountering an emergency and ask you to login for maintenance?
- Or does it go through all the installation and cleanup and then reboot for you?
  - If so, does it get to the login?
  - At this point, do you feel like you're still in F19?

I can confirm that this update fixed my problem, too.

Upgrading to FedUp 0.8 simply works. 
You people rock.

Thank you