1 |
On Wed, Jul 31, 2013 at 1:11 PM, Thanasis <thanasis@××××××××××.org> wrote: |
2 |
> Early during booting phase, dmesg shows: |
3 |
> |
4 |
> [ 0.515651] ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port |
5 |
> 0xfdefe180 irq 17 |
6 |
> [ 0.833387] ata6: SATA link down (SStatus 0 SControl 300) |
7 |
> |
8 |
> But later, it reports lots like the following stanza: |
9 |
> |
10 |
> [164362.715469] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 |
11 |
> action 0xe frozen |
12 |
> [164362.715474] ata6: irq_stat 0x00000040, connection status changed |
13 |
> [164362.715479] ata6: SError: { DevExch } |
14 |
> [164362.715490] ata6: hard resetting link |
15 |
> [164363.433615] ata6: SATA link down (SStatus 0 SControl 300) |
16 |
> [164363.446934] ata6: EH complete |
17 |
> |
18 |
> Is it related to a disk drive, and if so, is there a way to know which |
19 |
> drive is on ata6? |
20 |
> |
21 |
> PS: There are two drives attached to the system, reported by dmesg like so: |
22 |
> [ 0.872490] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks: |
23 |
> (80.0 GB/74.5 GiB) |
24 |
> [ 0.874828] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 |
25 |
> GB/232 GiB) |
26 |
> |
27 |
|
28 |
If no disks are attached, I wonder if something is probing it? |
29 |
|
30 |
I checked my dmesg and every time I plug in my eSATA enclosure, I see |
31 |
this very similar message: |
32 |
|
33 |
[156541.724580] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4040000 |
34 |
action 0xe frozen |
35 |
[156541.724587] ata7: irq_stat 0x00000040, connection status changed |
36 |
[156541.724593] ata7: SError: { CommWake DevExch } |
37 |
[156541.724604] ata7: hard resetting link |
38 |
[156551.725559] ata7: softreset failed (device not ready) |
39 |
[156551.725567] ata7: hard resetting link |
40 |
|
41 |
(and then a bunch of lines initializing all of the disks in the enclosure). |