ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen

ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen

[Pol Hallen]

howdy :-)

in dmesg:

[ 5485.000040] ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 
frozen
[ 5485.000103] ata4.00: failed command: READ FPDMA QUEUED
[ 5485.000140] ata4.00: cmd 60/08:00:9f:00:00/00:00:7c:00:00/40 tag 0 ncq 4096 
in
[ 5485.000141]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 
(timeout)
[ 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!

Pol

Re: ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen

[Tim Small]

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

Re: ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6 frozen

[Jeff Garzik]

On 11/15/2010 09:33 AM, Pol Hallen wrote:
> howdy :-)
>
> in dmesg:
>
> [ 5485.000040] ata4.00: exception Emask 0x0 SAct 0x1b7ffff SErr 0x0 action 0x6
> frozen
> [ 5485.000103] ata4.00: failed command: READ FPDMA QUEUED
> [ 5485.000140] ata4.00: cmd 60/08:00:9f:00:00/00:00:7c:00:00/40 tag 0 ncq 4096
> in
> [ 5485.000141]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4
> (timeout)
> [ 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!


https://ata.wiki.kernel.org/index.php/Libata_error_messages