Skip to main content
NetApp Knowledge Base

VMware ESXi 6.5 hosts reporting Invalid Sense Data during Straight IO

  1. Last updated
  2. Save as PDF
Views:
2,629
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

​ ​

Applies to

  • NetApp E-Series Storage Array
  • VMware ESXi 6.5

Issue

On a VMware ESXi 6.5 GA host or VMware ESXi 6.5.0 build-4449886, the vmkernel.log available at /var/log/ (or /scratch/log/) might report several lines that include "Invalid Sense Data", reported by ScsiDeviceIO. These lines will include SCSI ASC/ASCQ assignments that truly are invalid, in that they are not listed in the Technical Committee T10 specifications for SCSI Storage Interfaces. They are also not characterized as NetApp E-Series vendor-specific ASC/ASCQ assignments.

Example:
2016-10-12T15:27:00.905Z cpu28:267900)ScsiDeviceIO: 2927: Cmd(0x439d07881d80) 0x28, CmdSN 0x80000002 from world 267686 to dev "naa.60080e50004354280000e829573b45aa" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x3 0x43 0x0

Sense Key - 0x3
ASC - 0x43
ASCQ - 0x0

In this example, the Sense Key of "0x3" suggests that a medium error exists. However, the ASC of "0x43" is not defined in the T10 specifications.

NetApp E-Series Storage Arrays are not reporting such sense data, and the host appears to be fabricating it.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.