From 665c3ecff6cb6584ef1c0a3eb867acc5ea3944e3 Mon Sep 17 00:00:00 2001 From: Peter Hjalmarsson Date: Wed, 23 Feb 2011 07:14:04 +0100 Subject: [PATCH] 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. --- defaults/initrd.scripts | 5 ----- 1 file changed, 5 deletions(-) diff --git a/defaults/initrd.scripts b/defaults/initrd.scripts index f7f01de..dd44429 100755 --- 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 -- 2.26.2