linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: phyros <dlopuch@mit.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help on Recovering a Corrupted raid5 Partition
Date: Sat, 9 Jun 2007 07:47:26 +1000	[thread overview]
Message-ID: <18025.52846.187895.423902@notabene.brown> (raw)
In-Reply-To: message from phyros on Friday June 8


mdadm --examine
only makes sense on a component of an md/raid array, not on the whole
array itself.  So the "mdadm --examine" errors you were getting were
user errors :-)

Everything looks fine except for the "total devices" "working devices"
"active devices" totals, and they aren't used much.  You can probably
fix them with:

  mdadm --stop /dev/md1
  mdadm --assemble /dev/md1 --update=summaries /dev/sd[abcd]3

but before you do that:
  Why do you say the raid5 partition is corrupted?  What are the
  symptoms that caused you to start looking into this?

NeilBrown

  reply	other threads:[~2007-06-08 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 19:32 Help on Recovering a Corrupted raid5 Partition phyros
2007-06-08 21:47 ` Neil Brown [this message]
2007-06-09 13:11 ` Bill Davidsen

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=18025.52846.187895.423902@notabene.brown \
    --to=neilb@suse.de \
    --cc=dlopuch@mit.edu \
    --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).