Re: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen
On 2012-06-09, David Christensen <dpchrist@holgerdanske.com> wrote:
>
> I have a new machine with debian-6.0.5-amd64 and:
>
> Intel i7-2600S processor
> Intel DQ67SW motherboard
> Intel 520 Series 60 GB SSD
>
>
> I noticed error messages similar to the following example on the console:
>
> [ 131.742744] ata3.00: exception Emask 0x10 SAct 0x0 SErr
> 0x400100 action 0x6 frozen
> [ 131.742787] ata3.00: irq_stat 0x08000000, interface fatal error
> [ 131.742806] ata3: SError: { UnrecovData Handshk }
> [ 131.742822] ata3.00: failed command: WRITE DMA EXT
> [ 131.742839] ata3.00: cmd 35/00:00:c8:ce:79/00:04:00:00:00/e0
> tag 0 dma 524288 out
> [ 131.742840] res 50/00:00:c8:ca:79/00:00:04:00:00/e0
> Emask 0x10 (ATA bus error)
> [ 131.742886] ata3.00: status: { DRDY }
>
>
> I assume these are error messages coming from the disk device driver
> (?). What do they mean?
>
According to this wiki
http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues#Drive_Interface_Issues
it could be a number of things, including:
# inadequate power supply
# device and controller don't like each other on 3Gbps
# cable too long or flaky connector (especially with eSATA cables or
genders or backplanes)
# faulty controller or drive
etc...
Something similar happened to me and I went out and bought another
machine. I've still got the failing (ed) one (which eventually would not boot at
all, especially after I kind of took it apart and maybe didn't put it
back together correctly ;-)), but I'm still planning on replacing
the internal sata cables to see if that does the trick.
If the new machine is under warranty, maybe you can get the shop you
bought it from to fix it, if you indeed bought it from a shop at all.
Good luck.
Reply to: