主页 / ubuntu / 问题 / 832394
Accepted
Vadim Peretokin
Asked: 2016-10-03 16:48:10 +0800 CST

这个错误是什么意思？

  • 772

日志中不断出现以下错误：

Oct  3 09:51:36 gooseberry kernel: [15050.345601] sd 5:0:0:0: [sdb] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
Oct  3 10:01:35 gooseberry kernel: [15649.821810] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Oct  3 10:01:35 gooseberry kernel: [15649.821817] sd 5:0:0:0: [sdb] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Oct  3 10:01:35 gooseberry kernel: [15649.821820] sd 5:0:0:0: [sdb] tag#0 Add. Sense: No additional sense information
Oct  3 10:01:35 gooseberry kernel: [15649.821824] sd 5:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Oct  3 10:01:36 gooseberry kernel: [15650.300873] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Oct  3 10:01:36 gooseberry kernel: [15650.300879] sd 5:0:0:0: [sdb] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Oct  3 10:01:36 gooseberry kernel: [15650.300881] sd 5:0:0:0: [sdb] tag#0 Add. Sense: No additional sense information
Oct  3 10:01:36 gooseberry kernel: [15650.300885] sd 5:0:0:0: [sdb] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00

$ uname -a 
Linux gooseberry 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
kernel

2 个回答

  1. Best Answer

    我在第一次出现此错误的地方找到了内核版本 4.6.3 及更高版本的错误报告。/var/log/syslog它每 10 分钟发送一次垃圾邮件。该错误在内核版本 4.7.2 时才被报告。显然 Ubuntu 对内核 4.4.0-38 的更新现在已经引入了这个错误。

    此外，USB 连接的驱动器也会报告此错误。我想你sdb是。

    显然，除了它向您的syslog.

    我发现的错误报告可以在：https ://bugzilla.redhat.com/show_bug.cgi?id=1351305

    • 6

  2. 很有可能是由于这个提交：

    0dec8c0d67c64401d97122e4eba347ccc5850622 is the first bad commit
commit 0dec8c0d67c64401d97122e4eba347ccc5850622
Author: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Date:   Fri May 13 12:04:06 2016 -0700

    scsi_lib: correctly retry failed zero length REQ_TYPE_FS commands

    commit a621bac3044ed6f7ec5fa0326491b2d4838bfa93 upstream.

    When SCSI was written, all commands coming from the filesystem
    (REQ_TYPE_FS commands) had data.  This meant that our signal for needing
    to complete the command was the number of bytes completed being equal to
    the number of bytes in the request.  Unfortunately, with the advent of
    flush barriers, we can now get zero length REQ_TYPE_FS commands, which
    confuse this logic because they satisfy the condition every time.  This
    means they never get retried even for retryable conditions, like UNIT
    ATTENTION because we complete them early assuming they're done.  Fix
    this by special casing the early completion condition to recognise zero
    length commands with errors and let them drop through to the retry code.

    我相信从我从这个修复程序中了解到的错误是现在正在使用操作码为 0x85“ATA 命令通过（16）”和 0xa1“ATA 命令通过（12）/空白”的 ATA 直通命令（可能错误地）发出并因此导致这些错误消息。

    查看 ATA 直通命令数据，它看起来像是正在发出 SMART（自我监控、分析和报告技术）ATA 命令（命令代码 0xb0），我推测这个 H/W 可能无法处理这个。

    • 4

相关问题