what a coincidence, just an hour ago i started with mdadm....  on one
page i saw it desribed that you should keep an /etc/dadm.conf file,
which you can maintain using 
	mdadm --detail --scan >> /etc/dadm.conf 
and with the right option in /etc/fstab it would be mounted.

I didn't do that yet, so i was surprised to see that one seems
to have to run
	mdadm --create .....
each time before /dev/md0 is in the correct shape so you can mount
it again.   However, i'm in the steep part of the learning curve
myself, i think..../hope...

peter

On Mon, 21 Mar 2005, Maarten Ballintijn wrote:

> Hi,
> 
> In the case of single level arrays, just marking the partitions
> type auto-start (fd) should be sufficient I think?
> 
> It seems that the assemble option of mdadm should be able to
> replace raidstart in the rest of the cases?
> 
> I've been using mdadm for all normal array management and recovery
> functions. It does its job very well.
> 
> Cheers,
> 
> Maarten.
> 
> On Mon, 2005-03-21 at 16:44, Daniel Widyono wrote:
> > Greetings,
> > 	Anyone using software raid and managing it via mdadm rather than
> > raidtools?  It seems that there's no equivalent to raidstart in rc.sysinit as
> > supplied with RHEL.  It's annoying that they provide mdadm however, without
> > full support of bootup.  Perhaps it's my inexperience, but can anyone confirm
> > this to be true?  If so, can someone point me to a "best practice" rc.sysinit
> > patch which does what RH's does with raidtools, but using mdadm instead?
> > 	I'll hack into it and see if I can provide such a patch, but I just
> > can't believe that we're the only ones who ran into this.  I'll check
> > bugzilla later just in case something showed up there.
> > 
> > Thanks,
> > Dan W.
>