From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: Can't figure out how to use mdadm in initrd Date: Sat, 29 Jun 2002 03:18:12 +1000 (EST) Sender: linux-raid-owner@vger.kernel.org Message-ID: <15644.39508.634914.468355@notabene.cse.unsw.edu.au> References: <1025275522.600.10.camel@temp> <15644.31109.281940.446666@notabene.cse.unsw.edu.au> <1025282183.600.18.camel@temp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: message from Ken Causey on June 28 To: Ken Causey Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On June 28, ken@ineffable.com wrote: > > > > > > set "/dev/md2" > > > [ -b "$1" ] || set "/dev/md/2" > > > mdadm --assemble --run --scan "$1" > > > > This bit of code is silly. If it chooses "/dev/md/2", then it > > won't find a match in /etc/mdadm/mdadm.conf and wont do anything > > useful. > > Why not just: > > mdadm --assemble --scan > > I understand that it may seem silly, but it makes plenty of sense when > you consider that it is generated by mkinitrd which is ended to be of > general use. Unfortunately you are seeing this out of context as this > script is told whether or not devfs is in use or not. I gather the mdadm.conf is also autogenerated to make... fair enough then. > > I don't need --run? The man page seems to imply that --run is needed if > you want to start a degraded array. --run is only needed when starting things "manually". In this context --scan implied --run. NeilBrown