From: Tim Small <tim@seoss.co.uk>
To: Pol Hallen <raid2@fuckaround.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen
Date: Mon, 15 Nov 2010 15:05:17 +0000 [thread overview]
Message-ID: <4CE14C2D.5090701@seoss.co.uk> (raw)
In-Reply-To: <201011151533.17638.raid2@fuckaround.org>
On 15/11/10 14:33, Pol Hallen wrote:
> [ 5485.000265] ata4.00: status: { DRDY }
> [ 5485.000293] ata4.00: failed command: READ FPDMA QUEUED
> [ 5485.000325] ata4.00: cmd 60/60:08:c7:3e:84/00:00:56:00:00/40 tag 1 ncq
> 49152 in
> [ 5485.000326] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
> (timeout)
> [...]
>
> how check which disk should be broke broken? or is it a controller problem?
> thanks!
>
Could be all sorts of things - disk or controller, or cabling, or
PSU... See the libata wiki, and run smartctl -a against each drive in
turn. Look for non-zero reallocated sector counts, non-zero pending
sector counts (check the "raw" data field for both), as well as logged
SMART errors etc. etc. If you have a suspect bad drive, you can use
smartctl to tell the drive to run a smart long self test. See the
documentation.
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
next prev parent reply other threads:[~2010-11-15 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 14:33 ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen Pol Hallen
2010-11-15 15:05 ` Tim Small [this message]
2010-11-15 18:42 ` Jeff Garzik
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=4CE14C2D.5090701@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=raid2@fuckaround.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