Red Hat Bugzilla – Bug 732861
FormatSetupError: invalid device specification
Last modified: 2011-09-15 16:42:15 EDT
abrt version: 2.0.5
reason: FormatSetupError: invalid device specification
time: Tue Aug 23 18:45:45 2011
:The following was filed automatically by anaconda:
:anaconda 16.14.6 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 334, in setup
: raise FormatSetupError("invalid device specification")
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 171, in setup
: DeviceFormat.setup(self, *args, **kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 844, in setupParents
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 701, in _preSetup
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 712, in setup
: if not self._preSetup(orig=orig):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2042, in turnOnSwap
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1305, in turnOnSwap
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 151, in turnOnFilesystems
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 348, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 235, in go_forward
: File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1198, in nextClicked
:FormatSetupError: invalid device specification
This one was lousy, happened during the formatting of partitions, formatted /boot/ then blew up, left me with a non functioning install of fedora. Looks to me like it doesn't like luks, but I am no expert.
Can you please attach /tmp/anaconda-tb-* to this bug report as well? I don't know why libreport didn't do that for us, but it's pretty annoying.
Well the third time through the install seems to be the charm as the issue did not occur again. Sorry I can't get you better debug info, I too thought it was all attached here.
In the absence of critical information I am going on a hunch and closing this as a dupe of bug 737916.
*** This bug has been marked as a duplicate of bug 737916 ***