The following was filed automatically by anaconda: anaconda 12.46 exception report Traceback (most recent call first): File "/usr/lib/anaconda/isys.py", line 173, in umount rc = _isys.umount(what) File "/usr/lib/anaconda/storage/formats/fs.py", line 600, in unmount rc = isys.umount(self._mountpoint, removeDir = False) File "/usr/lib/anaconda/storage/formats/fs.py", line 790, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/anaconda/storage/__init__.py", line 1855, in umountFilesystems device.format.teardown() File "/usr/lib/anaconda/storage/__init__.py", line 1052, in umountFilesystems self.fsset.umountFilesystems(ignoreErrors=ignoreErrors, swapoff=swapoff) File "/usr/lib/anaconda/yuminstall.py", line 834, in run self.anaconda.id.storage.umountFilesystems() File "/usr/lib/anaconda/yuminstall.py", line 1585, in doInstall rc = self.ayum.run(self.instLog, cb, anaconda.intf, anaconda.id) File "/usr/lib/anaconda/backend.py", line 291, in doInstall return anaconda.backend.doInstall(anaconda) File "/usr/lib/anaconda/dispatch.py", line 200, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 123, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1195, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1216, in handleRenderCallback self.currentWindow.renderCallback() SystemError: (2, None)
Created attachment 379096 [details] Attached traceback automatically from anaconda.
This is the anaconda dump when an FC12 update (from FC11) fails with the error message "error transferring install image". This also occurred on a workstation upgrade. Both machines have ASUS CD drives. I tried using the "linux allowcddma" boot option to no avail. I cannot upgrade to FC12 due to this fatal error.
Are you doing something on tty2 that is keeping /mnt/sysimage busy, and therefore unmountable?
Nothing at all. Just watching Anaconda do its thing, until it launches the error message dialog. I've successfully upgraded FC11 to FC12 on another (i386) server, by the way, without this problem. I have encountered this problem on an i386 workstation and the x64 server reported here, both upgrading from FC11. And yes, I'm using the x64 distro for the x64 server upgrade.
Sam, You seem to be doing an installation from CD's, correct ? What is happening is that anaconda needs to transfer the image it is running from to the HD, so CD's can be swapped, it chooses /boot to store the install.img, and then fails because it runs out of diskspace. After this it for some reason I've not quite figured out yet it throws this error while trying to clean up, which is weird, esp so as errno 2 means ENOENT. But the real issue is the failing of the image transfer. This is caused by a bug where anaconda chooses the filesystem with the least amount of freespace to store the image (instead of the largest). Here is an updates.img fixing this: http://people.fedoraproject.org/~jwrdegoede/updates-548592.img Add: updates=http://people.fedoraproject.org/~jwrdegoede/updates-548592.img At the end of the syslinux cmdline when starting anaconda to use this, this should fix this issue. Please let us know if this fixes things. Regards, Hans
Thanks, Hans. Yes, I was doing a CD install. Unfortunately (for testing purposes) I went ahead and used preupgrade to upgrade these systems (which worked fine). So I don't have them available to test your update, but I have one more server to upgrade from FC 10 to 12, which I'll try from CD first, in case it reproduces the problem (doubtful) and, if so, I'll try the new image. Thanks!
Putting this back into needinfo until we get results from that server.
*** Bug 542610 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 573467 has been marked as a duplicate of this bug. ***
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.