Hi,
Hi,
you can use this tool to decode what bothers you in vmkernel.log.
It doesn't look dangerous but annoying for sure. You can consult this vmkernel record with storage vendor's support organization.
Just to add to what vmrale said, it is important to correlate which is the "faulty" device, you can see it with the naa.id just before the scsi sense error code.