linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: James <jtp@nc.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: read errors corrected
Date: Fri, 31 Dec 2010 13:08:07 +1100	[thread overview]
Message-ID: <20101231130807.7567c09d@notabene.brown> (raw)
In-Reply-To: <AANLkTimhWHfcnDH4Zy6=VGX17_JAH0ON3OMuPhA4oBjf@mail.gmail.com>

On Fri, 31 Dec 2010 01:48:07 +0000 James <jtp@nc.rr.com> wrote:

> Neil,
> 
> I'm runinng 2.6.35.
> 
> Although an expensive route, the only thing I can think to do to
> determine 100% whether the issue is software or hardware (and, if
> hardware, whether SATA controller or the drives) is to swap the drives
> out.
> 
> Ouch!
> 
> Any other ideas, however, would be appreciated before I drop a few
> hundred bucks. :)

Buy a PCIe SATA controller, plug it in and move some/all drives over to that?
Should be a lot less than $100.  Make sure it is a different chipset to what
you have on your motherboard.

NeilBrown

  parent reply	other threads:[~2010-12-31  2:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30  3:20 read errors corrected James
2010-12-30  5:24 ` Mikael Abrahamsson
2010-12-30 16:33   ` James
2010-12-30 16:44     ` Roman Mamedov
2010-12-30 16:51       ` James
2010-12-30 17:59         ` Ryan Wagoner
2010-12-30 18:03           ` James
2010-12-30  9:15 ` Neil Brown
     [not found]   ` <AANLkTik2+Gk1XveqD=crGMH5JshzJqQb_i77ZpOFUncB@mail.gmail.com>
2010-12-30 16:35     ` James
2010-12-30 23:12       ` Neil Brown
2010-12-31  1:48         ` James
2010-12-31  1:56           ` Guy Watkins
2010-12-31  2:08           ` Neil Brown [this message]
2010-12-30 10:13 ` Giovanni Tessore
2010-12-30 16:41   ` James
2011-01-15 12:00     ` Giovanni Tessore
2011-01-16  8:33       ` Jaap Crezee
  -- strict thread matches above, loose matches on Subject: below --
2010-12-30 20:19 Richard Scobie

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=20101231130807.7567c09d@notabene.brown \
    --to=neilb@suse.de \
    --cc=jtp@nc.rr.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 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).