All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: "Garðar Arnarsson" <gardar@giraffi.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
Date: Sun, 08 Sep 2013 09:30:33 -0400	[thread overview]
Message-ID: <522C7BF9.2020107@turmel.org> (raw)
In-Reply-To: <CAH-e9vJGPOWm2YqGk54CRtGVW1pYcxbU0xS9HaU74fR_q+Ecug@mail.gmail.com>

On 09/07/2013 07:49 PM, Garðar Arnarsson wrote:
> I seem to have been able to resolve this.
> 
> I tried force assembling the array with all the drives except for sda1
> (the problematic device before) that way the array got assembled with
> 12 drives and one spare, enough so I could recover the array.
> 
> Still would want to know what might have caused these problems for the
> first place, but I'm glad it seems to be working ok for now.

In my years of helping people on this list, the single most common cause
of spurious dropouts is mismatched error recovery timeouts.  Caused by
use of desktop hard drives in raid arrays.  You should search the list
archives for various combinations of "scterc" "device/timeout" "tler"
and "ure".

Then report the following on the list (inline, not attached):

for x in /sys/block/*/device/timeout ; do echo $x $(< $x) ; done

smartctl -x /dev/sd[a-q]


HTH,

Phil

--
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-09-08 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 22:56 raid6 array assembled from 11 drives and 2 spares - not enough to start the array Garðar Arnarsson
2013-09-07 23:49 ` Garðar Arnarsson
2013-09-08  0:05   ` Roger Heflin
2013-09-08  0:36     ` Garðar Arnarsson
2013-09-08  1:25       ` Roger Heflin
2013-09-08 13:30   ` 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=522C7BF9.2020107@turmel.org \
    --to=philip@turmel.org \
    --cc=gardar@giraffi.net \
    --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 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.