Red Hat Bugzilla – Bug 117805
rc.sysinit does not start RAID devices if they are not explicitly listed in fstab
Last modified: 2014-03-16 22:43:01 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040130
Description of problem:
Have a system with RAID-0, RAID-1 and RAID-5 drives (using kernel MD
for software RAID). The RAID-1 drives (/dev/md0 on my system) start
at boot because it is explicitly mentioned in fstab.
The other md? devices have LVM logical volumes built on top of them.
Thus the RAID devices (/dev/md) are not explicitly listed in
fstab; the logical volumes on top of them are in fstab.
Thus the lines (460-464) in rc.sysinit:
> INFSTAB=`LC_ALL=C grep -c "^$i" /etc/fstab`
> if [ $INFSTAB -eq 0 ] ; then
cause the unmentioned (but needed) RAID devices to not be started.
Commenting those lines out brings up my storage.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create RAID drive.
2. Make a volume group and logical volume on to of it.
3. Set the logical voulume to automount in fstab.
Actual Results: Logical volume is not mounted. RAID unit beneath was
Expected Results: The RAID unit should have been started, and the
logcal volume mounted.
I first saw this in RH9, when I first started using LVM.
Can confirm this behaviour for RH9 at least. I added the following
right below the NOAUTO-if an it works for me:
LVMRAID=`LC_ALL=C grep -c "$i" /etc/lvmconf/
if [ $LVMRAID -gt 0 ]; then
echo -n "LVM is using MD: "
This is fixed in the current devel initscripts for FC4.