From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
rc.sysinit does not run vgscan after mdadm RAID initialization.  It does scan after raidtools initialization but raidtools is not present in RHEL4.

Version-Release number of selected component (if applicable):
initscripts-7.93.11.EL-1

How reproducible:
Always

Steps to Reproduce:
1.Create a RAID device and an /etc/mdadm.conf file
2.Mark the RAID device as a physical volume and create a volume group
3.Add an entry to /etc/fstab
4.Reboot and enjoy the sulogin goodness.
  

Actual Results:  Sulogin of doom when rc.sysinit got to the fsck.

Expected Results:  The VG should have started and then the fsck would not have errored out.

Additional info:

Here is the patch:

--- ./rc.sysinit.orig   2005-02-26 12:35:50.000000000 -0500
+++ ./rc.sysinit        2005-02-27 11:15:01.975030370 -0500
@@ -542,6 +542,13 @@
 update_boot_stage RCraid
 if [ -f /etc/mdadm.conf ]; then
     /sbin/mdadm -A -s
+
+    # LVM2 initialization, take 2 ( It could be on top of mdadm RAID )
+    if [ -c /dev/mapper/control -a -x /sbin/lvm.static ]; then
+        if /sbin/lvm.static vgscan > /dev/null 2>&1 ; then
+            action $"Setting up Logical Volume Management:" /sbin/lvm.static vgscan --mknodes --ignorelockingfailure && /sbin/lvm.static vgchange -a y --ignorelockingfailure
+        fi
+    fi
 fi
  
 if [ -f /etc/raidtab ]; then