From: Erik Slagter <erik@slagter.name>
To: linux-ide@vger.kernel.org
Subject: Re: DriveStatusError BadCRC
Date: Mon, 08 Aug 2005 11:54:17 +0200 [thread overview]
Message-ID: <1123494857.22328.52.camel@localhost.localdomain> (raw)
In-Reply-To: <311601c905080707384a2def32@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On Sun, 2005-08-07 at 08:38 -0600, Eric D. Mudama wrote:
> 51/84 indicates the crc failed on the incoming write data from your
> system. These failures should be very rare (on PATA), but the bummer
> is they don't have anything to do with bad blocks on the media or
> degrading heads...
>
> What is the temperature like inside your case? What host adapter are
> you using? How many drives in the system?
I'd suggest trying another cable... And also a lower UDMA setting.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-08 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 9:32 DriveStatusError BadCRC sampei02
2005-08-07 10:47 ` Tyler
2005-08-07 14:38 ` Eric D. Mudama
2005-08-08 9:54 ` Erik Slagter [this message]
2005-08-10 10:14 ` SOLVED: " sampei02
2005-08-10 10:25 ` 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=1123494857.22328.52.camel@localhost.localdomain \
--to=erik@slagter.name \
--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).