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.

Description of problem:

I have a machine which has pre-existing (RHEL5) volumes on it.  I have valuable data on them which I need to access in my RHEL6 install.

Not only are the partitions no longer detected (they were, apparently, before BZ 591030 - a DVD from 20100523 detected them fine, 20100603 blew up in the installer), but there is no way to add back the LVMs which are there on the disk using the graphical installer.

The net result is installing RHEL6 is going to wipe my system.  This is unacceptable.  I had an install of RHEL6 on the machine before, which isn't detected anymore (it exists, I can still boot into it).  It appears as if the fix to the broken upgrade functionality was to simply not make it detect the volumes to upgrade!  Hardly a good solution.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Use 20100607 RHEL6 x86_64 iso to install
2.  Abort install in panic realizing it is going to wipe my entire drive
3.
  
Actual results:


Expected results:


Additional info:

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Can you grab the updates image from bug 602369 comment #2, boot with updates=<location where you put that image>, and see if anaconda then detects your partitions?

Well, it detected all of my partitions if I do a "Fresh Install", but the Update option only sees my RHEL6 partition.  I assume this is the correct behavior.

BTW, to get the updates image to work on my USB key, I had to decompress it and recreate it as an ext2 filesystem.

Yes, that's correct.  anaconda will only offer to upgrade partitions of the same product.

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