aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurence Perkins <lperkins@zagmail.gonzaga.edu>2019-03-29 10:48:05 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2019-03-29 14:26:03 -0700
commit7ea94b035c91e0edee183522cdeb51810e043b72 (patch)
tree4e9a611015e9f48aa7661bd6ae352c348f194727
parentgenkernel: Use isTrue for $BOOTRW (diff)
downloadgenkernel-7ea94b035c91e0edee183522cdeb51810e043b72.tar.gz
genkernel-7ea94b035c91e0edee183522cdeb51810e043b72.tar.bz2
genkernel-7ea94b035c91e0edee183522cdeb51810e043b72.zip
Intel RST/Matrix RAID support
Intel Matrix RAID uses a nested container structure requiring that the array first be assembled, and then the actual storage volumes be activated. Signed-Off-By: Laurence Perkins <lperkins@zagmail.gonzaga.edu> (cherry picked from commit 952ecaffb742fef7422e313af5fa0a4426625e14) Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
-rw-r--r--defaults/initrd.scripts3
1 files changed, 3 insertions, 0 deletions
diff --git a/defaults/initrd.scripts b/defaults/initrd.scripts
index c57f016..5d3a220 100644
--- a/defaults/initrd.scripts
+++ b/defaults/initrd.scripts
@@ -1074,6 +1074,9 @@ startVolumes() {
if [ -x '/sbin/mdadm' ]
then
/sbin/mdadm --assemble --scan
+ #Intel Matrix RAID (and possibly others) have a container layer above the actual volumes,
+ #So we have to look for volumes that haven't been activated.
+ mdadm -IRs
else
bad_msg "mdadm not found: skipping mdadm raid assembly!"
fi