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.
Bug 696110 - /etc/rc3.d/S25netfs: line 47: mdadm: command not found
Summary: /etc/rc3.d/S25netfs: line 47: mdadm: command not found
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 670159
TreeView+ depends on / blocked
 
Reported: 2011-04-13 09:55 UTC by Alexander Todorov
Modified: 2011-05-19 13:52 UTC (History)
3 users (show)

Fixed In Version: initscripts-9.03.23-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 696907 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:52:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
boot.log (3.03 KB, application/octet-stream)
2011-04-13 09:55 UTC, Alexander Todorov 		no flags Details
anaconda.ifcfg.log (2.94 KB, application/octet-stream)
2011-04-13 09:55 UTC, Alexander Todorov 		no flags Details
anaconda.log (26.84 KB, application/octet-stream)
2011-04-13 09:55 UTC, Alexander Todorov 		no flags Details
program.log (83.87 KB, application/octet-stream)
2011-04-13 09:56 UTC, Alexander Todorov 		no flags Details
storage.log (257.85 KB, application/octet-stream)
2011-04-13 09:56 UTC, Alexander Todorov 		no flags Details
syslog (50.09 KB, application/octet-stream)
2011-04-13 09:56 UTC, Alexander Todorov 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0647 0 normal SHIPPED_LIVE initscripts bug fix and enhancement update 2011-05-19 09:37:27 UTC

Description Alexander Todorov 2011-04-13 09:55:15 UTC 
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:
Comment 1 Alexander Todorov 2011-04-13 09:55:50 UTC 
Created attachment 491698 [details]
anaconda.ifcfg.log
Comment 2 Alexander Todorov 2011-04-13 09:55:59 UTC 
Created attachment 491699 [details]
anaconda.log
Comment 3 Alexander Todorov 2011-04-13 09:56:08 UTC 
Created attachment 491700 [details]
program.log
Comment 4 Alexander Todorov 2011-04-13 09:56:16 UTC 
Created attachment 491701 [details]
storage.log
Comment 5 Alexander Todorov 2011-04-13 09:56:23 UTC 
Created attachment 491702 [details]
syslog
Comment 6 Alexander Todorov 2011-04-13 10:33:47 UTC 
Happens also with 0412.n.0 Server/Workstation.
Comment 7 Chris Lumens 2011-04-13 13:17:10 UTC 
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.
Comment 8 Bill Nottingham 2011-04-13 13:39:10 UTC 
Need ae1353b8528561a41fe82314f3ee010a82e6da7a backported.
Comment 9 Bill Nottingham 2011-04-13 13:40:12 UTC 
Out of curiousity - what's your mdadm.conf look like?
Comment 11 Alexander Todorov 2011-04-14 12:03:42 UTC 
(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
Comment 12 Bill Nottingham 2011-04-14 14:14:54 UTC 
Chris - do we want anaconda writing out mdadm.conf if mdadm isn't being installed?
Comment 14 Chris Lumens 2011-04-15 02:32:14 UTC 
(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.
Comment 18 errata-xmlrpc 2011-05-19 13:52:08 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.