From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: Neil Brown <neilb@suse.de>
Cc: linux-ide@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.15-mm3 sata_mv / raid 5 array start failure on boot
Date: Wed, 11 Jan 2006 10:08:29 +0000 [thread overview]
Message-ID: <43C4D91D.9060008@projecthugo.co.uk> (raw)
In-Reply-To: <17347.3650.415581.4115@cse.unsw.edu.au>
Neil Brown wrote:
>On Tuesday January 3, kernel-lists@projecthugo.co.uk wrote:
>
>
>>I re-created the array - and took a dump of the raid config
>>
>>ARRAY /dev/md6 level=raid5 num-devices=6 spares=1
>>UUID=f92fa512:1fe54278:d3ba820f:cecb842a
>>
>>
>
>You'll need a 'DEVICES' line in the mdadm.conf for it to work.
>
>NeilBrown
>
>
thanks for this tip.
Matt
prev parent reply other threads:[~2006-01-11 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 19:30 2.6.15-mm3 sata_mv / raid 5 array start failure on boot Matt Darcy
2006-01-03 15:37 ` Matt Darcy
2006-01-10 1:30 ` Neil Brown
2006-01-11 10:08 ` Matt Darcy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C4D91D.9060008@projecthugo.co.uk \
--to=kernel-lists@projecthugo.co.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).