From: rgheck <rgheck@bobjweil.com>
To: linux-ide@vger.kernel.org
Cc: Jim MacBaine <jmacbaine@gmail.com>, Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: SATA timeouts on two disks
Date: Sat, 19 Jan 2008 11:50:11 -0500 [thread overview]
Message-ID: <47922A43.5080409@bobjweil.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.
>
I don't know if your problems are similar to mine or not. But I have
been having extensive problems for quite some time now. Do you get these
timeouts when using optical drives? That's what seems to trigger it in
my case: If I'm using the optical drives, I'll often see the errors with
them first, and then the whole ATA subsystem seems to go down. Then I
get journal commit errors, general read errors, etc, until the system
basically locks up. Worst case, it all happens very suddenly, and
there's not even anything in the logs. Just a couple messages to the
terminal, usually a journal commit error.
In my case, the opticall drives are a brand new Pioneer DVD-RW on SATA
and an old Plextor on PATA. I mostly see the errors with the latter but
have also seen them with the former. I'd thought I'd fixed it by adding
pnpacpi=off and pci=nomsi,nommconf to the kernel boot options, as well
as libata noacpi=1 to modules.conf, but now I've just had the problem
again. I'm now thinking I should try eliminating the Plextor drive. It
may be that it's the PATA drive that is causing all the trouble. I'll
report if so.
FYI, here are the relevant modules being loaded:
[root@rghquad rgheck]# lsmod | grep ata
pata_amd 20293 0
pata_pdc2027x 17477 0
sata_nv 25157 8
ata_generic 14405 0
libata 114673 4 pata_amd,pata_pdc2027x,sata_nv,ata_generic
scsi_mod 145657 5 sr_mod,sg,usb_storage,libata,sd_mod
The IDE interface is an nVidia MCP55, apparently, on an ASUS P5N32-E mb.
I doubt very much it's a PS issue in my case. There's not that much in
the box.
Richard
next prev parent reply other threads:[~2008-01-19 16:50 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 [this message]
2008-01-19 16:58 ` Jim MacBaine
2008-01-21 7:47 ` Tejun Heo
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=47922A43.5080409@bobjweil.com \
--to=rgheck@bobjweil.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).