From: Robert Hancock <hancockrwd@gmail.com>
To: Peter <elekesp@freemail.hu>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: sata problem...
Date: Sat, 12 Mar 2011 20:10:51 -0600 [thread overview]
Message-ID: <4D7C27AB.1010908@gmail.com> (raw)
In-Reply-To: <E0ABD6B5-3B05-48D8-AFDC-9FD559AF2583@freemail.hu>
On 03/12/2011 02:33 PM, Peter wrote:
> Hi!
>
> Motherboard is
> GIGABYTE GA-D510UD
..
> [ 1.782644] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 1.785561] ata4.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133
> [ 1.785570] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> [ 1.787834] ata4.00: configured for UDMA/133
...
> [ 2.098472] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [ 2.098483] ata4.00: irq_stat 0x40000008
> [ 2.098493] ata4.00: failed command: READ FPDMA QUEUED
> [ 2.098512] ata4.00: cmd 60/20:00:bf:0c:0e/00:00:74:00:00/40 tag 0 ncq 16384 in
> [ 2.098516] res 41/40:00:c7:0c:0e/00:00:74:00:00/40 Emask 0x409 (media error)<F>
> [ 2.098526] ata4.00: status: { DRDY ERR }
> [ 2.098532] ata4.00: error: { UNC }
> [ 2.104001] ata4.00: configured for UDMA/133
> [ 2.104026] ata4: EH complete
..
> I dont know why there is "[ 2.098493] ata4.00: failed command: READ FPDMA QUEUED" in dmesg.
>
> I have 3 WD Green 1TB HDD, and I samsung 160GB HDD.
> 1 SAMSUNG and 1 WD on the intel SATA,
> 2 WD on the GIGABYTE Sata.
> I think the problem is only with the gigabye sata port.
That's an uncorrectable read error the drive is reporting. Most likely
that hard drive is failing.
next prev parent reply other threads:[~2011-03-13 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04BB68BD-352B-45B0-A7FC-42B6005A80B3@freemail.hu>
[not found] ` <20110227153338.GA23527@mtj.dyndns.org>
2011-03-12 20:33 ` sata problem Peter
2011-03-13 2:10 ` Robert Hancock [this message]
2011-03-13 8:42 ` Tejun Heo
2011-03-14 19:22 ` Mark Lord
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=4D7C27AB.1010908@gmail.com \
--to=hancockrwd@gmail.com \
--cc=elekesp@freemail.hu \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).