ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
Early during booting phase, dmesg shows:

[    0.515651] ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port
0xfdefe180 irq 17
[    0.833387] ata6: SATA link down (SStatus 0 SControl 300)

But later, it reports lots like the following stanza:

[164362.715469] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000
action 0xe frozen
[164362.715474] ata6: irq_stat 0x00000040, connection status changed
[164362.715479] ata6: SError: { DevExch }
[164362.715490] ata6: hard resetting link
[164363.433615] ata6: SATA link down (SStatus 0 SControl 300)
[164363.446934] ata6: EH complete

Is it related to a disk drive, and if so, is there a way to know which
drive is on ata6?

PS: There are two drives attached to the system, reported by dmesg like so:
[    0.872490] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks:
(80.0 GB/74.5 GiB)
[    0.874828] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250
GB/232 GiB)

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Paul Hartman-3
On Wed, Jul 31, 2013 at 1:11 PM, Thanasis <[hidden email]> wrote:

> Early during booting phase, dmesg shows:
>
> [    0.515651] ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port
> 0xfdefe180 irq 17
> [    0.833387] ata6: SATA link down (SStatus 0 SControl 300)
>
> But later, it reports lots like the following stanza:
>
> [164362.715469] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000
> action 0xe frozen
> [164362.715474] ata6: irq_stat 0x00000040, connection status changed
> [164362.715479] ata6: SError: { DevExch }
> [164362.715490] ata6: hard resetting link
> [164363.433615] ata6: SATA link down (SStatus 0 SControl 300)
> [164363.446934] ata6: EH complete
>
> Is it related to a disk drive, and if so, is there a way to know which
> drive is on ata6?
>
> PS: There are two drives attached to the system, reported by dmesg like so:
> [    0.872490] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks:
> (80.0 GB/74.5 GiB)
> [    0.874828] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250
> GB/232 GiB)
>

There are a few approaches to try figuring it out explained here:

http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Bruce Hill, Jr.
In reply to this post by Thanasis
On Wed, Jul 31, 2013 at 09:11:22PM +0300, Thanasis wrote:

> Early during booting phase, dmesg shows:
>
> [    0.515651] ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port
> 0xfdefe180 irq 17
> [    0.833387] ata6: SATA link down (SStatus 0 SControl 300)
>
> But later, it reports lots like the following stanza:
>
> [164362.715469] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000
> action 0xe frozen
> [164362.715474] ata6: irq_stat 0x00000040, connection status changed
> [164362.715479] ata6: SError: { DevExch }
> [164362.715490] ata6: hard resetting link
> [164363.433615] ata6: SATA link down (SStatus 0 SControl 300)
> [164363.446934] ata6: EH complete
>
> Is it related to a disk drive, and if so, is there a way to know which
> drive is on ata6?
>
> PS: There are two drives attached to the system, reported by dmesg like so:
> [    0.872490] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks:
> (80.0 GB/74.5 GiB)
> [    0.874828] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250
> GB/232 GiB)
 
Short and sweet... bad SATA cable, bad controller, or bad drive.

Long and detailed later.
--
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
[hidden email]
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
In reply to this post by Paul Hartman-3
on 07/31/2013 10:06 PM Paul Hartman wrote the following:
>
> There are a few approaches to try figuring it out explained here:
>
> http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name
>

Looking into /sys/dev/block it seems like /dev/sda is on ata1 and
/dev/sdb is on ata2, and since there is nothing else attached to the
system, the ata6 problem may be related to a controller (as Bruce said),
and hopefully not a disk drive.

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Paul Hartman-3
In reply to this post by Thanasis
On Wed, Jul 31, 2013 at 1:11 PM, Thanasis <[hidden email]> wrote:

> Early during booting phase, dmesg shows:
>
> [    0.515651] ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port
> 0xfdefe180 irq 17
> [    0.833387] ata6: SATA link down (SStatus 0 SControl 300)
>
> But later, it reports lots like the following stanza:
>
> [164362.715469] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000
> action 0xe frozen
> [164362.715474] ata6: irq_stat 0x00000040, connection status changed
> [164362.715479] ata6: SError: { DevExch }
> [164362.715490] ata6: hard resetting link
> [164363.433615] ata6: SATA link down (SStatus 0 SControl 300)
> [164363.446934] ata6: EH complete
>
> Is it related to a disk drive, and if so, is there a way to know which
> drive is on ata6?
>
> PS: There are two drives attached to the system, reported by dmesg like so:
> [    0.872490] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks:
> (80.0 GB/74.5 GiB)
> [    0.874828] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250
> GB/232 GiB)
>

If no disks are attached, I wonder if something is probing it?

I checked my dmesg and every time I plug in my eSATA enclosure, I see
this very similar message:

[156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000
action 0xe frozen
[156541.724587] ata7: irq_stat 0x00000040, connection status changed
[156541.724593] ata7: SError: { CommWake DevExch }
[156541.724604] ata7: hard resetting link
[156551.725559] ata7: softreset failed (device not ready)
[156551.725567] ata7: hard resetting link

(and then a bunch of lines initializing all of the disks in the enclosure).

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Bruce Hill, Jr.
In reply to this post by Thanasis
On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote:

> on 07/31/2013 10:06 PM Paul Hartman wrote the following:
> >
> > There are a few approaches to try figuring it out explained here:
> >
> > http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name
> >
>
> Looking into /sys/dev/block it seems like /dev/sda is on ata1 and
> /dev/sdb is on ata2, and since there is nothing else attached to the
> system, the ata6 problem may be related to a controller (as Bruce said),
> and hopefully not a disk drive.
 
Sorry I don't have time to reply atm. If either drive has errors continuing,
please change the SATA cable for a new one. Or, at least, reseat them, and
aftewards report results.
--
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
[hidden email]
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
In reply to this post by Paul Hartman-3
on 08/01/2013 12:59 AM Paul Hartman wrote the following:

> If no disks are attached, I wonder if something is probing it?
>
> I checked my dmesg and every time I plug in my eSATA enclosure, I see
> this very similar message:
>
> [156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000
> action 0xe frozen
> [156541.724587] ata7: irq_stat 0x00000040, connection status changed
> [156541.724593] ata7: SError: { CommWake DevExch }
> [156541.724604] ata7: hard resetting link
> [156551.725559] ata7: softreset failed (device not ready)
> [156551.725567] ata7: hard resetting link
>
> (and then a bunch of lines initializing all of the disks in the enclosure).
>

Me too. That's exactly how I use this Sata port, so it must be related
to the way the kernel handles/probes it.

BTW, I use a cable which is sata <-> eSata, i.e. sata for the
motherboard side and eSata for the external disk side, and I keep the
cable connected to the motherboard and the disk connected to the cable.
I just power on the eSata external disk enclosure whenever I need to use
the disk, and before switching the power off, I just unmount the disk.
Is that a correct procedure?

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
In reply to this post by Bruce Hill, Jr.
on 08/01/2013 01:10 AM Bruce Hill wrote the following:

> On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote:
>> on 07/31/2013 10:06 PM Paul Hartman wrote the following:
>>>
>>> There are a few approaches to try figuring it out explained here:
>>>
>>> http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name
>>>
>>
>> Looking into /sys/dev/block it seems like /dev/sda is on ata1 and
>> /dev/sdb is on ata2, and since there is nothing else attached to the
>> system, the ata6 problem may be related to a controller (as Bruce said),
>> and hopefully not a disk drive.
>  
> Sorry I don't have time to reply atm. If either drive has errors continuing,
> please change the SATA cable for a new one. Or, at least, reseat them, and
> aftewards report results.
>

I keep the cable connected to both the motherboard's sata port and to
the external eSata disk enclosure.
I noticed that the cable indeed needed reseating, but on the other hand,
the external disk had *not* been powered on since last reboot, i.e.
before these "errors or warnings" in dmesg had appeared.

FWIW, after reseating the cable, I powered the external disk on, run a
forced fsck on it, and no errors where reported.

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

David Haller-5
In reply to this post by Paul Hartman-3
Hello,

On Wed, 31 Jul 2013, Paul Hartman wrote:
>http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name

All flawed IMHO. My version (works with PATA too), possibly flawed too:

==== ~/bin/ataid_to_drive.sh ====
#!/bin/bash
oIFS="$IFS"
IFS=$'\n'
CTRLS=( $(/sbin/lspci | grep 'ATA\|IDE') )
IFS="$oIFS"
for arg; do
    if test -z "${arg/ata*}"; then
        arg="${arg/ata}"
    fi
    if test -z "${arg/*.*}"; then
        ata="${arg%.*}"
        subid="$(printf "%i" "${arg##*.}")"
    else
        ata="$arg"
    fi
    echo "ata${ata}${subid/*/.$(printf "%02i" $subid)} is:"
    for ctrl in ${CTRLS[@]%% *}; do
        idpath="/sys/bus/pci/devices/*${ctrl}/*/*/*/unique_id"
        grep "^${ata}$" $idpath 2>/dev/null
        host=$(grep "^${ata}$" $idpath 2>/dev/null | \
               sed 's@.*/host\([0-9A-Fa-f]\+\)/.*@\1@')
        if test -n "$host"; then
            dmesg | grep "\] s[dr] $host:0:$subid.*Attached"
        fi
    done
done
====

Usage samples:

$ ataid_to_drive.sh ata23.00
$ ataid_to_drive.sh ata23.01
$ ataid_to_drive.sh ata23
$ ataid_to_drive.sh 23.01
$ ataid_to_drive.sh 23.1
$ ataid_to_drive.sh 23
$ ataid_to_drive.sh $(seq 1 4)

So you can use c&p from dmest/syslog or enter the number(s) yourself.

HTH,
-dnh

--
This space intentionally left aligned.

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Paul Hartman-3
In reply to this post by Thanasis
On Thu, Aug 1, 2013 at 2:51 AM, Thanasis <[hidden email]> wrote:

> on 08/01/2013 01:10 AM Bruce Hill wrote the following:
>> On Wed, Jul 31, 2013 at 11:17:02PM +0300, Thanasis wrote:
>>> on 07/31/2013 10:06 PM Paul Hartman wrote the following:
>>>>
>>>> There are a few approaches to try figuring it out explained here:
>>>>
>>>> http://serverfault.com/questions/244944/linux-ata-errors-translating-to-a-device-name
>>>>
>>>
>>> Looking into /sys/dev/block it seems like /dev/sda is on ata1 and
>>> /dev/sdb is on ata2, and since there is nothing else attached to the
>>> system, the ata6 problem may be related to a controller (as Bruce said),
>>> and hopefully not a disk drive.
>>
>> Sorry I don't have time to reply atm. If either drive has errors continuing,
>> please change the SATA cable for a new one. Or, at least, reseat them, and
>> aftewards report results.
>>
>
> I keep the cable connected to both the motherboard's sata port and to
> the external eSata disk enclosure.
> I noticed that the cable indeed needed reseating, but on the other hand,
> the external disk had *not* been powered on since last reboot, i.e.
> before these "errors or warnings" in dmesg had appeared.

Some internal SATA ports apparently don't support hotplugging. I don't
know if perhaps your chipset is one of them, if you Google your
motherboard's SATA chipset maybe you can find out. If it has always
worked before and now suddenly throws errors, that seems unlikely to
be the cause...

> FWIW, after reseating the cable, I powered the external disk on, run a
> forced fsck on it, and no errors where reported.

Or maybe that's all it was. :)

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Bruce Hill, Jr.
In reply to this post by Thanasis
On Thu, Aug 01, 2013 at 10:51:56AM +0300, Thanasis wrote:
>
> I keep the cable connected to both the motherboard's sata port and to
> the external eSata disk enclosure.

The _only_ time that I am _certain_ I've received that particular error is in
a very similar case. My workstation has 2 SATA cables plugged to the
motherboard and hanging out of it. Both of them have given such errors before.
Internal SATA connectors are a poor design; external (eSATA) is much better.
And sometimes one cable works and not the other.

> I noticed that the cable indeed needed reseating, but on the other hand,
> the external disk had *not* been powered on since last reboot, i.e.
> before these "errors or warnings" in dmesg had appeared.
>
> FWIW, after reseating the cable, I powered the external disk on, run a
> forced fsck on it, and no errors where reported.

That might not have been necessary, because according to the error the device
was disconnected. Glad you have solved your issue.

In order to test/fix/backup/use external drives I'm thinking of purchasing a
SATA to eSATA Slot Plate Bracket
http://www.amazon.com/StarTech-eSATA-Plate-Bracket-ESATAPLATE2/dp/B000NPKGH4/ref=sr_1_2?s=electronics&ie=UTF8&qid=1375365716&sr=1-2&keywords=SATA+to+eSATA+Slot+Plate+Bracket
and an eSATA enclosure, something like this
http://www.sabrent.com/category/hard-drive-enclosures/ECS-STU35K/
--
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
[hidden email]
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Bruce Hill, Jr.
In reply to this post by Thanasis
On Thu, Aug 01, 2013 at 10:37:34AM +0300, Thanasis wrote:

>
> Me too. That's exactly how I use this Sata port, so it must be related
> to the way the kernel handles/probes it.
>
> BTW, I use a cable which is sata <-> eSata, i.e. sata for the
> motherboard side and eSata for the external disk side, and I keep the
> cable connected to the motherboard and the disk connected to the cable.
> I just power on the eSata external disk enclosure whenever I need to use
> the disk, and before switching the power off, I just unmount the disk.
> Is that a correct procedure?

The problem is more than likely with the SATA cable plugged to the
motherboard. How is the cable routed from the motherboard to the external
enclosure? If it's not stable, that can cause this problem; which is why my
present thought is to buy 2 items as shown in the previous post.
--
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
[hidden email]
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Volker Armin Hemmann
In reply to this post by Thanasis
Am 01.08.2013 09:37, schrieb Thanasis:

> on 08/01/2013 12:59 AM Paul Hartman wrote the following:
>
>> If no disks are attached, I wonder if something is probing it?
>>
>> I checked my dmesg and every time I plug in my eSATA enclosure, I see
>> this very similar message:
>>
>> [156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000
>> action 0xe frozen
>> [156541.724587] ata7: irq_stat 0x00000040, connection status changed
>> [156541.724593] ata7: SError: { CommWake DevExch }
>> [156541.724604] ata7: hard resetting link
>> [156551.725559] ata7: softreset failed (device not ready)
>> [156551.725567] ata7: hard resetting link
>>
>> (and then a bunch of lines initializing all of the disks in the enclosure).
>>
> Me too. That's exactly how I use this Sata port, so it must be related
> to the way the kernel handles/probes it.
>
> BTW, I use a cable which is sata <-> eSata, i.e. sata for the
> motherboard side and eSata for the external disk side, and I keep the
> cable connected to the motherboard and the disk connected to the cable.
> I just power on the eSata external disk enclosure whenever I need to use
> the disk, and before switching the power off, I just unmount the disk.
> Is that a correct procedure?
>
> .
>
that is not an error. That is the linux kernel initializing the sata
connection.

stuff like that always happens if you hotplug a (e)sata device.

Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
In reply to this post by Bruce Hill, Jr.
on 08/01/2013 05:43 PM Bruce Hill wrote the following:

> On Thu, Aug 01, 2013 at 10:37:34AM +0300, Thanasis wrote:
>>
>> Me too. That's exactly how I use this Sata port, so it must be related
>> to the way the kernel handles/probes it.
>>
>> BTW, I use a cable which is sata <-> eSata, i.e. sata for the
>> motherboard side and eSata for the external disk side, and I keep the
>> cable connected to the motherboard and the disk connected to the cable.
>> I just power on the eSata external disk enclosure whenever I need to use
>> the disk, and before switching the power off, I just unmount the disk.
>> Is that a correct procedure?
>
> The problem is more than likely with the SATA cable plugged to the
> motherboard. How is the cable routed from the motherboard to the external
> enclosure? If it's not stable, that can cause this problem; which is why my
> present thought is to buy 2 items as shown in the previous post.
>

I didn't say it from the start for simplicity's sake, but actually, I am
using a bracket like the one you said, and the reseating was needed at
the bracket's eSata (external) port.

I think that there are specs for eSata cables and ports so that the
connection between them is made secure and doesn't get easily loose, but
in my case, either the (external) eSata cable or the Bracket's ports (or
both cable and bracket) do not follow these specs.


Reply | Threaded
Open this post in threaded view
|

Re: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

Thanasis
In reply to this post by Volker Armin Hemmann
on 08/01/2013 07:38 PM Volker Armin Hemmann wrote the following:

> Am 01.08.2013 09:37, schrieb Thanasis:
>> on 08/01/2013 12:59 AM Paul Hartman wrote the following:
>>
>>> If no disks are attached, I wonder if something is probing it?
>>>
>>> I checked my dmesg and every time I plug in my eSATA enclosure, I see
>>> this very similar message:
>>>
>>> [156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000
>>> action 0xe frozen
>>> [156541.724587] ata7: irq_stat 0x00000040, connection status changed
>>> [156541.724593] ata7: SError: { CommWake DevExch }
>>> [156541.724604] ata7: hard resetting link
>>> [156551.725559] ata7: softreset failed (device not ready)
>>> [156551.725567] ata7: hard resetting link
>>>

> that is not an error. That is the linux kernel initializing the sata
> connection.
>
> stuff like that always happens if you hotplug a (e)sata device.
>
>

Thanks Volker, and thank you all for your help.