Hide Forgot
Created attachment 491696 [details] boot.log Description of problem: Starting RPC idmapd: [ OK ] /etc/rc3.d/S25netfs: line 47: mdadm: command not found Setting up Logical Volume Management: 2 logical volume(s) in volume group "vg_dhcp70188" now active This is when booting a KVM domU of the latest Workstation variant (snap #3) which has 2 iSCSI targets acting as PVs. Version-Release number of selected component (if applicable): initscripts-9.03.22-1.el6.x86_64 anaconda version 13.21.111 How reproducible: Steps to Reproduce: 1. Configure tgtd to export 2 iSCSI targets 2. Start KVM domU install with a local disk and attach to the 2 targets 3. Select to use all space on all disks (will create LVM) 4. Select minimal package set Actual results: mdadm not found because it is not installed. Expected results: If mdadm is necessary I suppose it should have been installed automatically by anaconda. Additional info:
Created attachment 491698 [details] anaconda.ifcfg.log
Created attachment 491699 [details] anaconda.log
Created attachment 491700 [details] program.log
Created attachment 491701 [details] storage.log
Created attachment 491702 [details] syslog
Happens also with 0412.n.0 Server/Workstation.
If you didn't do any RAID partitioning setup, you didn't need mdadm to activate anything therefore it was not marked for installation. If something's changed in initscripts that make mdadm required for all installs now, that is either a bug in initscripts or comps needs to be changed to make mdadm required.
Need ae1353b8528561a41fe82314f3ee010a82e6da7a backported.
Out of curiousity - what's your mdadm.conf look like?
(In reply to comment #9) > Out of curiousity - what's your mdadm.conf look like? # cat /etc/mdadm.conf # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all
Chris - do we want anaconda writing out mdadm.conf if mdadm isn't being installed?
(In reply to comment #12) > Chris - do we want anaconda writing out mdadm.conf if mdadm isn't being > installed? We should create /etc/mdadm.conf on the basis of RAID devices being created. If there are none, the file should not be created.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0647.html