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
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
