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