Daniel B. Thurman wrote:
Yup, that's right. I have automatic updates set and somehow, I got a F10->F11 Upgrade popup dialog box. I thought to myself, why not. F10 was missing session-save, so I proceeded, not that I had any choice in the matter (the upgrade dialog box did not have "Cancel"... So, after many hours of "upgrading", it seemed search my local configuration, started downloading and setting up an upgrade configuration list, and at the end of that process, left a dialog box with a button saying: "Reboot", so I pressed the Reboot button. What is odd is on rebooting, the screen information was telling me that I was booting up as F10... When I logged in as a normal user, everything seemed to be running as F10... I am sure glad that I did not lose the OS in any case and it did come up working. What's up with that?
I rebooted the system, and noted there was a grub entry for starting the anaconda upgrade. I noted that X came up, searched for storage devices, found one and anaconda noted that the filesystem was encrypted, and then it prompted me for my passphrase. I entered the passphrase, checked the "global ..." checkbox, then it proceeded to search for the installation list, then finding it, popped up the 'Checking dependencies in packages selected for installation...", and starting showing the progress-bar moving slowly until it reached 1/3 of the way through then from that point "zipped" to progress-bar of 100%, after which several minutes passed and the "clock icon" stopped moving when I moved the mouse. I checked for disk activity for 10 minutes - nothing. The whole screen frozed up. No mouse movement, nothing. At that point, since there was no activity, I rebooted and tried the same thing over - same frozen result. Giving up, I tried to see if I could still boot to my F10 kernel via grub, and I was still able to boot into my F10 OS - all is well - the upgrade to F11 failed. Question: How can I redo the pre-upgrade process since there is already one installed previously so that I can rebuild the "installation list" to see if I can start the upgrade process once again. Is it possible to delete the pre-upgrade "area", so that I can run preupgrade again as it won't let me do so since one already exist? Seems like there is perhaps something wrong with the initial pre-upgrade process. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
