Bug#569359: mdadm -Ds insists on /dev/md/X device presence

[Martin Michlmayr]

* Neil Brown <neilb at suse.de> [2010-06-08 08:57]:
> > When I run:
> >     mdadm --examine --scan --config=partitions
> > I get:
> >     ARRAY /dev/md/0 metadata=1.2 UUID=afb5fddc:1e5a383b:246bf8de:7f52a209 name=debian:0
> > i.e. the /dev/md/0 form.  (Also note that that the UUID in the map
> > file is different to that reported by --examine --scan; not sure
> > why.)
> 
> You use --examine like this?  You know the array you have just created.

Right.  The installer doesn't run this.  It was just an example.  But
when mdadm is installed in the chroot, it doesn't know about the RAID
devices and runs this command to find out what they are and to create
a config.

> It would be safer to use
>    mdadm -As
> to ensure all arrays are assembled, then
>    mdadm -Ds
> to create mdadm.conf
> 
> ... but why do you even want to create mdadm.conf ???

I'll let madduck answer this.

In any case, it seems the short-time fix for this bug is to make sure
/dev/md/X are created in Debian installer.

-- 
Martin Michlmayr
http://www.cyrius.com/