Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

[Raymond]

The Ubuntu 16.04.1 LTS upgrade from kernel 4.4.0-21 to 4.4.0-34 introduced the following periodic error message sequence reported in dmesg/syslog:

...
sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]
sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]
sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]
sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
...

These repeat at precisely five and ten minute intervals but appear to result in no data corruption, nor performance degradation on the external USB drive.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0c: rap 3412 F...m pulseaudio
 /dev/snd/pcmC1D0p: rap 3412 F...m pulseaudio
 /dev/snd/controlC1: rap 3412 F.... pulseaudio
 /dev/snd/controlC0: rap 3412 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 30 19:48:43 2016
HibernationDevice: RESUME=UUID=bb098361-baff-41e3-bf95-dad938b5d42c
InstallationDate: Installed on 2016-08-10 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lo no wireless extensions.

 enp0s9 no wireless extensions.
MachineType: ECS K8M890M-M
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=d38a2b9b-2da3-48e2-b5f8-a464f49a5dc5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080013
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K8M890M-M
dmi.board.vendor: ECS
dmi.board.version: 1.X
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd12/29/2006:svnECS:pnK8M890M-M:pvr1.X:rvnECS:rnK8M890M-M:rvr1.X:cvnECS:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: K8M890M-M
dmi.product.version: 1.X
dmi.sys.vendor: ECS

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19

[Andrew Piziali (bj7u6139zdy-andy)]

Joseph, yes, we will be testing the 4.4.19 kernel to see if the DID_ERRORs manifest themselves.

[Raymond (i-ray)]

Joseph, we just verified that this bug manifests itself in the current upstream kernel (4.4.19). I added the tag "kernel-bug-exists-upstream" to the report. Thanks!

[penalvch (penalvch)]

Raymond, to keep this relevant to upstream, one would want to test the latest mainline kernel (4.8-rc5) as it is released.

Could you please advise?

[Raymond (i-ray)]

Christopher, we (Andrew and Raymond) just verified that this bug still manifests itself in the 4.8-rc5 kernel (see below). Please let us know if you need any further information.

Thanks!

---
Sep 13 18:09:59 penbrook2 kernel: [ 670.050331] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

Sep 13 18:09:59 penbrook2 kernel: [ 670.050336] sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]

Sep 13 18:09:59 penbrook2 kernel: [ 670.050339] sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information

Sep 13 18:09:59 penbrook2 kernel: [ 670.050343] sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00

Sep 13 18:09:59 penbrook2 kernel: [ 670.559187] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

Sep 13 18:09:59 penbrook2 kernel: [ 670.559194] sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor]

Sep 13 18:09:59 penbrook2 kernel: [ 670.559196] sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information

Sep 13 18:09:59 penbrook2 kernel: [ 670.559201] sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
...

[penalvch (penalvch)]

Raymond, please ensure when providing testing results, you are checking first for the latest mainline kernel available, as now 4.8-rc6 has been released a few days ago.

[Raymond (i-ray)]

Christopher, we (Andrew and Raymond) just verified that this bug still manifests itself in the 4.8-rc7 kernel (4.8.0-040800rc7-generic). Please let us know if you need any further information.

Thanks!

[penalvch (penalvch)]

Raymond / Andrew Piziali, the next step is to fully commit bisect from kernel 4.4.0-21 to 4.4.0-34 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Øyvind Stegard (oyvindstegard)]

Christopher, I think there is an upstream bug report for this problem:
https://bugzilla.kernel.org/show_bug.cgi?id=153241

(I thought my hard drive was dying when these messages suddenly appeared on a server running Ubuntu 14.04 with 4.4.0-38-kernel.)

[Andrew Piziali (bj7u6139zdy-andy)]

Christopher, since bug report 153241 documents the bisecting the kernels to isolate this problem, is there any reason for Raymond and I to do likewise?

[Chris Samuel (chris-csamuel)]

Just to update that this is still happening in 4.8.0-27-generic (AMD64).

[Mark (mark-k)]

Based on the first comment to the kernel bug I filed: https://bugzilla.kernel.org/show_bug.cgi?id=153241#c1
the problem is most likely with udisks, not the kernel itself.

I filed a bug for udisks about this issue, see https://bugs.freedesktop.org/show_bug.cgi?id=98991