linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid/device failure
Date: Mon, 11 Feb 2013 00:55:40 -0700	[thread overview]
Message-ID: <201302110055.40801.thomas@fjellstrom.ca> (raw)
In-Reply-To: <511863F7.2090108@fnarfbargle.com>

On February 10, 2013, Brad Campbell wrote:
> On 11/02/13 09:27, Thomas Fjellstrom wrote:
> > sd 0:0:7:0: [sdh]  Add. Sense: Information unit iuCRC error detected
> 
> The CRC error there is the key. Check your cables, backplane & PSU.
> 

Very good to know. Thank you. :) Google had hinted the same thing. I've gone 
into the machine and made sure everything was snug, just in case it was a lose 
cable or connection on the backplane.

I've --add'ed the drive back to the array. I think that should make a simple 
test to see if anything reallocates. After that, I'll try some more read and 
mixed read-write tests to see if the error's going to pop up again, but so far 
after a few hours, not even a single warning*.

Should the problem come back, I'll follow up with a power test, then some 
cable tests. Since it seemed that it was always erroring out on the same drive 
(not 100% sure, but it seems like it), and if its not likely a drive problem, 
it may be one SFF-8087 breakout cable, then swapping the cables should change 
which drive it happens to, if it does I should know its the cable.

* except for this: "[ 1052.626900] The scan_unevictable_pages sysctl/node-
interface has been disabled for lack of a legitimate use case.  If you have 
one, please send an email to linux-mm@kvack.org." and I have absolutely no 
idea what caused that at this point and time. Also don't think its applicable.


-- 
Thomas Fjellstrom
thomas@fjellstrom.ca

  reply	other threads:[~2013-02-11  7:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  1:27 raid/device failure Thomas Fjellstrom
2013-02-11  2:09 ` Phil Turmel
2013-02-11  2:52   ` EJ Vincent
2013-02-11  3:44     ` Phil Turmel
2013-02-11 20:28       ` EJ Vincent
2013-02-11  2:55   ` Thomas Fjellstrom
2013-02-11  3:22 ` Brad Campbell
2013-02-11  7:55   ` Thomas Fjellstrom [this message]
2013-02-11  8:29 ` Roy Sigurd Karlsbakk
2013-02-11  9:13   ` Thomas Fjellstrom
2013-02-12 22:31 ` Thomas Fjellstrom

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=201302110055.40801.thomas@fjellstrom.ca \
    --to=thomas@fjellstrom.ca \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.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).