All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Martin Bosner <martin@bosner.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: assistance recovering failed raid6 array
Date: Mon, 20 Feb 2017 13:11:03 -0500	[thread overview]
Message-ID: <676bd1fa-4b97-2c6a-05b8-bd23290fb9a6@turmel.org> (raw)
In-Reply-To: <231629B1-0888-4B3D-BD81-F641937AC045@bosner.de>

Hi Martin,

On 02/20/2017 12:48 PM, Martin Bosner wrote:
> Hi Phil,
> 
>> { Note: convention on kernel.org is reply-to-all, bottom post or 
>> interleave, and trim unneeded material. }
> Sorry, hope this one is better.
> 
> 
>> for x in /dev/sd[a-z] /dev/sda[a-j] ; do mdadm -E ${x}1 ; done
> 
> See below for full output.

Not good.

>> Eewwww!  You have desktop drives.  Which means your array has
>> blown up due to timeout mismatch.  You have some reading to do.[1]

Of the 36 original disks, you have 34.  You have one incomplete
rebuild, meaning it is still technically a spare. One of the still
active 34 is also showing pending relocations, meaning that disk will
not be able to supply all sectors to complete any recovery.
{ /dev/sdah, serial # S1F0FPYR }

If you have any access to the two "dead" drives, there might be
a slight chance. Since they were likely kicked out due to timeout
mismatch, not a complete failure, this could be possible.

Otherwise, you are utterly screwed.  Sorry.

> I will be using so called “NAS” or “enterprise disks in the next 
> cluster …  especially these seagate disks were a bad decision.

Yes.

Phil


  reply	other threads:[~2017-02-20 18:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20  1:49 assistance recovering failed raid6 array Martin Bosner
2017-02-20 15:39 ` Phil Turmel
     [not found]   ` <E18A7C79-09E0-4361-9F89-68AE1E6FCBF6@bosner.de>
2017-02-20 17:36     ` Phil Turmel
2017-02-20 17:48       ` Martin Bosner
2017-02-20 18:11         ` Phil Turmel [this message]
2017-02-20 18:27           ` Martin Bosner
2017-02-20 19:01             ` Wols Lists
2017-02-20 19:11               ` Martin Bosner
2017-02-20 19:16             ` Phil Turmel
2017-02-20 19:31               ` Martin Bosner
2017-02-20 21:30                 ` Phil Turmel
2017-02-20 20:45               ` Wols Lists
2017-02-20 21:21                 ` Phil Turmel
2017-02-21  2:03                   ` Brad Campbell
2017-02-20 17:50       ` Roman Mamedov
2017-02-20 18:13         ` Martin Bosner

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=676bd1fa-4b97-2c6a-05b8-bd23290fb9a6@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin@bosner.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 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.