Hi
On Sun, Dec 29, 2013 at 9:51 AM, Brian Hanks wrote:
In response I removed kmod-VirtualBox, akmod-VirtualBox, and VirtualBox. Then I did a fedup --clean and reattempted fedup --network 20. This went well until the reboot. Following the reboot I select the Fedup option, but nothing really happened. I ended up back in my Fedora 19 system while running the new Fedora 20 kernel. As an update on the other machine where I was having problems with the net install. I checked for any meaningful logs but found that none exist. The /var/log directory hasn't even been created. So, then I tried to run a grub2-mkconfig, grub2-install, dracut series to potentially fix the problem. The file sizes did change a bit, but the end result was the same.
Which version of fedup? Make sure you have the latest
https://fedoraproject.org/wiki/FedUp#Why_does_my_upgrade_to_Fedora_20_fail_.28immediately_reboot_to_my_old_Fedora.29.3F
https://fedoraproject.org/wiki/FedUp#Why_does_my_upgrade_to_Fedora_20_fail_.28immediately_reboot_to_my_old_Fedora.29.3F
Rahul
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
