3 Replies Latest reply on Mar 8, 2018 8:57 AM by sarikrizvi

    Failed: H:0x0 D:0x2 P:0x0 Valid sense data

    gr99 Novice

      On my ESXi 5.5 U3 servers, I'm seeing regular messages in /var/log/vmkernel about failed valid sense data:

       

      2017-02-23T14:08:16.307Z cpu2:34366)NMP: nmp_ThrottleLogForDevice:2458: Cmd 0x85 (0x412e86932dc0, 34608) to dev "naa.6c81f660d81ddf001a52e77d094d4447" on path "vmhba0:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

      2017-02-23T14:08:16.307Z cpu2:34366)ScsiDeviceIO: 2369: Cmd(0x412e86932dc0) 0x4d, CmdSN 0x105a from world 34608 to dev "naa.6c81f660d81ddf001a52e77d094d4447" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2017-02-23T14:08:16.307Z cpu2:34366)ScsiDeviceIO: 2369: Cmd(0x412e86932dc0) 0x1a, CmdSN 0x105b from world 34608 to dev "naa.6c81f660d81ddf001a52e77d094d4447" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.


      I thought this was due to the change in SCSI heartbeats (As per KB 2113956 ) I've applied the workaround:

       

      # esxcli system settings advanced set -i 0 -o /VMFS3/UseATSForHBOnVMFS5


      But I'm still seeing the errors. The disc is an onboard RAID card virtual drive:

       

      # esxcli storage nmp device list

      naa.6c81f660d81ddf001a52e77d094d4447

         Device Display Name: Local DELL Disk (naa.6c81f660d81ddf001a52e77d094d4447)

         Storage Array Type: VMW_SATP_LOCAL

         Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.

         Path Selection Policy: VMW_PSP_FIXED

         Path Selection Policy Device Config: {preferred=vmhba0:C2:T0:L0;current=vmhba0:C2:T0:L0}

         Path Selection Policy Device Custom Config:

         Working Paths: vmhba0:C2:T0:L0

         Is Local SAS Device: false

         Is USB: false

         Is Boot USB Device: false


      The hardware is a PowerEdge R720xd server with a PERC H710P Mini controller.

        • 1. Re: Failed: H:0x0 D:0x2 P:0x0 Valid sense data
          Hot Shot

          It looks like harmless log spew related to rescan of local devices. Do the alerts come at regular intervals? 5 minutes, or 30 minutes?

           

          Brief mention of this here: Filtering logs in VMware vSphere ESXi (2118562) | VMware KB

           

          Example:

           

          Some rescan commands for local storage devices will report a SCSI log expression in the vmkernel.log that can be safely filtered.

           

          Below is an example of the logfilters file including these expressions:

           

          0 | vmkernel | 0x1a.* H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x2[04] 0x0
          0 | vmkernel | 0x85.* H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0
          0 | vmkernel | 0x12.* H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0
          0 | vmkernel | 0x9e.* H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0
          0 | vmkernel | bad CDB .* scsi_op=0x9e
          0 | vmkernel | 0x4d.* H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0

          • 2. Re: Failed: H:0x0 D:0x2 P:0x0 Valid sense data
            RajeevVCP4 Hot Shot
            vExpert

            Here I am assuming vmhba0:C2:T0:L0 is your local/boot storage ,

             

            path "vmhba0:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

            2017-02-23T14:08:16.307Z cpu2:34366)ScsiDeviceIO: 2369: Cmd(0x412e86932dc0) 0x4d, CmdSN 0x105a from world 34608 to dev


            This is not errors but information returned from the SAN /LUNs

             


            Here is decoding of this code

             

            Host Status [0x0] OK This status is returned when there is no error on the host side. This is when you will see if there is a status for a Device or Plugin. It is also when you will see Valid sense data instead of Possible sense Data.

             

            Device Status [0x2] This status is returned when a command fails for a specific reason. When a CHECK CONDITION is received, the ESX storage stack will send out a SCSI command 0x3 (REQUEST SENSE) in order to get the SCSI sense data (Sense Key, Additional Sense Code, ASC Qualifier, and other bits). The sense data is listed after Valid sense data in the order of Sense Key, Additional Sense Code, and ASC Qualifier.

             

            Plugin Status [0x0] GOOD No error. (ESXi 5.x / 6.x only)

             

            Sense Key [0x5] ILLEGAL REQUEST

             

            Additional Sense Data 20/00 INVALID COMMAND OPERATION CODE

             

            For Cmd 0x4d scsi command 4d LOG SENSE (see https://en.wikipedia.org/wiki/SCSI_command )

             

             

             

            • 3. Re: Failed: H:0x0 D:0x2 P:0x0 Valid sense data
              sarikrizvi Enthusiast

              Check below KBs to understand SCSI Check Conditions in VMkernel logs

               

              VMware Knowledge Base

              VMware Knowledge Base

               

               

              TypeCodeNameDescription
              Host Status[0x0]OKThis status is returned when there is no error on the host side. This is when you will see if there is a status for a Device or Plugin. It is also when you will see Valid sense data instead of Possible sense Data.
              Device Status[0x2]CHECK_CONDITIONThis status is returned when a command fails for a specific reason. When a CHECK CONDITION is received, the ESX storage stack will send out a SCSI command 0x3 (REQUEST SENSE) in order to get the SCSI sense data (Sense Key, Additional Sense Code, ASC Qualifier, and other bits). The sense data is listed after Valid sense data in the order of Sense Key, Additional Sense Code, and ASC Qualifier.
              Plugin Status[0x0]GOODNo error. (ESXi 5.x / 6.x only)
              Sense Key[0x5]ILLEGAL REQUEST
              Additional Sense Data24/00INVALID FIELD IN CDB