8 Replies Latest reply on Oct 2, 2018 6:22 AM by Finikiez

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

    TaKeN3 Novice

      Hello guys,

      I just install a fresh ESXi 6.0 on my new server but in dmesg i got spam like this:

       

      2018-04-07T11:57:07.608Z cpu5:33150)ScsiDeviceIO: 2636: Cmd(0x43b5c0870240) 0x85, CmdSN 0x103 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T12:27:07.626Z cpu4:32916)ScsiDeviceIO: 2636: Cmd(0x43b5c08528c0) 0x4d, CmdSN 0x10d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T12:52:21.148Z cpu1:34192)ScsiDeviceIO: 2636: Cmd(0x43b5c088bfc0) 0x1a, CmdSN 0x110e from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T13:27:07.657Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c08daec0) 0x85, CmdSN 0x11b from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T13:57:07.681Z cpu5:33288)ScsiDeviceIO: 2636: Cmd(0x43b5c083bfc0) 0x1a, CmdSN 0x11c4 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T14:22:22.030Z cpu6:33480)ScsiDeviceIO: 2636: Cmd(0x43b5c0850340) 0x1a, CmdSN 0x11fd from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T15:01:01.192Z cpu3:32916)ScsiDeviceIO: 2636: Cmd(0x43b5c084d740) 0x1a, CmdSN 0x126c from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T15:57:07.741Z cpu7:33044)ScsiDeviceIO: 2636: Cmd(0x43b5c085a740) 0x85, CmdSN 0x140 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T15:57:07.748Z cpu7:32863)ScsiDeviceIO: 2636: Cmd(0x43b5c085a740) 0x1a, CmdSN 0x12f5 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T16:32:23.323Z cpu7:32785)ScsiDeviceIO: 2636: Cmd(0x43b5c0846e80) 0x1a, CmdSN 0x135e from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T17:27:07.802Z cpu1:32867)ScsiDeviceIO: 2636: Cmd(0x43b5c0835900) 0x85, CmdSN 0x158 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T17:27:07.816Z cpu1:32836)ScsiDeviceIO: 2636: Cmd(0x43b5c0835900) 0x4d, CmdSN 0x15d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T18:02:24.194Z cpu5:33226)ScsiDeviceIO: 2636: Cmd(0x43b5c07bddc0) 0x1a, CmdSN 0x144d from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T18:57:07.865Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bbcc0) 0x1a, CmdSN 0x172 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T18:57:07.875Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bbcc0) 0x1a, CmdSN 0x14d0 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T19:42:25.184Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bac40) 0x1a, CmdSN 0x1542 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T20:27:07.943Z cpu3:33044)ScsiDeviceIO: 2636: Cmd(0x43b5c08d0e00) 0x1a, CmdSN 0x18a from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T20:57:07.961Z cpu3:33143)ScsiDeviceIO: 2636: Cmd(0x43b5c07e25c0) 0x1a, CmdSN 0x1601 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T21:12:26.060Z cpu2:33290)ScsiDeviceIO: 2636: Cmd(0x43b5c083d940) 0x1a, CmdSN 0x1631 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T21:57:07.984Z cpu7:32836)ScsiDeviceIO: 2636: Cmd(0x43b5c07c2b00) 0x85, CmdSN 0x1a3 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T22:27:08.004Z cpu7:32803)ScsiDeviceIO: 2636: Cmd(0x43b5c08709c0) 0x4d, CmdSN 0x1ad from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T22:52:27.109Z cpu3:32771)ScsiDeviceIO: 2636: Cmd(0x43b5c0883880) 0x1a, CmdSN 0x1726 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-07T23:27:08.027Z cpu5:33733)ScsiDeviceIO: 2636: Cmd(0x43b5c0892e00) 0x85, CmdSN 0x1bb from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-07T23:57:08.072Z cpu5:32838)ScsiDeviceIO: 2636: Cmd(0x43b5c0880100) 0x1a, CmdSN 0x17dc from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T00:22:28.016Z cpu2:33226)ScsiDeviceIO: 2636: Cmd(0x43b5c080a1c0) 0x1a, CmdSN 0x1815 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T01:01:01.761Z cpu7:33454)ScsiDeviceIO: 2636: Cmd(0x43b5c085c6c0) 0x1a, CmdSN 0x1884 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T01:57:08.157Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c07f3b80) 0x85, CmdSN 0x1e0 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-08T01:57:08.173Z cpu6:33275)ScsiDeviceIO: 2636: Cmd(0x43b5c07f3b80) 0x1a, CmdSN 0x190d from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T02:32:29.338Z cpu1:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c0845680) 0x1a, CmdSN 0x1976 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T03:27:08.211Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0894000) 0x85, CmdSN 0x1f8 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-08T03:27:08.213Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0894000) 0x4d, CmdSN 0x1fd from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-08T04:02:30.247Z cpu3:34200)ScsiDeviceIO: 2636: Cmd(0x43b5c0814a40) 0x1a, CmdSN 0x1a65 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T04:57:08.264Z cpu7:33043)ScsiDeviceIO: 2636: Cmd(0x43b5c08516c0) 0x1a, CmdSN 0x212 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T04:57:08.280Z cpu7:33043)ScsiDeviceIO: 2636: Cmd(0x43b5c08516c0) 0x1a, CmdSN 0x1ae8 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T05:42:31.261Z cpu3:33164)ScsiDeviceIO: 2636: Cmd(0x43b5c08be9c0) 0x1a, CmdSN 0x1b5a from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T06:27:08.391Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0802b00) 0x1a, CmdSN 0x22a from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T06:57:08.407Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c081a800) 0x1a, CmdSN 0x1c19 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T07:12:32.127Z cpu2:33276)ScsiDeviceIO: 2636: Cmd(0x43b5c07eb200) 0x1a, CmdSN 0x1c49 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

      2018-04-08T07:57:08.442Z cpu7:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08581c0) 0x85, CmdSN 0x243 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-08T08:27:08.472Z cpu3:32863)ScsiDeviceIO: 2636: Cmd(0x43b5c0898640) 0x4d, CmdSN 0x24d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

      2018-04-08T08:30:20.129Z cpu7:32984)ScsiDeviceIO: 2636: Cmd(0x43b5c0858640) 0x1a, CmdSN 0x1d2f from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

       

      This is a server with 2x SSD and 2x HDD i create 2x RAID1 from this all 4 devices.

       

      [root@esx03:~] lspci |grep -i raid

      0000:06:00.0 Mass storage controller: Avago (LSI / Symbios Logic) MegaRAID SAS Fusion Controller [vmhba1]

       

      Anyone can tell me what`s that mean and how to disable this spam in dmesg?

       

      Best Regards

      TaKeN

        • 1. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
          RvdNieuwendijk Virtuoso
          User ModeratorsvExpert

          VMware Knowledge Base article Interpreting SCSI sense codes in VMware ESXi and ESX (289902) explains how you can decode the SCSI sense codes in the error messages. To decode the SCSI Sense Keys, you can use the table on http://www.t10.org/lists/2sensekey.htm. To decode the combination of the Aditional Sense Code and Additional Sense Code Qualifier, you can use the information on http://www.t10.org/lists/asc-num.txt.

           

          The following part of the Knowledge Base article tells you what every part of the codes relate to:

          H:0xA D:0xB P:0xC Possible sense data: 0xD 0xE 0xF

          A = Host status (Initiator)

          B = Device Status (Target)

          C = Plugin (VMware Specific)

          D = Sense Key

          E = Additional Sense Code

          F = Additional Sense Code Qualifier

           

          In your case, you get the following SCSI sense codes:

          H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0, and H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

           

          These code translate to the following:

          Host Status: H:0x0 NO error

          Device Status: D:0x2 CHECK CONDITION

          Plugin Error code: P:0x0 No error

          Sense Key: 0x5 ILLEGAL REQUEST

          Aditional Sense Code: 0x20 and Additional Sense Code Qualifier: 0x0 INVALID COMMAND OPERATION CODE

          Additional Sense Code: 0x24 and Additional Sense Code Qualifier: 0x0 INVALID FIELD IN CDB

           

          The device status is CHECK CONDITION. In this case, the sense codes contain the information necessary to understand why the command has failed. It seems there is an ILLEGAL REQUEST SCSI request made with an INVALID COMMAND OPERATION CODE and an INVALID FIELD IN CDB.

          • 2. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
            TaKeN3 Novice

            Thank You for answer, so how to disable this spam?

            Like You see in 1 hour i got many many of them...

            There is any way to repair this problem or disable invalid command or update VIB for this controler?

             

            2. I just saw new spam in dmesg too:

            2018-04-07T05:01:03.184Z cpu4:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:01:19.147Z cpu2:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:01:35.148Z cpu4:33112)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:01:35.302Z cpu2:33117)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:01:51.182Z cpu1:33117)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:02:07.229Z cpu1:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:02:23.038Z cpu1:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:02:38.903Z cpu1:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:03:10.347Z cpu1:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:03:10.668Z cpu3:33108)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:03:26.146Z cpu3:33108)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:03:41.793Z cpu1:33117)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:03:57.675Z cpu1:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:04:29.112Z cpu7:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:04:44.858Z cpu7:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:04:46.373Z cpu7:33109)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:05:00.683Z cpu5:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:05:32.071Z cpu7:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:05:47.769Z cpu4:33112)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:06:19.114Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:06:22.822Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:06:34.906Z cpu4:33112)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:06:50.663Z cpu7:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:07:22.145Z cpu0:33122)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:07:37.907Z cpu0:33122)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:07:53.699Z cpu0:33122)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:07:59.612Z cpu5:33107)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:08:25.225Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:08:40.903Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:08:56.839Z cpu0:33122)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:09:28.316Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:09:36.212Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:09:43.984Z cpu3:33116)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:09:59.728Z cpu5:33111)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:10:31.091Z cpu6:33120)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:10:46.797Z cpu3:33115)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:11:14.234Z cpu4:33114)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:11:18.209Z cpu3:33115)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:11:33.936Z cpu4:33114)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:11:50.017Z cpu6:33120)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:12:06.933Z cpu6:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:12:22.803Z cpu5:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:12:38.693Z cpu0:33117)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:12:52.424Z cpu4:33114)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:13:09.023Z cpu2:33111)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:13:35.822Z cpu0:33121)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:14:02.843Z cpu5:33118)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:14:29.621Z cpu5:33113)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:14:30.522Z cpu4:33107)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:14:56.500Z cpu5:33122)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:15:23.223Z cpu5:33114)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:15:50.130Z cpu5:33118)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:16:08.853Z cpu3:33119)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:16:16.925Z cpu5:33108)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:16:43.801Z cpu0:33112)<6>megasas_hotplug_work[0]: event code 0x0041

            2018-04-07T05:17:10.648Z cpu2:33111)<6>megasas_hotplug_work[0]: event code 0x0041

             

            This is exacly this controler:

            [root@esx03:~] esxcli storage core adapter list

            HBA Name  Driver        Link State  UID             Capabilities  Description

            --------  ------------  ----------  --------------  ------------  -------------------------------------------------------------------------

            vmhba1    megaraid_sas  link-n/a    unknown.vmhba1                (0000:06:00.0) Avago (LSI / Symbios Logic) MegaRAID SAS Fusion Controller

             

            This is a status:

            [root@esx03:~] esxcli storage core device vaai status get

            naa.600605b00cd0cf6022439b052a3716ef

               VAAI Plugin Name:

               ATS Status: unsupported

               Clone Status: unsupported

               Zero Status: unsupported

               Delete Status: unsupported

             

             

            naa.600605b00cd0cf6022439b0b2a9c2622

               VAAI Plugin Name:

               ATS Status: unsupported

               Clone Status: unsupported

               Zero Status: unsupported

               Delete Status: unsupported

             

            Best Regards

            TaKeN

            • 3. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
              TaKeN3 Novice

              Anyone can help me?

              • 4. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
                TaKeN3 Novice

                Still i don`t get back any help.

                Someone can help me with this problem? Or i just need to ignore all:

                failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0

                and

                failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

                 

                 

                Best Regards

                TaKeN

                • 5. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
                  Finikiez Master
                  vExpert

                  According to posted errors failed comands are

                  0x1a - MODE SENSE (6)

                  and

                  0x85 - ATA PASS-THROUGH(16)

                   

                  Sence code is

                  H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

                   

                  0x5 0x24 means - ILLEGAL REQUEST plus INVALID FIELD IN CDB

                   

                  Generally speaking it means that local disk controller doesn't understand these. And that's ok to local disk controllers.

                   

                  Just ignore them.

                  • 6. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
                    Finikiez Master
                    vExpert

                    As well you can filter these logs in vmkernel using instructions from KB article https://kb.vmware.com/s/article/2118562

                     

                    Just do it carefully.

                    • 7. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
                      itsk201110141 Lurker

                      Dear Finikiez,

                      I just figured out to have the very same error messages filling up my log as TaKeN3 reportet.

                      Same controller though and also a newly installed VMware ESXi 6.7.

                      For me, it seems as if ESXi regularly checks the controller and/or Disks for certain information which the controller (I have the same one installed as TaKeN3) does not understand.

                      Therefore - I would rather stop (or alter) this querying than to filter the log.

                      Is there any possiblity to do so?

                      Kind regards,

                      Stefan

                      • 8. Re: Failed H:0x0 D:0x2 P:0x0 Valid sense data
                        Finikiez Master
                        vExpert

                        Hello!

                         

                        As mentioned earlier you can filter out annoying messages so they won't appear in vmkernel.log

                        Have a look into the following article with instructions VMware Knowledge Base