From: Jim Paris <jim@jtan.com>
To: Simon Kirby <sim@netnation.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: Data corruption with sata_sil (Sil 3112)
Date: Fri, 4 May 2007 22:40:04 -0400 [thread overview]
Message-ID: <20070505024004.GA17765@jim.sh> (raw)
In-Reply-To: <20070504085955.GA5937@hostway.ca>
> I've been having problems with Sil 3112 cards I purchased for additional
> SATA ports resulting in read data corruption, about 3-5 instances over
> 2 GB of data, 100% reproducible.
..
> I just rebuilt the entire box with the remains of another (went from
> A7V8X (VIA) to A7N8X (NVidia), new CPU, new RAM, new power supply),
> thinking the problem was related to the motherboard. The issue followed
> to the new box.
Have you tried different disks? I recently spent a long time trying
to track down the same sort of problem and it ended up being a bad
HD (not a media failure, so SMART didn't report it).
> This new motherboard has an onboard Sil 3112 as well. The old onboard
> was VIA SATA, which did not corrupt anything. The Sil 3112 onboard now
> does too.
Maybe the VIA controller was only 1.5 Gbps and your 3112 controllers
are running at 3.0 Gbps? Some drives have a jumper that lets you
limit their operation to 1.5, which you could try.
> Scipt used to md5sum to find corruption:
>
> find $* -type f -print0 | sort -z | xargs -0 md5sum
Can you figure out the nature of the corruption? Flipped bit, entire
blocks corrupted, etc? Maybe make two big identical files and use
"cmp -l" to see how they read differently.
-jim
next prev parent reply other threads:[~2007-05-05 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 8:59 Data corruption with sata_sil (Sil 3112) Simon Kirby
2007-05-05 2:40 ` Jim Paris [this message]
2007-05-05 15:34 ` 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=20070505024004.GA17765@jim.sh \
--to=jim@jtan.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=sim@netnation.com \
/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).