Created attachment 438334 [details] Err during filesystem check after upgrading bootloader Description of problem: An ERR occurred during filesystem check after upgrading form F13 to F14 while creating a new bootloader configuration Version-Release number of selected component (if applicable): anaconda 14.15 F14-alpha-rc3 How reproducible: 100% Steps to Reproduce: 1.Perform a default installation of the previous release ( Fedora 13) 2.Boot the current release (Fedora 14) using any available means (boot.iso) 3.Select appropriate language and keyboard, then select Upgrade an existing installation 4.Select Create new boot loader configuration to update 5.After upgrade finished, reboot the system Actual results: An ERR occurred during filesystem check Detail info is in the attachment Expected results: 1. The system should be upgraded to new version without error 2. The system can boot into new version fedora without error 3. The opened terminal, file browser, or other system applications should display and work correctly Additional info:
Please attach all the /var/log/anaconda* files to this bug report.
Created attachment 438585 [details] Err during filesystem check after upgrading bootloader
Mark as Beta blocker according to: The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation of the previous stable Fedora release, either via preupgrade or by booting to the installer manually
There should be more logs than just anaconda.log and anaconda-yum.log [bcl@lister tmp]$ ls /var/log/anaconda.* /var/log/anaconda.log /var/log/anaconda.syslog /var/log/anaconda.program.log /var/log/anaconda.xlog /var/log/anaconda.storage.log /var/log/anaconda.yum.log
Discussed at today's blocker review meeting. This seems a clear blocker on the criterion cited. Accepted as Beta blocker. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hurry / Ming Tao, can you attach the extra logs Brian asked for?
Created attachment 443214 [details] all log files in /tmp after updating bootloader I couldn't get log files after rebooting because of the filesystem error. I got the log files in /tmp before rebooting.
What are the plans for addressing and assessing this bug? We'd love to have more information before the next blocker meeting this Friday.
I'll try to reproduce this.
I did a test using an updated F13 KVM virt. I upgraded using the full Alpha DVD and the Alpha netboot.iso and saw no problems with filesystem errors. Problems like that are more likely to be an issue with the local system's hardware than with Anaconda.