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?
