The following was filed automatically by anaconda: anaconda 11.5.0.28 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/formats/fs.py", line 428, in mount raise FSError("no mountpoint given") File "/usr/lib/anaconda/storage/formats/fs.py", line 656, in setup return self.mount(**kwargs) File "/usr/lib/anaconda/storage/devices.py", line 511, in setup parent.format.setup() File "/usr/lib/anaconda/storage/devices.py", line 1026, in create self.setup() File "/usr/lib/anaconda/storage/deviceaction.py", line 205, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 618, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 181, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 115, in turnOnFilesystems anaconda.id.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() FSError: no mountpoint given
Created attachment 335003 [details] Attached traceback automatically from anaconda.
Since we don't currently allow unpartitioned disks to contain formatting other than a disklabel we need to ignore things like filesystems detected on them. That's what is happening here -- your preexisting btrfs on the disk is recognized, but we don't know to destroy the formatting when writing the disklabel.
*** Bug 490641 has been marked as a duplicate of this bug. ***
mmm, but if the disk only had a filesyste on it and no partitions there should have been a question asking if to ignore or to reinitialize the disk with a partition. Maybe this happens when both filesystem metadata and partition metadata are detected on the disk (its happened to me more than once).
*** Bug 496535 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 513235 has been marked as a duplicate of this bug. ***
*** Bug 531880 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Support for preexisting whole-disk formatting was added to anaconda-13.10-1, which will be in Fedora 13. Reformatting and setting a mountpoint are not supported, but the formatting will be recognized. In the case of lvm physical volumes and software (md) raid member devices, the devices can be used in new or existing configurations.
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
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.