All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Jungers <nicolas@jungers.net>
To: Barrett Lewis <barrett.lewis.mitsi@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Mdadm server eating drives
Date: Thu, 27 Jun 2013 19:13:08 +0200	[thread overview]
Message-ID: <51CC72A4.4040508@jungers.net> (raw)
In-Reply-To: <CAPSPcXiXo=pVfmp770==Vvj+yMU1sLMVxNf1dwCoh0At1zz3vQ@mail.gmail.com>

On 06/27/2013 02:23 AM, Barrett Lewis wrote:
> Everything is going well, I am just trying to replace the parts that
> are on the way out.
> I ran a 'repair' and it came out with 5477 under
> /sys/block/md0/md/mismatch_cnt.  Then a 'check' came out with 0.
>
> Then I went out and bought a couple WD Reds (I'm done with greens now
> that I know they lack ERC).  I replaced one of the two drives Phil
> said was not ok, which had many reallocations (I can personally see
> those) in the smart status.  I then ran another repair to be safe.  It
> came up with 0 mismatches, but in the process /dev/sda started giving
> me tons (and tons and tons, rolled over dmesg) of these "failed
> command: READ FPDMA QUEUED status: { DRDY ERR } error: { UNC }"
> errors. sda hadn't been giving me problems before but I'll come back
> to it.
>
> The second disk Phil said was "not ok" was this one which showed
> "several pending errors".
> (original smart status) http://pastie.org/8040852
> I was going to replace it with my second spare Red, but the errors
> seem to have gone away.
> (current smart status) http://pastie.org/8084278
> Or maybe I am looking in the wrong place to find the pending errors
> (looking at "197 Current_Pending_Sector").  Is the drive currently in
> need of replacement?  I'm not sure what I'm looking for.
>
> What about this one (sda), after it gave all of those errors during a
> repair?  http://pastie.org/8084292
> I get the "5 Reallocated_Sector_Ct", but where do you find pending errors?
>
> What does it mean to get all these "failed command: READ FPDMA QUEUED
> status: { DRDY ERR } error: { UNC }" errors and the smart status seems
> to be fine even after a repair?

Have you considered that your SATA may be faulty? I had consistent bad 
experiences with "cheap" SATA cables. I also use exclusively now cables 
with latches. I said "cheap" because the price is not an absolute 
criteria, quality of sourcing is more important in my experience.

Regards,
N.


>
> Thanks everyone, I'm learning a lot.
> --
> 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
>


  reply	other threads:[~2013-06-27 17:13 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 [this message]
2013-07-02  0:17                             ` Barrett Lewis
2013-07-02  1:57                               ` Stan Hoeppner
2013-07-02 15:48                                 ` Barrett Lewis
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=51CC72A4.4040508@jungers.net \
    --to=nicolas@jungers.net \
    --cc=barrett.lewis.mitsi@gmail.com \
    --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.