linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Heflin <rogerheflin@gmail.com>
To: Mirko <mirko76@arcor.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Need help with my raid5
Date: Fri, 22 Mar 2013 10:37:47 -0500	[thread overview]
Message-ID: <CAAMCDeeympGaLMCfQKt32bJ-ZWtf08RCTv0=LZNP_r-kxn6fiQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20130322T134448-923@post.gmane.org>

On Fri, Mar 22, 2013 at 7:53 AM, Mirko <mirko76@arcor.de> wrote:
>> According to the above you removed device 3 not device 7....device 3
>> is missing...device 7 is still there and is a spare.
>
> Thats right.
>
>> Put what you though was 7 back
> This device no longer exists.

What do you mean no longer exists?

If so, then you are likely restoring from backups as device 7 failed
and device 3 was otherwise was removed and is now no longer viable.
You may be able to do add a -f on the mdadm and force it
online...typically it will force a previously declared missing/spare
device to be re-evaluated and reused if it is good enough or failed
for some reasons.

>
>> ...note that properly determining which
>> device is which is pretty difficult unless you have a commercial grade
>> wired enclosure from a tier 1 vendor that is actually labeled and
>> wired correctly (don't always count on that).
>
> I thought, every device has its fixed device number in the raid:
>
> mdadm -E /dev/sd[a-f]1 | grep Role
>    Device Role : Active device 1
>    Device Role : Active device 5
>    Device Role : spare
>    Device Role : Active device 0
>    Device Role : Active device 4
>    Device Role : Active device 2
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-03-22 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  7:57 Need help with my raid5 Mirko
2013-03-22 12:06 ` Roger Heflin
2013-03-22 12:13   ` Brad Campbell
2013-03-22 12:53   ` Mirko
2013-03-22 15:21     ` Mirko
2013-03-22 15:28     ` Mirko
2013-03-22 15:37     ` Roger Heflin [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='CAAMCDeeympGaLMCfQKt32bJ-ZWtf08RCTv0=LZNP_r-kxn6fiQ@mail.gmail.com' \
    --to=rogerheflin@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mirko76@arcor.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).