In vmkernel.log file the ScisDeviceIO errors we are getting
reported every 30 minutes:
CPUxx:32857)NMP: nmp_ThrottleLogForDevice:2331 Cmd 0x85
(0x412fc2d41c40, 34430) to dev "naa.xxxxxxxxxxxxxxxxx4a4" on path
"vmhba0:C2:T1:L0" Failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20
0x0. Act:None
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x85,
CmdSN 0x2ba4 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx4a4"
failed H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x4d,
CmdSN 0x2ba5 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx4a4"
failed H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x1a,
CmdSN 0x2ba6 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx4a4" failed
H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
CPUxx:32857)NMP: nmp_ThrottleLogForDevice:2331 Cmd 0x85
(0x412fc2d41c40, 34430) to dev "naa.xxxxxxxxxxxxxxxxx21a" on path
"vmhba0:C2:T0:L0" Failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20
0x0. Act:None
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x85,
CmdSN 0x2ba7 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx21a"
failed H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x4d,
CmdSN 0x2ba8 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx21a"
failed H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
CPUxx : 32800)ScsiDeviceIO: 2337: Cmd(0x412fc2d41c40) 0x1a,
CmdSN 0x2ba9 from world 34430 to dev "naa.xxxxxxxxxxxxxxxxx21a"
failed H:0x0 D:0x2 P:0x0 Valid sese data: 0x5 0x20 0x0
These messages above can be safely ignored. According
to the official T10 documentation 0x85 operation code is for ATA
pass-through capability:
The underlying SCSI drives do not support SCSI2
command 0x85 in response we received SCSI Sense Code: 0x20 0x0 what
means Invalid Command (for example for Seagate SCSI drives http://seagate.com/support/disc/manuals/scsi/38479j.pdf .)
The SCSI commands 0x4d (Log Sense.) and 0x1a
(Mode Sense(6)) return Invalid Command either.
The similar behaviour is described in http://kb.vmware.com/kb/1036874
IMHO that is not the best VMware KB but at least enlighten
what cause the issue. It focuses on local HP SmartArray controller
but is still valid for LSI controllers and SCSI sens code comes from disk.
===
In ESXi 5.1/5.5, you may see similar errors in the syslog.log file every 30 minutes. For
example:
cpu60:16444)<4>hpsa 0000:03:00.0: Device:C4:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.
cpu42:1071571)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x85 (0x4125c3535000, 17495) to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" on path "vmhba4:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
cpu42:1071571)ScsiDeviceIO: 2329: Cmd(0x4125c3535000) 0x85, CmdSN 0xebb from world 17495 to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
These messages can be safely ignored. They appear as a result of an ATA Pass-through command which cannot be interpreted by the controller.
cpu60:16444)<4>hpsa 0000:03:00.0: Device:C4:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.
cpu42:1071571)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x85 (0x4125c3535000, 17495) to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" on path "vmhba4:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
cpu42:1071571)ScsiDeviceIO: 2329: Cmd(0x4125c3535000) 0x85, CmdSN 0xebb from world 17495 to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
These messages can be safely ignored. They appear as a result of an ATA Pass-through command which cannot be interpreted by the controller.
===
KUDOS to Jeremy Chadwick from FreeBSD mailing list
No comments:
Post a Comment