Western Digital MyBook soft resets on eSata

[kmaxwell]

Hello,

I have a Western Digital MyBook Premium ES portable SATA drive. It supports both USB and SATA II via an eSATA connection. Here is the information on the drive:
ata7.00: ATA-6: WD My Book ES, 012, max UDMA/133
ata7.00: 625142448 sectors, multi 0: LBA48
ata7.00: configured for UDMA/133
If more information is needed, please let me know what and I will provide it.

The drive is connected to a JMicron controller, but I also tried a SIL3132 controller. My current controller is:
03:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03)

I can use the drive with small data operations. Once I start to do any major data operations on the drive. Copying large files, etc. I start getting these errors:
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: (irq_stat 0x48000000)
ata7.00: cmd ca/00:00:4f:0a:54/00:00:00:00:00/e3 tag 0 cdb 0x0 data 131072 out
res 51/84:00:4e:0b:54/00:00:03:00:00/e3 Emask 0x10 (ATA bus error)
ata7: soft resetting port
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata7.00: configured for UDMA/133
ata7: EH complete
sd 6:0:0:0: [sdc] 625142448 512-byte hardware sectors (320073 MB)
sd 6:0:0:0: [sdc] Write Protect is off
sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

They continue until the drive even negiotates to this:
ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata7.00: configured for UDMA/33

This HD is capable of 3.0 Gbps, but is does not support NCQ. The libata driver detects that the drive cannot support NCQ. I have forcefully disabled NCQ just to be sure by making the depth 1 with the echo command. I bring up NCQ because I have read a lot of posts that suggest this problem is due the drive not liking what it is seeing in the communication and it is related to NCQ. I have read about blacklisting drives from NCQ negotiation, but don’t know how to even go about this since it must be done prior to driver compilation. I am at my wits end. Does anyone know what I can do to get this to work?

I am running Fedora Core 7 with Linux 2.6.22.9-91.fc7

Thank you,

Kent

[sej7278]

haven't we already been through this?

http://www.fedoraforum.org/forum/sho...d.php?t=169301

[kmaxwell]

"been through" infers a solution. Where is the solution?

[Firewing1]

First of all, that type of attitude won't get you anywhere. Second of all, the fact you didn't get a solution doesn't matter. It's explicitly stated in the guides NOT to double post. Thread closed.