Unable to turn off vm, server gets stuck. Esxi 6.7

[Janmail]

Hi guys,

I have a big problem with one server, its a HP G10, with freshly installed esxi 6.7 latest.

The problem is when I try to turn off a virtual machine, then it says turning off and nothing but does not turn off the vm. the interface gets stuck. on the esxi host gui and also from vcenter, then I cannot do anything anymore. the vm keeps working. the gui keeps working for some time and then gets stuck and I'm unable to do anything. and this problem blocks any other action. even if I want to turn off the esxi it's not turning it off, i have to press power button and turn off the whole server.

Turning on vm's is no problem, this problem happens only when turning off vm's.

Please help / advise how can I solve this.

I have tried restarting agents via terminal etc... nothing helps.
even if i get to the esxi interface on server, the yellow management interface and use F12 to turn off / shutdown the server its asking password and after that says turning off, but server keeps working.

this server is new install, new hdd's new ram. its completely good working server.

[continuum]

Can you power off the misbehaving VMs via ssh using esxcli ?
Make sure that the datastores are not running out of free space - especially not if you try to suspend VMs.

Ulli

[Janmail]

That i didnot try, will try it next.

I have enough room on the storage and I never suspend vm's. only on or off.

[Janmail]

2 things

yesterday found out that the time was wrong on this server, was like 2001. corrected that.

today turned off multiple vm's via terminal. and all went well. later will turn off via gui.

[Janmail]

Just did a restart via gui, whole interface froze and I cannot get it back again.

and tried it true cli, it froze to, i had to do ctrl+c to stop the command cause there was no reaction at all

off / on no difrence.

so the time was not the problem. the problem is still there. as soon as I do shutdown or restart true the gui it freezes.

[continuum]

Have a log at your vmkernel.log - you should find some information there.

[Janmail]

2022-06-22T12:07:00.701Z cpu8:2110459)VSCSI: 2623: handle 8217(vscsi0:0):Reset request on FSS handle 12125743 (0 outstanding commands) from (vmm0:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
2022-06-22T12:07:00.701Z cpu1:2097480)VSCSI: 2903: handle 8217(vscsi0:0):Reset [Retries: 0/0] from (vmm0:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
2022-06-22T12:07:00.701Z cpu1:2097480)VSCSI: 2691: handle 8217(vscsi0:0):Completing reset (0 outstanding commands)
2022-06-22T12:07:02.721Z cpu0:2097499)VMW_SATP_LOCAL: satp_local_updatePath:789: Failed to update path "vmhba32:C0:T0:L0" state. Status=Transient storage condition, suggest retry
2022-06-22T12:07:04.383Z cpu0:2097195)NMP: nmp_ThrottleLogForDevice:3689: Cmd 0x25 (0x45a27aea85c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL
2022-06-22T12:07:04.383Z cpu0:2097195)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba32:C0:T0:L0" state in doubt; requested fast path state update...
2022-06-22T12:07:04.383Z cpu0:2097195)ScsiDeviceIO: 3029: Cmd(0x45a27aea85c0) 0x25, CmdSN 0x4e96 from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x65 0x6e 0x73.
2022-06-22T12:07:10.735Z cpu18:2110467)VSCSI: 2623: handle 8217(vscsi0:0):Reset request on FSS handle 12125743 (0 outstanding commands) from (vmm0:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
2022-06-22T12:07:10.736Z cpu1:2097480)VSCSI: 2903: handle 8217(vscsi0:0):Reset [Retries: 0/0] from (vmm0:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
2022-06-22T12:07:10.736Z cpu1:2097480)VSCSI: 2691: handle 8217(vscsi0:0):Completing reset (0 outstanding commands)

and this goes on and on.