All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Maarten <maarten@ultratux.net>, linux-raid@vger.kernel.org
Subject: Re: re-assembling arrays after severe controller hardware issues...
Date: Fri, 25 Oct 2013 19:06:16 -0400	[thread overview]
Message-ID: <526AF968.7090306@turmel.org> (raw)
In-Reply-To: <526AE059.8020006@ultratux.net>

Hi Maarten,

Good report.

On 10/25/2013 05:19 PM, Maarten wrote:
> 
> Hi
> 
> I suffered a coupleof (subsequent) multi-disk raid failures caused by
> hardware (not disk) issues. I now am reasonably confident the cause of
> the hardware issues has been remedied. Looking at one of the arrays I
> see differing event counters, but all close together. If I attempt
> --assemble that doesn't work, mdadm insists on only taking two of the
> six raid6 members into account.. Am I correct that an added --force will
> rectify that, or is a different course of action necessary ?

You are correct.  --force is the correct action.  You may have very
slight corruption from the data still in OS caches, but there's no help
for that.  Also use --verbose, and save the output for us in case
there's further difficulties.

> (Yes, there was a sixth member too, but I suffered a crash (kernel
> kicked a controller with 5 disks on it) during the re-adding of that one
> disk, so I have therefore deemed it unsafe to use for --assemble, so
> that one is marked and put away safely)

Yes, leave that one out.  I also recommend getting any critical backups
from the reassembled array before you attempt to add the missing drive.

HTH,

Phil


      reply	other threads:[~2013-10-25 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 21:19 re-assembling arrays after severe controller hardware issues Maarten
2013-10-25 23:06 ` Phil Turmel [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=526AF968.7090306@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=maarten@ultratux.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.