VMware Cloud Community
jmhayes
Enthusiast
Enthusiast

vmkernel: ScsiDeviceIO errors

I'm running ESXi 4.1 Update 1 on a dual-hexcore Supermicro with two 3ware 9750-8i cards.  Everything is up to date patch-wise.  The other day I was copying a VM (about 160GB) while ssh'd into ESXi.  I got the following errors:

Apr 18 00:12:27 vmkernel: 0:00:00:48.117 cpu12:4744)VMWARE SCSI Id: Id for vmhba2:C0:T0:L2

Apr 18 00:12:27 vmkernel: 0:00:00:48.142 cpu0:4120)ScsiDeviceIO: 1672: Command 0x1a to device "naa.600050e07a2015008b0c000280640000" failed
H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.

Apr 18 00:12:27 vmkernel: 0:00:00:48.142 cpu12:4744)ScsiDeviceIO: 4494: Could not detect setting of QErr for device naa.600050e07a2015008b0c000280640000.  Error Failure.

And then the device was gone.  Needless to say all my VMs were in great distress at that point, and the only solution was a reboot of the hypervisor.  I ran a VERIFY on the RAID units and didn't get any errors or messages.

I've taken the machine out of service at this point and on reboot I see a lot of messages like this:

Apr 21 18:30:01 vmkernel: 0:00:01:17.650 cpu8:4104)ScsiDeviceIO: 1672: Command 0x1a to device "naa.600050e07a2015008b0c000280640000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.

I get one of these messages for each of the 9 devices across 16 disks.  I've read that "H:0x0" means it's not an error at all, but I'm puzzled by the use of the word "failed" ...

I get a cluster of these 9 error messages during any significant change I make to a VM configuration via the vSphere client.

Any ideas what's going on here?

Thanks.

Tags (4)
Reply
0 Kudos
5 Replies
MauroBonder
VMware Employee
VMware Employee

check if this kb help http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101610...

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos
habibalby
Hot Shot
Hot Shot

Hello,

I'm facing the same issue, but if the LUN is presented to only one ESX Hosts then this error won't appear at all. As soon as the LUN(s) presented to other servers, the error will start appearing on the newly added host. For instance, ESX02 having an iSCSI LUN presented, the error won't show up. As soon as the same LUN presented to ESX01 the error will start filling the vmkernel log file of ESX01.

Best Regards, Hussain Al Sayed Consider awarding points for "correct" or "helpful".
Reply
0 Kudos
jmhayes
Enthusiast
Enthusiast

I don't see the errors at boot time, so I don't think that kb article is relevant.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

Check http://kb.vmware.com/kb/289902

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
jmhayes
Enthusiast
Enthusiast

Thanks, I looked at that article but it doesn't explain H:0x0 D:0x4 P:0x0

Reply
0 Kudos