From: Tejun Heo <htejun@gmail.com>
To: Patrik Jonsson <patrik@ucolick.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Frequent SATA errors / port timeouts in 2.6.18.3?
Date: Tue, 19 Dec 2006 16:09:48 +0900 [thread overview]
Message-ID: <4587903C.3050204@gmail.com> (raw)
In-Reply-To: <4580907D.1020407@ucolick.org>
Patrik Jonsson wrote:
> First I thought it was a cabling or card issue, because the same drive
> got kicked twice. That drive was connected to a 2-port SIG sata_sil24
> card. However, I just had another drive kicked that's connected to the
> onboard sata_nv, which leads me to suspect that the upgraded kernel
> might have something to do with it. A quick googling seems to indicate
> that others are seeing this with 2.6.18, too, so I was wondering if
> anyone knows more.
I don't think there has been any change which can affect both sata_sil24
and sata_nv to cause timeouts. Please post the result of 'smartctl -d
ata -a /dev/sdX' of failed devices.
> The drives contain science data for analysis, so it
> would be a pain (though not a disaster) to lose it. Would it be
> advisable to revert to the previous 2.6.17 that I was running before or
> is this a problem that's fixed in a later kernel than the one I'm
> running now?
>
> I did at the same time also install an Areca ARC1260 controller and
> connected a bunch of drives to it, so another idea I had was cable
> interference or something (there are now 18 drives in the machine).
>
> Any ideas or thought would be appreciated,
Power quality degradation can cause transmission failures which can
result in timeouts. How are your power lines hooked?
--
tejun
next prev parent reply other threads:[~2006-12-19 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4578F5D4.8080205@moniker.net>
2006-12-13 23:45 ` Frequent SATA errors / port timeouts in 2.6.18.3? Patrik Jonsson
2006-12-19 7:09 ` Tejun Heo [this message]
2006-12-20 0:31 ` Patrik Jonsson
2006-12-20 0:42 ` Tejun Heo
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=4587903C.3050204@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=patrik@ucolick.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).