From: Robert Hancock <hancockrwd@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: timeout problems on onboard SATA 6.0 controller on Asus P7H57D-V EVO
Date: Tue, 13 Jul 2010 19:44:36 -0600 [thread overview]
Message-ID: <4C3D1684.3050107@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1007110842150.23489@uplift.swm.pp.se>
On 07/11/2010 12:47 AM, Mikael Abrahamsson wrote:
> On Sun, 11 Jul 2010, Robert Hancock wrote:
>
>> Unfortunately that's a pretty generic timeout error that could be
>> caused by quite a few things, like a hardware issue, bad cable, etc.
>> as well as possible driver problem..
>
> Oki, in my case I saw it with multiple drives (all WD though) and
> multiple cables, but with just a single motherboard. The other people in
> the threads I quoted seem to have worked around it by disabling NCQ. I
> saw it on both channels on my motherboard as well, but I guess that
> could be hardware issue. I don't really have any way of fault finding
> this further as I have no lab machine, but it was fairly easy to
> reproduce (letting mdadm hammer the drive with an array check made it
> happen every time).
>
> mdadm never kicked the drive, so whatever was going on was handled
> gracefully, but of course any file access was stopped for 10+ seconds.
In a lot of cases with people having trouble when running multiple hard
drives in a machine - especially with simultaneous access situations,
like a RAID check/rebuild - the problem has been a power issue. It seems
that some hard drives can cause power draw spikes that some PSUs can't
handle, especially if multiple drives are connected to the some cable
from the power supply.
next prev parent reply other threads:[~2010-07-14 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 9:56 timeout problems on onboard SATA 6.0 controller on Asus P7H57D-V EVO Mikael Abrahamsson
2010-07-11 6:20 ` Robert Hancock
2010-07-11 6:47 ` Mikael Abrahamsson
2010-07-14 1:44 ` Robert Hancock [this message]
2010-07-14 6:40 ` Mikael Abrahamsson
2010-07-14 6:56 ` Paul Check
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=4C3D1684.3050107@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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