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.
DescriptionAlexander Todorov
2011-03-15 15:39:15 UTC
Created attachment 485525[details]
anaconda.log
Description of problem:
When / is on RAID0 array and booting into rescue mode anaconda tells me that it can't find any Linux file systems.
Version-Release number of selected component (if applicable):
anaconda-13.21.104-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create a KVM domU with 2 disks: vda and vdb
2. Create the following layout:
vda1 - 1024, ext4 - /boot
vda2 - rest of space, Linux raid
vdb1 - 1024, swap
vdb2 - rest of space, Linux raid
md0 - RAID0, ext4, vda2, vdb2 - /
3. Complete the install and confirm that / is on RAID0 array
4. Boot into rescue mode.
Actual results:
/ can't be found
Expected results:
/ is found and mounted under /mnt/sysimage.
Additional info:
Comment 1Alexander Todorov
2011-03-15 15:39:42 UTC
Created attachment 485525 [details] anaconda.log Description of problem: When / is on RAID0 array and booting into rescue mode anaconda tells me that it can't find any Linux file systems. Version-Release number of selected component (if applicable): anaconda-13.21.104-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a KVM domU with 2 disks: vda and vdb 2. Create the following layout: vda1 - 1024, ext4 - /boot vda2 - rest of space, Linux raid vdb1 - 1024, swap vdb2 - rest of space, Linux raid md0 - RAID0, ext4, vda2, vdb2 - / 3. Complete the install and confirm that / is on RAID0 array 4. Boot into rescue mode. Actual results: / can't be found Expected results: / is found and mounted under /mnt/sysimage. Additional info: