From: Wols Lists <antlists@youngman.org.uk>
To: Amit Biswas <abiswas@nyu.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovering RAID Volumes from 6 Disks
Date: Wed, 20 Jul 2016 15:31:09 +0100 [thread overview]
Message-ID: <578F8B2D.5070003@youngman.org.uk> (raw)
In-Reply-To: <CADsVfeyz=KiAqSBe11jjBT-yOWpZp_eyP_BctkjvWC5UPNLXuQ@mail.gmail.com>
Ummmmm ...
b,e and f are Barracudas ... I know my 3TB Barracudas are vulnerable to
the timeout problem. It looks like the 1TB ones probably are as well ...
While you're waiting for someone else to chime in, read the following
... not the best reading ... about why your Barracudas are probably a
bad choice :-(
http://marc.info/?l=linux-raid&m=139050322510249&w=2
http://marc.info/?l=linux-raid&m=135863964624202&w=2
http://marc.info/?l=linux-raid&m=135811522817345&w=1
http://marc.info/?l=linux-raid&m=133761065622164&w=2
http://marc.info/?l=linux-raid&m=132477199207506
http://marc.info/?l=linux-raid&m=133665797115876&w=2
http://marc.info/?l=linux-raid&m=142487508806844&w=3
http://marc.info/?l=linux-raid&m=144535576302583&w=2
Have you got a spare Constellation lying around? If not, can you get a
proper raid drive - WD Red or Seagate NAS? Do a ddrescue to copy sda to
the replacement drive if you can. You don't want to use that to recover
the array if you can help it, but you might not have much choice, and at
least you'll have it to hand.
And do NOT do this until the experts chime in and help, but hopefully
it's just a case of making sure all your arrays are stopped, running the
following script
for x in /sys/block/sd[a-z] ; do
echo 180 > $x/device/timeout
done
echo 4096 > /sys/block/md0/md/stripe_cache_size
on the barracudas and re-assembling the array(s). At which point,
backing up and replacing the barracudas should be extremely high on the
agenda! It's probably a good idea to go Raid-6 and get 2 or 3TB drives.
Cheers,
Wol
On 19/07/16 23:34, Amit Biswas wrote:
> Here are the smart reports for all six drives. drive sda was not co-operating...
>
> /dev/sda
>
> smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.2.0-27-generic] (local build)
> Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Vendor: /2:0:0:0
> Product:
> User Capacity: 600,332,565,813,390,450 bytes [600 PB]
> Logical block size: 774843950 bytes
>>> Terminate command early due to bad response to IEC mode page
>
> === START OF READ SMART DATA SECTION ===
>
> Error Counter logging not supported
>
> Device does not support Self Test logging
>
next prev parent reply other threads:[~2016-07-20 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 16:29 Recovering RAID Volumes from 6 Disks Amit Biswas
2016-07-19 19:57 ` Wols Lists
2016-07-19 22:34 ` Amit Biswas
2016-07-20 14:31 ` Wols Lists [this message]
2016-07-20 14:53 ` Wols Lists
2016-07-20 15:07 ` Roman Mamedov
2016-07-20 15:36 ` Wols Lists
2016-07-20 16:10 ` Wols Lists
2016-07-22 13:56 ` Phil Turmel
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=578F8B2D.5070003@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=abiswas@nyu.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 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.