linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@seoss.co.uk>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ahci timeouts, retries etc.
Date: Fri, 23 Oct 2009 12:26:57 +0100	[thread overview]
Message-ID: <4AE19301.9000906@seoss.co.uk> (raw)
In-Reply-To: <4AD7C3D9.9090805@gmail.com>

Robert Hancock wrote:
>>
>> I'm assuming that the kernel will retry these requests after the sata
>> link has been reset?
>
> Yes.
>
>>
>> The errors appear to be randomly distributed over the four drives on
>> this machine - all are Seagate ST31000340NS with either firmware version
>> SN05 or SN16...
>
> This kind of problem often seems to be due to signal integrity or 
> power problems. For whatever reason, an insufficient power supply (or 
> something like overloading one power cable) can tend to trigger SATA 
> errors as an early symptom..

Thanks for the reply Robert...  The power (and SATA signal) delivery to 
these drives is via a hot-swap backplane which is built-into the chassis 
- I had considered some sort of hardware fault here, and that would seem 
possible, but I don't really have any way to check as I don't have 
access to another one of these machines in order to swap-out parts etc.  
IPMI info looks OK (although I realise this may not catch transient 
power problems at the drives etc.).

The timeouts appear to happen about 4 times per month.  In the absence 
of any other easy strategies, I've disabled SMART data collection on 
this machine, on the off-chance that that makes any difference....

Cheers,

Tim.

      reply	other threads:[~2009-10-23 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 16:51 ahci timeouts, retries etc Tim Small
2009-10-16  0:52 ` Robert Hancock
2009-10-23 11:26   ` Tim Small [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=4AE19301.9000906@seoss.co.uk \
    --to=tim@seoss.co.uk \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@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).