Hide Forgot
Description of problem: I tried to use preupgrade to install Fedora 16 Beta. However, when anaconda started, it refused to proceed with installation complaining that /dev/sda1 (root filesystem with ext4 on Intel SSD) was not cleanly unmounted. I tried to boot into Fedora 15 and shutdown via different ways including Gnome menu and shutdown -h now, but that has not helped. How reproducible: Always. Steps to Reproduce: 1. Install and run preupgrade on Fedora 15 to prepare for Fedora 16 Beta installation. 2. Shutdown or reboot and choose the upgrate in the grub menu. Actual results: Anaconda installer refused to run complaining about unclean mount. Expected results: The upgrade should run normally.
Please collect the file /tmp/program.log from the shell on tty2 while the error message is shown on the installer's graphical screen. To get to the shell, press <ctrl>+<alt>+<f2>. From there you can use scp to transfer the file to another computer and attach it to this report. Thanks. You also might want to try running 'e2fsck -p /dev/sda1' while you're on tty2. That should fix any problems in the filesystem, including it being marked as dirty. If that works and then the upgrade works as well you don't need to attach the program.log file here.
Created attachment 530382 [details] progran.log This is the requested /tmp/program.log. Running e2fsck -p /dev/sda1 does not help as it reports that the filesystem is clean.
Can you attach the other logs, please? /tmp/anaconda.log /tmp/storage.log If you are doing a live install: /var/log/messages If not: /tmp/syslog Thanks.
Created attachment 530390 [details] anaconda.log
Created attachment 530391 [details] program.log
Created attachment 530392 [details] storage.log
Created attachment 530393 [details] syslog
Apparently my /dev/sda1 has errors that are visible if I mount it with -f. I suppose anaconda discovers that. So the issue is usability one. That is, the error message should report about that and not about unclean umount.
I submitted a bug[0] that might be a duplicate, would appreciate if someone could confirm/deny. P.S. I do not seem to have any "invisible" errors on my drive, I have mounted with -f, fsck'ed with -v, and anything else I could think of and have not encountered any errors. [0] https://bugzilla.redhat.com/show_bug.cgi?id=752720
This seems like a duplicate of the old bug #557989, at least the description matches what I remember from last year when I tried to debug #557989. A few minutes ago I added an untested patch to bug #557989; maybe you could try this and report back if it fixes your issue.
I just figured I should point out here that the old bug #557989 is CLOSED WONTFIX, because it was filed against Fedora 12 which has reached EOL. The issue was never fixed. The patch I attached to bug #557989 was originally developed for the anaconda version of the Fedora 14 release and tested once, using a method similar to the method I described in comment 14 of bug #557989. I have updated the patch for the current anaconda git HEAD version as of 2011-11-29. The anaconda hacking method from bug #557989 cannot be used any longer for the installer of Fedora 16, because the stage2 installer is no longer packed in a separate image, but tacked piggyback onto the initramfs image. I have tried, but failed so far, to find a way to separate the parts of the Fedora 16 installer initramfs image. So, if anyone wants to use my patch, the only option seem to be to build a new installer initramfs image from scratch (which I did not try so far).
For F18 we are no longer using preupgrade, which also means anaconda is no longer involved in the upgrade process at all. Therefore, this bug report should no longer be relevant. If you experience upgrade problems with F18, please file them either against the fedup component, or the specific package that is causing upgrade problems. Thanks.