Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen
908 views
Skip to first unread message
David Christensen
Jun 9, 2012, 8:00:02 PM6/9/12
to
debian-user:
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?
I then upgraded the kernel to 3.2.0-0.bpo.2-amd64 via debian-backports,
and the errors filled the console whenever the disk was busy (such as
running tasksel and installing Graphical desktop environment).
STFW, I installed sysfsutils and added the following entries to
/etc/sysfs.conf. The quantity of messages decreased:
block/sda/device/queue_depth=1
block/sdb/device/queue_depth=1
Any suggestions?
TIA,
David
--
2012-06-09 15:50:58 root@i72600s ~
# cat /etc/debian_version
6.0.5
2012-06-09 15:51:02 root@i72600s ~
# uname -a
Linux i72600s 3.2.0-0.bpo.2-amd64 #1 SMP Sun Jun 3 21:40:57 UTC 2012
x86_64 GNU/Linux
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4FD3D4BA...@holgerdanske.com
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?
I then upgraded the kernel to 3.2.0-0.bpo.2-amd64 via debian-backports,
and the errors filled the console whenever the disk was busy (such as
running tasksel and installing Graphical desktop environment).
STFW, I installed sysfsutils and added the following entries to
/etc/sysfs.conf. The quantity of messages decreased:
block/sda/device/queue_depth=1
block/sdb/device/queue_depth=1
Any suggestions?
TIA,
David
--
2012-06-09 15:50:58 root@i72600s ~
# cat /etc/debian_version
6.0.5
2012-06-09 15:51:02 root@i72600s ~
# uname -a
Linux i72600s 3.2.0-0.bpo.2-amd64 #1 SMP Sun Jun 3 21:40:57 UTC 2012
x86_64 GNU/Linux
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4FD3D4BA...@holgerdanske.com
Camaleón
Jun 10, 2012, 8:00:02 AM6/10/12
to
On Sat, 09 Jun 2012 15:56:58 -0700, David Christensen 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 }
Mmm... given that the system is new (is a DIY or you bought the system
> 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 }
already assembled)? it can be a bad or poor sata cable or loose
connection. I'd first try to replace it and see how it goes.
> I assume these are error messages coming from the disk device driver
> (?). What do they mean?
first locate the offending device and replace the SATA cable (always
use good quality cables and discard the ones coming with the motherboard).
dmesg | grep "ata3.00" will tell what's attached to the SATA 3 port.
> I then upgraded the kernel to 3.2.0-0.bpo.2-amd64 via debian-backports,
> and the errors filled the console whenever the disk was busy (such as
> running tasksel and installing Graphical desktop environment).
>
>
> STFW, I installed sysfsutils and added the following entries to
> /etc/sysfs.conf. The quantity of messages decreased:
>
> block/sda/device/queue_depth=1
> block/sdb/device/queue_depth=1
>
>
> Any suggestions?
the kernel line, let's hope they are landing around here :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Bannister
Jun 10, 2012, 9:50:02 AM6/10/12
to
On Sun, Jun 10, 2012 at 11:55:24AM +0000, Camaleón wrote:
> It can be something coming from the kernel or a hardware problem. I'd
> first locate the offending device and replace the SATA cable (always
> use good quality cables and discard the ones coming with the motherboard).
When you say "discard" here, do you mean toss them out in the rubbish?
> It can be something coming from the kernel or a hardware problem. I'd
> first locate the offending device and replace the SATA cable (always
> use good quality cables and discard the ones coming with the motherboard).
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Curt
Jun 10, 2012, 10:30:01 AM6/10/12
to
On 2012-06-09, David Christensen <dpch...@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
>
> 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?
>
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.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
Jun 10, 2012, 10:30:02 AM6/10/12
to
On Mon, 11 Jun 2012 01:45:59 +1200, Chris Bannister wrote:
> On Sun, Jun 10, 2012 at 11:55:24AM +0000, Camaleón wrote:
>> It can be something coming from the kernel or a hardware problem. I'd
>> first locate the offending device and replace the SATA cable (always
>> use good quality cables and discard the ones coming with the
>> motherboard).
>
> When you say "discard" here, do you mean toss them out in the rubbish?
No, I mean "put them into the drawer" and reserve for another things
> On Sun, Jun 10, 2012 at 11:55:24AM +0000, Camaleón wrote:
>> It can be something coming from the kernel or a hardware problem. I'd
>> first locate the offending device and replace the SATA cable (always
>> use good quality cables and discard the ones coming with the
>> motherboard).
>
> When you say "discard" here, do you mean toss them out in the rubbish?
(hardware testing or emergency situations).
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Christensen
Jun 11, 2012, 12:10:01 AM6/11/12
to
On 06/10/2012 04:55 AM, Camaleón wrote:
> ... (is a DIY or you bought the system already assembled)?
I bought parts and put them together.
On 06/10/2012 04:55 AM, Camaleón wrote:
> dmesg | grep "ata3.00" will tell what's attached to the SATA 3 port.
The Intel 520 SSD.
On 06/10/2012 04:55 AM, Camaleón wrote:
> ... it can be a bad or poor sata cable or loose
the problems persisted. I installed the SSD internally and the problems
went away. :-)
Thanks!
David
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4FD56DF2...@holgerdanske.com
> ... (is a DIY or you bought the system already assembled)?
I bought parts and put them together.
On 06/10/2012 04:55 AM, Camaleón wrote:
> dmesg | grep "ata3.00" will tell what's attached to the SATA 3 port.
On 06/10/2012 04:55 AM, Camaleón wrote:
> ... it can be a bad or poor sata cable or loose
> connection. I'd first try to replace it and see how it goes.
On 06/10/2012 07:23 AM, Curt wrote:
> 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...
I was using a StarTech SATDOCK2520 mobile dock. I swapped cables and
> 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...
the problems persisted. I installed the SSD internally and the problems
went away. :-)
Thanks!
David
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages