The following was filed automatically by anaconda:
anaconda 13.21.48 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 406, in lvactivate
raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
File "/usr/lib/anaconda/storage/devices.py", line 2332, in setup
File "/usr/lib/anaconda/storage/devicetree.py", line 1529, in handleVgLvs
File "/usr/lib/anaconda/storage/devicetree.py", line 1964, in _setupLvs
File "/usr/lib/anaconda/storage/devicetree.py", line 2045, in populate
File "/usr/lib/anaconda/storage/__init__.py", line 379, in reset
File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1423, in setScreen
File "/usr/lib/anaconda/gui.py", line 1336, in nextClicked
LVMError: lvactivate failed for LVM2_LV_NAME=x64_fc: 11:43:35,618 ERROR : One or more specified logical volume(s) not found.
Created attachment 418140 [details]
Attached traceback automatically from anaconda.
We probably shouldn't be including "LVM2_LV_NAME=" in the name of the logical volume we're trying to activate.
We've a patch fixing this granting devel ack. We should really fix this for 6.0, this will happen whenever there is a pre-existing VG which has some freespace at the beginning of one of its pvs.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The installer will backtrace (crash) when it encounters a physical volume which contains freespace (space not used by a logical volume) at the beginning of the physicial volume. To work around this create a logical volume using this space before starting the installation.
This is fixed in anaconda-13.21.51-1, moving to modified.
Verified on build RHEL6.0-20100701.0 with anaconda-13.21.56-1.el6. Closing the bug.
*** Bug 610510 has been marked as a duplicate of this bug. ***
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.