The following was filed automatically by anaconda: anaconda 11.5.0.57-1.fc11 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/formats/luks.py", line 133, in teardown raise LUKSError("format has not been created") File "/usr/lib/anaconda/storage/formats/luks.py", line 162, in destroy self.teardown() File "/usr/lib/anaconda/storage/deviceaction.py", line 323, in execute self.origFormat.destroy() File "/usr/lib/anaconda/storage/devicetree.py", line 671, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 238, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems anaconda.id.storage.doIt() LUKSError: format has not been created
Created attachment 346047 [details] Attached traceback automatically from anaconda.
I _think_ on this one I refused the installer's request for a password to mount the previous LUKS (on RAID-1) volumes, as I didn't want the content on them and was trying to do a non-LUKS install as the LUKS re-install wasn't working. If that makes no sense, I could be thinking of the wrong attempt; sorry I didn't keep better notes. This was the RC2 LiveCD.
I wonder if this is another way of recreating https://fedoraproject.org/wiki/Common_F11_bugs#502310?
It sure sounds similar enough that a fix for one might fix the other.
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
Created attachment 355195 [details] Attached traceback automatically from anaconda.
Comment #6 was automatically created from anaconda. More info: The reason for the problem is most probably that the disk on which Fedora 11 shall be installed has already a LUKS partition which I didn't open (from an earlier Fedora 11 installation). Indeed I instructed anaconda through "custom disk setup" to scratch it and rebuild a new LUKS partition on top of it. Will now zero the partition and try again.
This should be fixed in anaconda-12.18-1. We had some issues that popped up when users chose not to provide a passphrase for preexisting LUKS devices.