Do not mess with MDADMs auto-detect

Only reason for this logic is to limit what entries in /proc/partitions
mdadm scans for arrays.
However this seems to break raids in containers (example Intel fakeraids)
as those containers are never scanned for arrays.
(On my system it activates /dev/md/imsm0, but never /dev/md/Gentoo_0 which
is the real RAID with the removed logic)
If someone has something dead-slow they do not want scanned for raids,
it is better if they specify their own mdadm.conf.
If someone finds an example of something that mdadm scans for arrays that
is not supposed to be scanned, we may handle that then.

diff --git a/defaults/initrd.scripts b/defaults/initrd.scripts
index f7f01dedddddbd5bbc8fa94641b248cc1b95ad5e..dd444296ab794b4e483b935a636f0c81d30d4c5c 100755 (executable)
--- a/defaults/initrd.scripts
+++ b/defaults/initrd.scripts
@@ -621,11 +621,6 @@ startVolumes() {
        
        if [ "${USE_MDADM}" = '1' ]
        then
-               if [ ! -e '/etc/mdadm.conf' ]
-               then
-                       echo "DEVICE /dev/sd[a-z]* /dev/hd[a-z]*" >/etc/mdadm.conf
-                       /sbin/mdadm --examine --scan >>/etc/mdadm.conf
-               fi
                /sbin/mdadm --assemble --scan
        fi