Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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
lvm.lvactivate(self.vg.name, self._name)
File "/usr/lib/anaconda/storage/devicetree.py", line 1529, in handleVgLvs
lv_device.setup()
File "/usr/lib/anaconda/storage/devicetree.py", line 1964, in _setupLvs
if self.handleVgLvs(device):
File "/usr/lib/anaconda/storage/devicetree.py", line 2045, in populate
if self._setupLvs():
File "/usr/lib/anaconda/storage/__init__.py", line 379, in reset
self.devicetree.populate()
File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize
storage.reset()
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1423, in setScreen
self.anaconda.dispatch.gotoNext()
File "/usr/lib/anaconda/gui.py", line 1336, in nextClicked
self.setScreen ()
LVMError: lvactivate failed for LVM2_LV_NAME=x64_fc: 11:43:35,618 ERROR : One or more specified logical volume(s) not found.
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.
New Contents:
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.
*** Bug 610510 has been marked as a duplicate of this bug. ***
Comment 14releng-rhel@redhat.com
2010-11-10 19:46:24 UTC
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.
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 lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/anaconda/storage/devicetree.py", line 1529, in handleVgLvs lv_device.setup() File "/usr/lib/anaconda/storage/devicetree.py", line 1964, in _setupLvs if self.handleVgLvs(device): File "/usr/lib/anaconda/storage/devicetree.py", line 2045, in populate if self._setupLvs(): File "/usr/lib/anaconda/storage/__init__.py", line 379, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize storage.reset() File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1423, in setScreen self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/gui.py", line 1336, in nextClicked self.setScreen () LVMError: lvactivate failed for LVM2_LV_NAME=x64_fc: 11:43:35,618 ERROR : One or more specified logical volume(s) not found.