Hide Forgot
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.
Created attachment 527665 [details] /tmp/anaconda.log
Created attachment 527666 [details] /tmp/storage.log
Created attachment 527667 [details] /tmp/syslog
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.
Created attachment 527730 [details] /tmp/program.log
(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?
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.
It still occur. On Snapshot5 also. Not allays, but appear. Michal
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.
It helps. Problem do not occurs. Michal
(In reply to comment #13) > It helps. Problem do not occurs. Thanks for testing, I'm reassigning this to anaconda team then.
*** This bug has been marked as a duplicate of bug 783841 ***