VMware vSphere

 View Only
Back to discussions
Expand all | Collapse all

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

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

    Posted Apr 08, 2018 08:50 AM

    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



  • 2.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 08, 2018 10:41 AM

    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.



  • 3.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 08, 2018 02:38 PM

    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



  • 4.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 11, 2018 08:13 PM

    Anyone can help me?



  • 5.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 18, 2018 07:52 PM

    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



  • 6.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data
    Best Answer

    Posted Apr 19, 2018 12:25 PM

    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.

    _______________________________________________________________________________________________________

    Did you find this helpful? Let us know by completing this survey (takes 1 minute!)



  • 7.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 11, 2023 07:59 PM

    could be the smartd that is being issued by ESX is not a valid command on our storage.  There are several articles on the web about this.  Solution would be to turn off the smartd checks that the host cannot honor, as it is not supported.



  • 8.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Apr 19, 2018 12:30 PM

    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.



  • 9.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Oct 02, 2018 12:02 PM

    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



  • 10.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Oct 02, 2018 01:22 PM

    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



  • 11.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Mar 29, 2022 11:14 AM
      |   view attached

    Did you find a way to stop this? I have 2 x Dell R820....  and have the same problem with both servers. 

    The server running on 6.5.0 (build number : 4564106) actually crashes every now and again with the pink screen (attached please find) 

    The server running on 6.7.0 (build number : 17167734) also has these logs but so far has not crashed:-

    2022-03-29T02:09:56.040Z cpu22:2098187)DVFilter: 6053: Checking disconnected filters for timeouts
    2022-03-29T02:10:20.674Z cpu73:2098237)ScsiDeviceIO: 3469: Cmd(0x45ca893a7940) 0x1a, CmdSN 0x11aadda from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:13:42.677Z cpu5:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bff40c0) 0x1a, CmdSN 0x11aae3e from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:16:25.675Z cpu0:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8be9a940) 0x1a, CmdSN 0x11aaea4 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:19:28.816Z cpu18:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bfa9840) 0x1a, CmdSN 0x11aaf08 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:19:56.041Z cpu24:2098187)DVFilter: 6053: Checking disconnected filters for timeouts
    2022-03-29T02:21:55.516Z cpu17:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bedfb80) 0x1a, CmdSN 0x11aaf6e from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:24:48.082Z cpu0:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bf42dc0) 0x1a, CmdSN 0x11aafd2 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:28:04.425Z cpu60:2098237)ScsiDeviceIO: 3469: Cmd(0x45ca9057d680) 0x1a, CmdSN 0x11ab038 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:29:56.041Z cpu24:2098187)DVFilter: 6053: Checking disconnected filters for timeouts
    2022-03-29T02:30:01.483Z cpu72:2098237)ScsiDeviceIO: 3469: Cmd(0x45ca89382140) 0x1a, CmdSN 0x11ab09e from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:33:34.177Z cpu13:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bec2a80) 0x1a, CmdSN 0x11ab102 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:35:20.579Z cpu58:2098236)ScsiDeviceIO: 3469: Cmd(0x45ba82cfad80) 0x1a, CmdSN 0x11ab168 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:38:23.423Z cpu65:2098237)ScsiDeviceIO: 3469: Cmd(0x45ca8932ea40) 0x85, CmdSN 0x14062 from world 2100523 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
    2022-03-29T02:39:56.042Z cpu24:2098187)DVFilter: 6053: Checking disconnected filters for timeouts
    2022-03-29T02:40:12.193Z cpu39:2098235)ScsiDeviceIO: 3469: Cmd(0x45aa8cdc2480) 0x1a, CmdSN 0x11ab219 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:43:34.244Z cpu7:2098234)ScsiDeviceIO: 3469: Cmd(0x459a8bf50b00) 0x1a, CmdSN 0x11ab27d from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
    2022-03-29T02:45:20.653Z cpu44:2098236)ScsiDeviceIO: 3469: Cmd(0x45ba82c7db00) 0x1a, CmdSN 0x11ab2e3 from world 0 to dev "naa.644a84200b4d370027b29af92fecb97c" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

    Did you find a way to stop ESXi from doing the scans?



  • 12.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Aug 17, 2020 10:29 AM

    I get the same as TakeN3

    2020-08-17T01:49:15.677Z cpu108:65805)ScsiDeviceIO: 3015: Cmd(0x439e4341dfc0) 0xfe, CmdSN 0xbbc2e5 from world 65687 to dev "naa.60060160e8004b00e2ca985c1400127d" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

    2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e4368a5c0, 65687) to dev "naa.60060160e8004b007e9d9a5cf732ff8e" on path "vmhba2:C0:T11:L47" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43720dc0) 0xfe, CmdSN 0x719b30 from world 65687 to dev "naa.60060160e8004b007e9d9a5cf732ff8e" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

    2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435e02c0, 65687) to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" on path "vmhba3:C0:T10:L102" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43502940) 0xfe, CmdSN 0x382ef0 from world 65687 to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

    2020-08-17T01:49:15.877Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435079c0, 65687) to dev "naa.60060160e8004b00de1a995cd70e3c6a" on path "vmhba3:C0:T12:L30" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

    I get these on every LUN that was mapped to this ESX070 host

    dev "naa.6006" is DELL EMC Storage, in my case Dell EMC Unity 650f running OE 4.5.1 (UWDC01) & OE 5.0.3 (UWDC02)

    Current Dell EMC Unity Target code is OE 5.0.3

    [root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160de004b005f5d2a5fbbcad438"

    naa.60060160de004b005f5d2a5fbbcad438:1                                     /vmfs/devices/disks/naa.60060160de004b005f5d2a5fbbcad438:1                                     5f2a5df1-f99059c6-eed8-20040ff4978e  0  UWDC01_IT-PROD-WDC_V005

    [root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160e8004b00e595255ec02cf074"

    naa.60060160e8004b00e595255ec02cf074:1                                     /vmfs/devices/disks/naa.60060160e8004b00e595255ec02cf074:1                                     5e2596ab-2bec8188-f141-20040ff4978e  0  UWDC02_IT-PROD-WDC_V103

    [root@esx070:~] vmkchdev -l | grep vmhba

    0000:00:11.5 8086:a1d2 1734:1230 vmkernel vmhba0

    0000:00:17.0 8086:a182 1734:1230 vmkernel vmhba1

    0000:17:00.0 1077:2261 1077:029b vmkernel vmhba2 ----------------> FC HBA

    0000:6d:00.0 1077:2261 1077:029b vmkernel vmhba3 ----------------> FC HBA

    [root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d

    Dumping all key-value instance names:

    Key Value Instance:  vmhba3/qlogic

    Key Value Instance:  vmhba2/qlogic

    Key Value Instance:  vmhba1/vmw_ahci

    Key Value Instance:  vmhba0/vmw_ahci

    Key Value Instance:  MOD_PARM/qlogic

    [root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -l -i vmhba2/qlogic
    Listing keys:
    Name:   ADAPTER
    Type:   string
    value:
    QLogic 16Gb 1-port FC to PCIe Gen3 x8 Adapter for QLE2690:
            FC Firmware Version: 8.05.61 (d0d5), Driver version 2.1.73.0

    Host Device Name vmhba2

    BIOS version 3.61
    FCODE version 4.11
    EFI version 6.11
    Flash FW version 8.05.61
    ISP: ISP2261, Serial# RFD1722T35676
    MSI-X enabled
    Request Queue = 0x4309f6548000, Response Queue = 0x4309f6569000
    Request Queue count = 2048, Response Queue count = 512
    Number of response queues for CPU affinity operation: 4
    CPU Affinity mode enabled
    Total number of MSI-X interrupts on vector 0 (handler = 23) = 26676
    Total number of MSI-X interrupts on vector 1 (handler = 24) = 2186
    Total number of MSI-X interrupts on vector 2 (handler = 25) = 1090148738
    Total number of MSI-X interrupts on vector 3 (handler = 26) = 583007145
    Total number of MSI-X interrupts on vector 4 (handler = 27) = 2055128386
    Total number of MSI-X interrupts on vector 5 (handler = 28) = 1406005796
    Device queue depth = 0x8
    Number of free request entries = 1271
    FAWWN support: disabled
    FEC support: Disabled
    Total number of outstanding commands: 0
    Number of mailbox timeouts = 0
    Number of ISP aborts = 0
    Number of loop resyncs = 29
    Host adapter:Loop State = [READY], flags = 0x20ae200
    Link speed = [16 Gbps]

    Dpc flags = 0x0
    Link down Timeout =  010
    Port down retry =  010
    Login retry count =  010
    Execution throttle = 2048
    ZIO mode = 0x6, ZIO timer = 1
    Commands retried with dropped frame(s) = 297

    Product ID = 4953 5020 2261 0001

    NPIV Supported : Yes
    Max Virtual Ports = 254

    SCSI Device Information:
    scsi-qla0-adapter-node=20000024ff149042:160a00:0;
    scsi-qla0-adapter-port=21000024ff149042:160a00:0;

    Name:   TARGET
    Type:   string
    value:
    Driver version 2.1.73.0

    Host Device Name vmhba2

    FC Target-Port List:
    scsi-qla0-target-0=500000e0da81df29:122300:0:Online;
    scsi-qla0-target-1=500000e0da81df39:142300:1:Online;
    scsi-qla0-target-2=5006016249e4121e:140000:2:Online;
    scsi-qla0-target-3=5006016349e0121e:120000:3:Online;
    scsi-qla0-target-4=5006016849e4121e:140100:4:Online;
    scsi-qla0-target-5=5006016a49e4121e:120200:5:Online;
    scsi-qla0-target-6=5006016249e415ff:0e0000:6:Online;
    scsi-qla0-target-7=5006016349e015ff:100000:7:Online;
    scsi-qla0-target-8=5006016849e415ff:100100:8:Online;
    scsi-qla0-target-9=5006016a49e415ff:0e0100:9:Online;
    scsi-qla0-target-10=5006016249e41688:0e0500:a:Online;
    scsi-qla0-target-11=5006016349e01688:100200:b:Online;
    scsi-qla0-target-12=5006016849e41688:100300:c:Online;
    scsi-qla0-target-13=5006016a49e41688:0e0300:d:Online;

    Name:   NPIV
    Type:   string
    value:
    Driver version 2.1.73.0

    Host Device Name vmhba2

    NPIV Supported : Yes

    Looking at the Qlogic Site (Marvell Nowadays) and looing for the QL2690, we are at version -1 compared to the latest

    QLogic / Marvell Driver Download

    README

                       Read1st for Cavium Flash Image Package

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

                       **** ONLY FOR 268x/269x/27xx Series Adapters ****

    1. Contents Of Flash Package

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

    The files contained in this Flash image package are zipped into a file that

    will expand to provide the following versions for the 268x/269x/276x Series Adapters.

    *  Flash Image Version 01.01.91

       BK010191.BIN contains:

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

         Bootcode FC

           FC BIOS       v3.62

           FC FCode      v4.11  (Initiator)

           FC FCode      v4.10  (Target)

           FC EFI        v7.00  (Signed)

         FC Firmware   v8.08.231

         MPI Firmware  v1.00.19

         PEP Firmware(Quad-port)        v1.0.27

         PEP Firmware(Single/Dual port) v2.0.12

         PEP SoftROM(Quad port)         v1.0.16

         PEP SoftROM(Single/Dual port)  v2.0.11

         EFlash tool  v1.18

    (...)



  • 13.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Mar 07, 2022 02:02 PM

    Follow these steps to fix the Error 0x0 0x0:

    1. Go through the computer repair app on your Windows PC.
    2. Make sure your computer repair application is installed properly.
    3. For finding out the issue, click Scan Now.
    4. Once the device has been scanned, click the ‘Fix All’ option. This should fix the 0x0 0x0 issue.

    For further details you can contact us here https://communities.vmware.com/t5/ESXi-Discussions/Failed-H-0x0-0x0-D-0x2-P-0x0-Valid-sense-data/td-p/464412.



  • 14.  RE: Failed H:0x0 D:0x2 P:0x0 Valid sense data

    Posted Jul 25, 2024 06:19 AM

    I ended up upgrading to ESXi 6.7 (U3) A19 and so far no crashes (touch wood)

    Malcolm 

    https://www.hodfords.com/


    Original Message