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.

Created attachment 436054 [details]
anaconda.log

To reproduce:
-do a default autopart install on an Intel BIOS RAID mirror
-start the installer in rescue mode, and let it try to automount the existing
 install

Result:
-fails to find the existing install

Further info:
-logs attached

Created attachment 436055 [details]
program.log

Created attachment 436056 [details]
storage.log

Created attachment 436057 [details]
syslog

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

What does /etc/fstab look like?

Created attachment 436089 [details]
/etc/fstab

15:13:49,515 DEBUG   : PV md127p2 has no vg_name
15:13:49,515 DEBUG   : PV md127p2 has no vg_uuid

So, according to udev/lvm, there is no VG metadata in the PV, which of course means we do not ever assemble the LVs and find the installation.

The root cause for this lies in lvm, see bug 620745. I'm testing a workaround patch now.

A workaround patch has been posted to a-d-l. I've verified that this patch fixes the finding of a default Intel Firmware RAID install in rescue mode with:
http://download.devel.redhat.com/rel-eng/RHEL6.0-20100730.5/6/Workstation/i386/os
+ an updates.img with the patch.

The lvm team has a fix for this, marking this bug as a duplicate of the lvm bug 620745.

*** This bug has been marked as a duplicate of bug 620745 ***