linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Barrett Lewis <barrett.lewis.mitsi@gmail.com>
To: stan@hardwarefreak.com
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Mdadm server eating drives
Date: Tue, 2 Jul 2013 10:48:59 -0500	[thread overview]
Message-ID: <CAPSPcXjOPben0xGqcUKwyZn4pX403uFbp5f57f=LEV371ZuDjw@mail.gmail.com> (raw)
In-Reply-To: <51D233A5.504@hardwarefreak.com>

After sending the last email I went out and bought 2 new WD reds, and
a new motherboard.  I came back and in those 2 hours all but 1 of my
drives failed to the point of being unable to read the superblock so
it really seems like my array is ended

On Mon, Jul 1, 2013 at 8:57 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> I noticed one drive was going up and down and determined that
>> the drive had actual physical damage to the power connecter and
>> was losing and regaining power through vibration.
>
> This intermittent contact could have damaged the PSU.  You've continued
> to have drive and lockup problems since replacing this drive with bad
> connector.

I hadn't thought of it until you said so but I bet you are right about
the iffy connector.  It certainly seemed as if I never had an issue
with the array for 8 months, and then suddenly everything got unstable
at once, and since then I've lost atleast 6 hard drives.

>
> The pink elephant in the room is thermal failure due to insufficient
> airflow.  The symptoms you describe sound like drives overheating.  What
> chassis is this?  Make/model please.  If you've installed individual
> drive hot swap cages, etc, it would be helpful if you snapped a photo or
> two and made those available.
>
>

It is also possible that there were cooling issues.  The case is an
NZXT H2.  It has some fans blowing directly on all the hard drives,
but there were a few times I have to admit I took the fans off to work
on things and forgot to put them back on for a few days, coming back
to find them very hot to the touch.  I would have mentioned that
earlier, but a data recovery place told me that it was unlikely that
would be a culprit (after they had my money).

I don't have any drives in special cages but here's a pic anyway.  The
two fanboxes that sit in front of them are taken off.
https://docs.google.com/file/d/0B1w3WvCHlYUWRVhWOVd0Qmt1TUk/edit?usp=sharing


Maybe thats all academic at this point.  I guess i'll have to rebuild
my server from scratch since all my disks seem destroyed and I can't
trust the mobo, cpu, or psu.  Atleast I can memtest the ram.  The psu
wasn't dirt cheap, Thermaltake TR2 500w @ $58.  Should I buy all new
everything?  If so, while I'm at can you suggest a set of consumer
level hardware ideal running a personal mdadm server.  Powered but not
overpowered, reliable not bleeding edge.  If I need 6-8 sata ports,
should I do onboard or get a controller?

I still have one backup allthough I'm very nervous now since it's on a
3 disk RAID0, just asking to implode (created in an emergency).

  reply	other threads:[~2013-07-02 15:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 13:47 Mdadm server eating drives Barrett Lewis
2013-06-12 13:57 ` David Brown
2013-06-12 14:44 ` Phil Turmel
2013-06-12 15:41 ` Adam Goryachev
     [not found]   ` <CAPSPcXihHrAi2TB9Fuxb1qOGMc_WzwGoXAA7nHdwe2knkO0LkQ@mail.gmail.com>
     [not found]     ` <CAPSPcXib4YZ9Ah-jLvL_kPwpKHLxaGT0rNaDL4XQcFm=RtjcAQ@mail.gmail.com>
2013-06-14  0:19       ` Barrett Lewis
2013-06-14  2:08         ` Phil Turmel
     [not found]           ` <CAPSPcXgMxOF-C2Szu_nf4ZLDC8p+yJFOtvLPu7xy1DTW9VAHjg@mail.gmail.com>
2013-06-14 21:18             ` Barrett Lewis
2013-06-14 21:20               ` Barrett Lewis
2013-06-14 21:25                 ` Phil Turmel
2013-06-14 21:30                   ` Phil Turmel
2013-06-17 21:37                     ` Barrett Lewis
2013-06-18  4:13                       ` Mikael Abrahamsson
2013-06-27  0:23                         ` Barrett Lewis
2013-06-27 17:13                           ` Nicolas Jungers
2013-07-02  0:17                             ` Barrett Lewis
2013-07-02  1:57                               ` Stan Hoeppner
2013-07-02 15:48                                 ` Barrett Lewis [this message]
2013-07-02 19:44                                   ` Stan Hoeppner
2013-07-02 19:54                                     ` Stan Hoeppner
2013-07-02 20:07                                     ` Jon Nelson
2013-07-02 20:23                                       ` Stan Hoeppner
2013-07-02 20:58                                     ` Barrett Lewis
2013-07-03  1:50                                       ` Stan Hoeppner
2013-07-03  5:26                                         ` Barrett Lewis
2013-07-03 14:03                                           ` Jon Nelson
2013-07-03 14:36                                             ` Phil Turmel
2013-07-03 17:32                                             ` Stan Hoeppner
2013-07-03 19:47                                               ` Barrett Lewis
2013-07-03 20:38                                                 ` Jon Nelson
2013-07-04  2:21                                                 ` Stan Hoeppner
2013-07-03 17:05                                           ` Stan Hoeppner
2013-07-02 21:49                               ` Phil Turmel
2013-06-14 21:24               ` Phil Turmel
2013-07-29 22:25           ` Roy Sigurd Karlsbakk

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='CAPSPcXjOPben0xGqcUKwyZn4pX403uFbp5f57f=LEV371ZuDjw@mail.gmail.com' \
    --to=barrett.lewis.mitsi@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.com \
    /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;
as well as URLs for NNTP newsgroup(s).