From: Stan Hoeppner <stan@hardwarefreak.com>
To: Tomas M <tomas@slax.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: How to prefer some devices over others in raid
Date: Thu, 02 Jan 2014 08:30:24 -0600 [thread overview]
Message-ID: <52C57800.3090802@hardwarefreak.com> (raw)
In-Reply-To: <CAL1oBhovXZhnKMqzoYt=7N5ZHeyX76LK+1LNYMRmcQGGqs7W3w@mail.gmail.com>
On 1/1/2014 12:00 PM, Tomas M wrote:
>> Your initial post suggested you knew which drive was flaky. Now you
>> indicate you don't know which, if any, is flaky. This suggests you have
>> no idea why your array is slow.
>
> Well, I always have an indication which drive is flaky, based on dmesg
> output (e.g. hard resetting ATA3 link, etc). However, sometimes it
> reports that more than one drive has problems
[snip]
Full stop.
Random resets on multiple links indicates a backplane (if present),
HBA/controller, or cable problem, not a drive problem. If you're using
an HBA+backplane with an SFF-8087 4x multilane cable, or a breakout
cable, the problem could be as simple as a lose connection at the
SFF-8087 multilane connector, or a cable gone bad. If you have multiple
discrete SATA cables, one per drive, this indicates a problem with the
controller/HBA.
Ergo, if you have a multilane cable, unplug/replug it and see if that
helps. If not, replace it. If that doesn't solve the problem, replace
the HBA. If replacing the HBA doesn't solve it, replace the backplane.
If you have discrete cables, replacing the HBA should fix the problem.
If you have discrete cables and are using motherboard SATA ports, you'll
need to acquire an HBA and cease using the motherboard ports.
--
Stan
prev parent reply other threads:[~2014-01-02 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 14:42 How to prefer some devices over others in raid Tomas M
2013-12-31 15:17 ` Stan Hoeppner
2014-01-01 6:50 ` Tomas M
2014-01-01 7:05 ` NeilBrown
2014-01-01 16:49 ` Stan Hoeppner
2014-01-01 18:00 ` Tomas M
2014-01-01 20:21 ` Phil Turmel
2014-01-02 14:30 ` Stan Hoeppner [this message]
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=52C57800.3090802@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=tomas@slax.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).