From: Roman Mamedov <rm@romanrm.net>
To: Martin Bosner <martin@bosner.de>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: assistance recovering failed raid6 array
Date: Mon, 20 Feb 2017 22:50:28 +0500 [thread overview]
Message-ID: <20170220225028.59824758@natsu> (raw)
In-Reply-To: <5cc1566c-1b4c-c663-56a1-2040b93b46d7@turmel.org>
> On 02/20/2017 12:05 PM, Martin Bosner wrote:
> > === START OF INFORMATION SECTION ===
> > Model Family: Seagate Barracuda 7200.14 (AF)
> > Device Model: ST3000DM001-1CH166
So you have the most terrible hard drive possible [1][2](they WILL ALL fail),
ran in about the most terrible RAID setup possible (only a single RAID5 would
have been worse). Now you realize why the latter was a bad idea: with such a
great number of disks, should have picked a 3x12-member RAID6 or similar. Just
let this be a lesson in component choice and risk assessment, restore from
your backups and move on.
[1] https://en.wikipedia.org/wiki/ST3000DM001
[2] https://www.quora.com/What-are-some-of-the-worst-hard-drive-designs-ever
--
With respect,
Roman
next prev parent reply other threads:[~2017-02-20 17:50 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
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 [this message]
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=20170220225028.59824758@natsu \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=martin@bosner.de \
--cc=philip@turmel.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