FedUp makes F17 no longer boot after botched "upgrade" to F19

[Joe Zeff]

On 11/02/2013 10:22 PM, Fernando Cassia wrote:
> No, I wanted to know first if this was a known scenario, before I went
> to the command line and started messing up things further ;).

You may have run afoul of this: 
https://bugzilla.redhat.com/show_bug.cgi?id=980543  Yes, it refers to 
18-19, but it hit me on an upgrade from 17-19.  Also, the maintainers 
are claiming that it's caused by a process that's just taking longer 
than expected to complete.  My suggestion is that you try using 
distro-sync once you get to a CLI.