From: "Mantas Mikulėnas" <grawity@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: Maxtor USB disk – "UNKNOWN(0x2003) Result" messages logged
Date: Mon, 24 Oct 2016 09:08:42 +0300 [thread overview]
Message-ID: <CAPWNY8UvHmmwAs9t3etm_+0hnjii19a0MteaR1rWp36d4n9yxg@mail.gmail.com> (raw)
Apologies if I'm posting to the wrong place; this is where I was
pointed to the last time I had USB storage questions.
I have a Maxtor (Seagate) "D3 Station" USB 3.0 SATA disk (0bc2:6125).
While it appears to work completely fine, every now and then the
following are logged in dmesg:
[Oct20 01:00] sd 3:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result:
hostbyte=0x07 driverbyte=0x08
[ +0.000004] sd 3:0:0:0: [sdb] tag#0 Sense Key : 0x4 [current] [descriptor]
[ +0.000003] sd 3:0:0:0: [sdb] tag#0 ASC=0x0 ASCQ=0x0
[ +0.000003] sd 3:0:0:0: [sdb] tag#0 CDB: opcode=0x85 85 06 20 00 00
00 00 00 00 00 00 00 00 00 e5 00
[ +0.137088] sd 3:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result:
hostbyte=0x07 driverbyte=0x08
[ +0.000003] sd 3:0:0:0: [sdb] tag#0 Sense Key : 0x4 [current] [descriptor]
[ +0.000002] sd 3:0:0:0: [sdb] tag#0 ASC=0x0 ASCQ=0x0
[ +0.000002] sd 3:0:0:0: [sdb] tag#0 CDB: opcode=0xa1 a1 06 20 da 00
00 4f c2 00 b0 00 00
When using smartctl (--health --device=sat), a similar message is also logged:
[Oct20 01:09] sd 3:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result:
hostbyte=0x07 driverbyte=0x08
[ +0.000004] sd 3:0:0:0: [sdb] tag#0 Sense Key : 0x4 [current] [descriptor]
[ +0.000001] sd 3:0:0:0: [sdb] tag#0 ASC=0x0 ASCQ=0x0
[ +0.000003] sd 3:0:0:0: [sdb] tag#0 CDB: opcode=0x85 85 06 2c 00 da
00 00 00 00 00 4f 00 c2 00 b0 00
Are those the sign of a hardware problem or a kernel bug? (I'm running
4.8.2 at the moment.)
--
Mantas Mikulėnas <grawity@gmail.com>
reply other threads:[~2016-10-24 6:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPWNY8UvHmmwAs9t3etm_+0hnjii19a0MteaR1rWp36d4n9yxg@mail.gmail.com \
--to=grawity@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.