From: Tejun Heo <htejun@gmail.com>
To: Jim MacBaine <jmacbaine@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-ide@vger.kernel.org
Subject: Re: SATA timeouts on two disks
Date: Mon, 21 Jan 2008 16:47:58 +0900 [thread overview]
Message-ID: <47944E2E.2070300@gmail.com> (raw)
In-Reply-To: <3afbacad0801190822v19be782er3d48cbc94293e262@mail.gmail.com>
Jim MacBaine wrote:
> On Jan 13, 2008 1:07 PM, Mikael Pettersson <mikpe@it.uu.se> wrote:
>
>> The fact that the problems occur on different disks on
>> different controllers driven by different drivers indicates
>> that it's not a disk, controller, or driver problem.
>>
>> I strongly suspect an underdimensioned or failing PSU.
>
> Thanks a lot for your clues.
>
> I bought a new PSU on Monday and didn't get any new disk failures for
> days. But last night the same time-outs occurred again on two disks.
> I guess I will try to replace the motherboard including the two SATA
> controllers next.
If you still have the old PSU lying around, please try to power one of
the failing drive with the old PSU. Just leave everything else as-is,
power-up old PSU by itself as described in the following web page and
connect only one of the failing drive to the old PSU.
http://modtown.co.uk/mt/article2.php?id=psumod
And see whether the problem continues and if so on which drives.
Connecting SATA drives to separate power is completely safe even if they
don't have common ground because SATA connection never directly connect
to each other.
--
tejun
next prev parent reply other threads:[~2008-01-21 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 0:56 SATA timeouts on two disks Jim MacBaine
2008-01-13 12:07 ` Mikael Pettersson
2008-01-19 16:22 ` Jim MacBaine
2008-01-19 16:50 ` rgheck
2008-01-19 16:58 ` Jim MacBaine
2008-01-21 7:47 ` Tejun Heo [this message]
2008-01-24 17:31 ` Jim MacBaine
2008-01-24 23:19 ` Tejun Heo
2008-01-25 3:24 ` rgheck
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=47944E2E.2070300@gmail.com \
--to=htejun@gmail.com \
--cc=jmacbaine@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.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;
as well as URLs for NNTP newsgroup(s).