WD MyBook eSata ATA errors

Bug #317858 reported by edv
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have an external Western Digital MyBook 320GB hard drive connected to eSATA. When the drive is idle everything seems to be all right, but as soon as I start writing data on the disk, I keep getting errors in my syslog. Additionally the drive itself makes an audible noise, as if it's rebooting itself. This happens quite alot when writing to the disk, sometimes a few times in a row. Nevertheless, the disk hasn't broken (yet?) even though I've suffered this problem for over an year now. (Yeah writing a bug report takes so much time...)

I've also tried 2 different eSATA cables, 2 different ports and several internal ports, none of which removes this problem.
Attached is some relevant info.

The error itself is usually as follows:

[29717.378493] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[29717.378499] ata4.00: irq_stat 0x40000001
[29717.378504] ata4.00: cmd 35/00:e0:9f:2f:e8/00:00:23:00:00/e0 tag 0 dma 114688 out
[29717.378505] res 51/84:00:7e:30:e8/00:00:23:00:00/e0 Emask 0x10 (ATA bus error)
[29717.378508] ata4.00: status: { DRDY ERR }
[29717.378509] ata4.00: error: { ICRC ABRT }
[29717.378513] ata4: hard resetting link
[29718.198462] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[29718.232376] ata4.00: configured for UDMA/133
[29718.232393] ata4: EH complete
[29720.013668] sd 3:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[29720.049222] sd 3:0:0:0: [sdb] Write Protect is off
[29720.049228] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[29720.078062] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[29846.905625] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[29846.905630] ata4.00: irq_stat 0x40000001
[29846.905635] ata4.00: cmd 35/00:08:ff:8d:e4/00:00:23:00:00/e0 tag 0 dma 4096 out
[29846.905636] res 51/84:00:06:8e:e4/00:00:23:00:00/e0 Emask 0x10 (ATA bus error)
[29846.905639] ata4.00: status: { DRDY ERR }
[29846.905640] ata4.00: error: { ICRC ABRT }
[29846.905645] ata4: hard resetting link
[29847.556517] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[29847.671439] ata4.00: configured for UDMA/133
[29847.671454] ata4: EH complete
[29849.051699] sd 3:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[29849.052352] sd 3:0:0:0: [sdb] Write Protect is off
[29849.052357] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[29849.053036] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
edv (ernovaur) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi edv,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 317858

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
edv (ernovaur) wrote :

Hello, unfortunately I have already replaced the hardware in question.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.