Power-on Reset occurred on naa... always happens after guest VM restart

[hongle]

Logging of "Power-on Reset occurred on naa...." in vmkernel happened without fail on a VMware ESXi 4.1.0 build-502767 host upon the restart of the Windows 2008 guest VM, which is also the ONLY guest VM on this host. This event also happened to the restart of a Redhat 5 VM on another host, although details on the involved host are not avail at this stage.

Both ESX host and guest VM seem to be running fine after VM restart.

Around this restart period was also present a number of logging of this nature H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x29 0x0, after which Storage Support staff examined the storage and said nothing was untowards in the underlying storage

Restarting the guest Windows Vm with Diagnostic Startup i.e. just loading essential Windows devices and services only also generated the same event.

Thanks for any suggestion,

Hong

[adelisa]

Hi hongle,

As this problem persisit for both windows and linux,could yuo please check event log if is there .

any error related to disk.

Some times due to disk problem system getting restart.

" Affirmation without discipline is the beginning of delusion."

[Sreejesh_D]

please share the snippet of logs generated  in vmware.log and vmkernel at d time of failure.

[hongle]

Thanks for your interest.

Corresponding to each VM restart e.g.

Feb 22 07:53:06.472: vcpu-0| CPU reset: soft (mode 1)

the event "Power-on Reset"  occurred and this logging was generated, which indicated some storage I/O failure. Nevertheless, the sequence of the events below did happen without fail on each guest VM restart

Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu0:22066)VSCSI: 2252: handle 8192(vscsi0:0):Reset request on FSS handle 1573567 (0 outstanding commands)
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu0:22066)VSCSI: 2252: handle 8193(vscsi0:1):Reset request on FSS handle 1770176 (0 outstanding commands)
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu1:4167)VSCSI: 2526: handle 8192(vscsi0:0):Reset [Retries: 0/0]
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu1:4167)VSCSI: 2326: handle 8192(vscsi0:0):Completing reset (0 outstanding commands)
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu1:4167)VSCSI: 2526: handle 8193(vscsi0:1):Reset [Retries: 0/0]
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu1:4167)WARNING: NMP: nmpDeviceTaskMgmt: Attempt to issue lun reset on device naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. This will clear any SCSI-2 reservations on the device.
Feb 22 07:53:06 vmkernel: 0:03:02:51.519 cpu1:4167)<6>qla2xxx 0000:06:00.0: scsi(2:1:81): DEVICE RESET ISSUED.
Feb 22 07:53:06 vmkernel: 0:03:02:51.526 cpu1:4167)<6>qla2xxx 0000:06:00.0: scsi(2:1:81): DEVICE RESET SUCCEEDED.
Feb 22 07:53:06 vmkernel: 0:03:02:51.526 cpu1:4167)VSCSI: 2326: handle 8193(vscsi0:1):Completing reset (0 outstanding commands)
Feb 22 07:53:07 vmkernel: 0:03:02:52.708 cpu2:4098)NMP: nmp_CompleteCommandForPath: Command 0x0 (0x41027f37c440) to NMP device "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" failed on physical path "vmhba2:C0:T1:L81" H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x29 0x0.
Feb 22 07:53:07 vmkernel: 0:03:02:52.708 cpu2:4098)ScsiDeviceIO: 1688: Command 0x0 to device "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x29 0x0.
Feb 22 07:53:07 vobd: Feb 02 07:53:07.522: 10972708456us: [vob.scsi.scsipath.por] Power-on Reset occurred on naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
Feb 22 07:53:07 vmkernel: 0:03:02:52.708 cpu2:4098)WARNING: ScsiCore: 1355: Power-on Reset occurred on naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[Sreejesh_D]

Does this host has a VM with  RDM LUN or MS Cluster Service configured?