Running ESXI 5.5 update 3
Seeing the below errors on my hosts and all of them are device id's for RDM's I am using on guests.
2015-11-23T17:36:30.579Z cpu17:48347)ScsiDeviceIO: 2363: Cmd(0x413682ced180) 0x4d, CmdSN 0x4ab from world 34739 to dev "naa.600508b1001cdd033b8ac13cd09915ee" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2015-11-23T18:06:30.678Z cpu26:34739)Partition: 644: Read from primary gpt table failed on "naa.600508b1001cdd033b8ac13cd09915ee".
2015-11-23T18:06:30.678Z cpu28:48270)NMP: nmp_ThrottleLogForDevice:2349: Cmd 0x85 (0x4136856e6440, 34739) to dev "naa.600508b1001cdd033b8ac13cd09915ee" on path "vmhba0:C0:T0:L2" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
2015-11-23T18:06:30.678Z cpu28:48270)ScsiDeviceIO: 2363: Cmd(0x4136856e6440) 0x4d, CmdSN 0x4b4 from world 34739 to dev "naa.600508b1001cdd033b8ac13cd09915ee" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
I found this article on repairing the GPT in the event of finding this error but it is very specific that you don't do this on RDM disks.
I assume this is because the GPT is being handled by the guest OS.
Any idea if this is just expected behavior in the logs for esxi servers with RDM's and I should just disregard them? The only reason to the contrary I have in my mind is that one of my hosts doesn't exhibit this behavior in its logs.