Lately in the logfile vmkernel.log of my ESXi 6.5 shows these messages:
[continue...]
2017-06-04T17:51:14.446Z cpu4:66132)ScsiDeviceIO: 2948: Cmd(0x4395008a4f80) 0x85, CmdSN 0x1117 from world 67312 to dev "naa.600304801a8bae002083d2ab7949221e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-06-04T18:51:14.504Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395008d2080) 0x4d, CmdSN 0x1121 from world 67312 to dev "naa.600304801a8bae002083d2e57cbe129b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-06-04T19:21:14.539Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395008c2480) 0x1a, CmdSN 0x112e from world 67312 to dev "naa.600304801a8bae002083d2ab7949221e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-06-04T20:21:14.597Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395008cc580) 0x1a, CmdSN 0x8e80 from world 0 to dev "naa.600304801a8bae002083d2e57cbe129b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-06-04T20:51:14.629Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x43950084b800) 0x1a, CmdSN 0x1146 from world 67312 to dev "naa.600304801a8bae002083d2ab7949221e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-06-04T22:21:14.722Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395009c0780) 0x1a, CmdSN 0x8ee9 from world 0 to dev "naa.600304801a8bae002083d2e57cbe129b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2017-06-04T22:21:14.725Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395009c0780) 0x85, CmdSN 0x115c from world 67312 to dev "naa.600304801a8bae002083d2ab7949221e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-06-04T23:51:14.821Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395009e5000) 0x4d, CmdSN 0x1171 from world 67312 to dev "naa.600304801a8bae002083d2e57cbe129b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2017-06-04T23:51:14.824Z cpu0:66132)ScsiDeviceIO: 2948: Cmd(0x4395009e5000) 0x85, CmdSN 0x1174 from world 67312 to dev "naa.600304801a8bae002083d2ab7949221e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
[continue...]
All day each hour at the same time show a messages.
[root@addcom-vmware01:/vmfs/volumes] esxcli storage nmp device list -d naa.600304801a8bae002083d2ab7949221e
naa.600304801a8bae002083d2ab7949221e
Device Display Name: Local LSI Disk (naa.600304801a8bae002083d2ab7949221e)
Storage Array Type: VMW_SATP_LOCAL
Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba1:C2:T0:L0;current=vmhba1:C2:T0:L0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba1:C2:T0:L0
Is USB: false
[root@addcom-vmware01:/vmfs/volumes] esxcli storage nmp device list -d naa.600304801a8bae002083d2e57cbe129b
naa.600304801a8bae002083d2e57cbe129b
Device Display Name: Local LSI Disk (naa.600304801a8bae002083d2e57cbe129b)
Storage Array Type: VMW_SATP_LOCAL
Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba1:C2:T1:L0;current=vmhba1:C2:T1:L0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba1:C2:T1:L0
Is USB: false
I have read that these messages are information but if it's all day...
The hardware is a Supermicro Server with a MegaRAID SAIS Controller(lsi_mr3)
I'm worried about this issue.
