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.
Created attachment 527664[details]
kickstart config
Description of problem:
In one configuration two raid volumes one RAID0 15GB, second RAID10 on the same 4 disks. In auto installation with configuration:
one partition /boot and two logic volume swap and "/" on RAID0. Anaconda hangs during installation.
Version-Release number of selected component (if applicable):
How reproducible: Sporadically
Steps to Reproduce:
1. Create in OROM two RAID volumes (RAID0 of size 15GB and RAID10) on the same 4 disks;
2. Prepare kickstart for auto installation with partitions:
part /boot --fstype ext2 --size=768 --ondisk=md126
part pv.011520 --size=1 --grow --ondisk=md126
volgroup lvmvolgroup0 --pesize=32768 pv.011520
logvol swap --fstype swap --size=768 --name=lvm_swap --vgname=lvmvolgroup0
logvol / --fstype ext3 --size=10752 --name=lvm_root --vgname=lvmvolgroup0
3. Start auto installation
Actual results:
System hangs on "Creating device /dev/mapper/lvmvolgroup0 - lvm_root"
Expected results:
Additional info:
If change order of partitions problem not occur.
Please collect /tmp/program.log from the installation environment after it stalls at "Creating device /dev/mapper/lvmvolgroup0 - lvm_root". Attach /tmp/program.log to this bug report as a plain text file.
(In reply to comment #0)
> Additional info:
> If change order of partitions problem not occur.
What do you mean? What partition order works and how are you defining it?
I am almost sure that for reverse configuration:
part pv.011520 --size=1 --grow --ondisk=md126
volgroup lvmvolgroup0 --pesize=32768 pv.011520
logvol / --fstype ext3 --size=10752 --name=lvm_root --vgname=lvmvolgroup0
logvol swap --fstype swap --size=768 --name=lvm_swap --vgname=lvmvolgroup0
part /boot --fstype ext2 --size=768 --ondisk=md126
installation ended without problems?
Comment 10RHEL Program Management
2011-10-25 05:48:20 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
We've debugged one problem with very similar symptoms recently. Please, try this update for the anaconda installer, just add:
updates=http://dlehman.fedorapeople.org/updates/updates-783841.0.img
..to the kernel command line before starting the installation.
This update modifies anaconda udev rules so it uses a different locking scheme while calling "lvm pvs" command to obtain existing PV properties (which is a workaround for now, but a proper fix is on its way for 6.3 already).
Please, let us know if it helps. Thanks.
Created attachment 527664 [details] kickstart config Description of problem: In one configuration two raid volumes one RAID0 15GB, second RAID10 on the same 4 disks. In auto installation with configuration: one partition /boot and two logic volume swap and "/" on RAID0. Anaconda hangs during installation. Version-Release number of selected component (if applicable): How reproducible: Sporadically Steps to Reproduce: 1. Create in OROM two RAID volumes (RAID0 of size 15GB and RAID10) on the same 4 disks; 2. Prepare kickstart for auto installation with partitions: part /boot --fstype ext2 --size=768 --ondisk=md126 part pv.011520 --size=1 --grow --ondisk=md126 volgroup lvmvolgroup0 --pesize=32768 pv.011520 logvol swap --fstype swap --size=768 --name=lvm_swap --vgname=lvmvolgroup0 logvol / --fstype ext3 --size=10752 --name=lvm_root --vgname=lvmvolgroup0 3. Start auto installation Actual results: System hangs on "Creating device /dev/mapper/lvmvolgroup0 - lvm_root" Expected results: Additional info: If change order of partitions problem not occur.