Bug 626201

Created attachment 440236 [details]
lsinitrd on initramfs with a default workstation packageset

Created attachment 440237 [details]
dracut -v output on minimal system

Created attachment 440239 [details]
dracut -v output on normal system

-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-crypt.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-log-userspace.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-registry.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-replicator.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-repl-log-ringbuffer.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-repl-slink-blockdev.ko
-lib/modules/2.6.32-63.el6.x86_64/kernel/drivers/md/dm-zero.ko

These are the only relevant differences, I can see.

diff --git a/modules.d/90dm/installkernel b/modules.d/90dm/installkernel
index af51a22..f5a8ad9 100755
--- a/modules.d/90dm/installkernel
+++ b/modules.d/90dm/installkernel
@@ -1,9 +1,5 @@
 #!/bin/bash
 
-for i in \
-    dm-snapshot dm-delay dm-mirror dm-mod dm-queue-length \
-    dm-region-hash dm-round-robin dm-service-time dm-snapshot \
-    ; do
-    modinfo -k $kernel $i >/dev/null 2>&1 && instmods $i
-done
+instmods =drivers/md
+
 
Proposed fix

Talked with Harald about this issue. Proposing as a blocker for RHEL-6 GA as this would affect every minimal install using raid devices, leaving customers unable to boot. Fix is very easy: Simply hardwire inclusion the missing modules during initramfs generation.

Thanks & regards, Phil

I've tried to reproduce this again, so that I could test the patch. And I've failed to reproduce. I don't understand how this has happened I've checked and double checked I could reproduce this before filing the bug ?

It does make sense though as I see no modules in the list of missing modules which are necessary for booting from dmraid sets. Sorry about this I suggest closing this as works for me.

Hmm, works for me, too. The only thing, which would not work is booting a isw raid without mdadm installed. This would require the following patch:


diff --git a/modules.d/90dmraid/parse-dm.sh b/modules.d/90dmraid/parse-dm.sh
index f031569..d34df10 100644
--- a/modules.d/90dmraid/parse-dm.sh
+++ b/modules.d/90dmraid/parse-dm.sh
@@ -3,3 +3,10 @@ if getarg rd_NO_DM || getarg nodmraid; then
     info "rd_NO_DM: removing DM RAID activation"
     udevproperty rd_NO_DM=1
 fi
+
+# noiswmd nodmraid for anaconda / rc.sysinit compatibility
+# note nodmraid really means nobiosraid, so we don't want MDIMSM then either
+if getarg rd_NO_MDIMSM || getarg noiswmd; then
+    info "rd_NO_MDIMSM: no MD RAID for imsm/isw raids"
+    udevproperty rd_NO_MDIMSM=1
+fi

(In reply to comment #9)
> Hmm, works for me, too. The only thing, which would not work is booting a isw
> raid without mdadm installed. This would require the following patch:
> 
> 
> diff --git a/modules.d/90dmraid/parse-dm.sh b/modules.d/90dmraid/parse-dm.sh
> index f031569..d34df10 100644
> --- a/modules.d/90dmraid/parse-dm.sh
> +++ b/modules.d/90dmraid/parse-dm.sh
> @@ -3,3 +3,10 @@ if getarg rd_NO_DM || getarg nodmraid; then
>      info "rd_NO_DM: removing DM RAID activation"
>      udevproperty rd_NO_DM=1
>  fi
> +
> +# noiswmd nodmraid for anaconda / rc.sysinit compatibility
> +# note nodmraid really means nobiosraid, so we don't want MDIMSM then either
> +if getarg rd_NO_MDIMSM || getarg noiswmd; then
> +    info "rd_NO_MDIMSM: no MD RAID for imsm/isw raids"
> +    udevproperty rd_NO_MDIMSM=1
> +fi

Ah, thats it! My original testing was on an isw machine using noiswmd, my reproducer used a
nvidia raid machine as the isw one was doing production work.

noiswmd is broken in multiple ways in 6.0 anyways so better move this to 6.1

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
If you want to boot an IMSM/ISW raid with dmraid and without mdadm, you still have to install the mdadm oackage in a kickstart minimal install and have to specify "noiswmd" or "rd_NO_MDIMSM" on the kernel command line.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If you want to boot an IMSM/ISW raid with dmraid and without mdadm, you still have to install the mdadm oackage in a kickstart minimal install and have to specify "noiswmd" or "rd_NO_MDIMSM" on the kernel command line.+If you want to boot an IMSM/ISW raid with dmraid and without mdadm, you still have to install the mdadm package in a kickstart minimal install and have to specify "noiswmd" or "rd_NO_MDIMSM" on the kernel command line.

As the original issue didn't seem to be the case the minor issue that Harald detected in comment #9 and Hans confirmed in comment #10 we'll move this to 6.1 but flag is a requiring a release note.

Removed blocker request and snap 13 target

Thanks & regards, Phil

Closed defered as we're going to fix this in 6.1, see clone bug #626389.

Keeping this tagged for 6.0 to allow release notes to pick up the text.

Thanks & regards, Phil

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If you want to boot an IMSM/ISW raid with dmraid and without mdadm, you still have to install the mdadm package in a kickstart minimal install and have to specify "noiswmd" or "rd_NO_MDIMSM" on the kernel command line.+When booting an IMSM/ISW RAID with dmraid but without mdadm, the mdadm package still needs to be installed on the system in a kickstart minimal install with the "noiswmd" or "rd_NO_MDIMSM" parameters specified.