linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
Date: Tue, 24 Apr 2007 09:17:17 +0200	[thread overview]
Message-ID: <c384c5ea0704240017m6963deet58b28b67377e8f91@mail.gmail.com> (raw)
In-Reply-To: <c384c5ea0704240004r176372e1nb384c06e558dd1f@mail.gmail.com>

On 4/24/07, Leon Woestenberg <leon.woestenberg@gmail.com> wrote:
> Hello,
>
> On 4/23/07, David Greaves <david@dgreaves.com> wrote:
> > There is some odd stuff in there:
> >
> [root@localhost ~]# mdadm -v --assemble --scan --config=/tmp/mdadm.conf --force
> [...]
> mdadm: no uptodate device for slot 1 of /dev/md0
> mdadm: no uptodate device for slot 2 of /dev/md0
> [...]
>
So, the problem I am facing is that the slot number (as seen with
--examine) is invalid on two and therefore they won't be recognized as
valid drives for the array.

Is there any way to override the slot number? I could not find
anything in mdadm or mdadm.conf to override them.

-- 
Leon

  reply	other threads:[~2007-04-24  7:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 17:17 Multiple disk failure, but slot numbers are corrupt and preventing assembly Leon Woestenberg
2007-04-23 17:55 ` David Greaves
2007-04-24  7:04   ` Leon Woestenberg
2007-04-24  7:17     ` Leon Woestenberg [this message]
2007-04-24  8:32       ` David Greaves
2007-04-24 12:44         ` Leon Woestenberg
2007-04-24 13:06           ` David Greaves
2007-04-25 22:31           ` Bill Davidsen
2007-04-26 19:46             ` David Greaves
2007-04-26 23:36               ` Leon Woestenberg
2007-04-27 19:01               ` Bill Davidsen
2007-04-26  6:47           ` Neil Brown

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=c384c5ea0704240017m6963deet58b28b67377e8f91@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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).