From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial ATA Lockups
Date: Wed, 28 Dec 2005 01:33:45 -0600 [thread overview]
Message-ID: <43B23FD9.2060004@shaw.ca> (raw)
In-Reply-To: <5oCZ7-3FB-17@gated-at.bofh.it>
Tomas Carnecky wrote:
> My setup: Shuttle XPC Barebone, AMD CPU, two serial ATA disks in a
> software raid setup.
> When the system is under heavy load (start World of Warcraft, dd
> if=/dev/zero of=/part/file etc) I get these messages in dmesg:
>
> ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x84 { DriveStatusError BadCRC }
>
> over and over, pages with these messages.
BadCRC indicates CRC errors during data transfers on the SATA interface.
This is almost certainly hardware problems - most likely a bad SATA
cable, or maybe a bad drive or motherboard controller.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-12-28 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5oCZ7-3FB-17@gated-at.bofh.it>
2005-12-28 7:33 ` Robert Hancock [this message]
2005-12-28 7:25 Serial ATA Lockups Tomas Carnecky
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=43B23FD9.2060004@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@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