I have also noticed these errors in our HP environment as well. In regards to the sense data error, it appears that they may be due to a device (CD/DVD) that does not support rescan. Check out this KB, which says the messages are normal and can be ignored. Additionally, when researching this issue I also found this ESXi SCSI Sense Code Decoder that may be helpful. In regards to the failed hp-ilo file open, I have yet to find the cause of a possible lock.
2017-03-19T16:51:13.325Z cpu45:66167)nhpsa: hpsa_vmkScsiCmdDone:5238: Sense data: error code: 0x70, key: 0x5, info:00 00 00 00 , cmdInfo:00 00 00 00 , CmdSN: 0x741, worldId: 0x109ea, Cmd: 0x85, ASC: 0x20, ASCQ: 0x0
you can translate it to below form
Valid sense data : 0x5 0x20 0x0
This message is generated because your disk or device does not support 0x85 command. 0x85 is ATA PASS-THROUGH(16)
you can safely ignore it.
0x20/0x0is Invalid Command Operation Code
0x24/0x0is Invalid Field in CDB (Command Descriptor Block)
This is not necessarily a problem. Some devices do not and cannot provide the requested information
If the storage device is otherwise working correctly, the log messages can be ignored.
were experiencing the exact same issue...
2017-08-31T09:16:17.372Z cpu31:68164)FSS: 6766: Failed to open file 'hpilo-d0ccb0'; Requested flags 0x5, world: 68164 [sfcb-smx], (Existing flags 0x0, world: 0 [unknown]): Busy
2017-08-31T09:16:17.385Z cpu21:68164)ilo : Open could not dequeue a packet
2017-08-31T09:16:17.385Z cpu21:68164)FSS: 6766: Failed to open file 'hpilo-d0ccb1'; Requested flags 0x5, world: 68164 [sfcb-smx], (Existing flags 0x0, world: 0 [unknown]): Busy
2017-08-31T09:16:17.399Z cpu31:68164)ilo : Open could not dequeue a packet
2017-08-31T09:16:17.400Z cpu31:68164)FSS: 6766: Failed to open file 'hpilo-d0ccb2'; Requested flags 0x5, world: 68164 [sfcb-smx], (Existing flags 0x0, world: 0 [unknown]): Busy
ive opened a support request with vmware but so far havent been able to resolve the issue.
we are running the custom HPE iso for 6.5u1
vmware suggested to install the latest AMS bundle pack... so you can try this, but it did not resolve our issue.
vmware pointed me to this as well.. but this doesnt resolve the issue either. the article is for esxi 5.x but they said it relates to 6.5 as well
also updating ilo to the latest version did not fix the issue.
my request with vmware is on going.
I was just wondering if you were ever able to resolve this issue? We are also seeing this in our environment as we upgrade to the Custom HP ESXi 6.5U1.
Same issue here, we are running ESXi 6.5 U1 with the latest HPE Agents and every host is logging the event between 20 and 60 times per 24 hours. According to HPE, these log entries can be ignored: HPE Support document - HPE Support Center
Do we have any update on the issue mentioned here?
If I decode the sense data in below error
nhpsa: hpsa_vmkScsiCmdDone:5239: Sense data: error code: 0x70, key: 0x5, info:00 00 00 00
I get this
LOGICAL UNIT DOES NOT RESPOND TO SELECTION
We're seeing the same log entries on an ESXi 6.7 host, using the HP custom ESXi image.