VMRC stops after some runtime

[GuenterKrembsle]

I just made an upgrade / fresh install with

HPE Customized ESXi 7.0.2 Image version 702.0.0.10.7.0 for HPE Servers based on VMware ESXi 7.0.2 release.

on an ProLiant ML350p Gen8.

Everything runs fine (even the installation had no problem) but after about 24 h runtime the access to all Remote / Web console gets lost.

In Vcenter i can see the "running circle" instead of an image.

Both - remote and web console - can not connetc to the VM's. To all VM's.

As VMRC is directly connected to ESXi and not VCenter i did some testinh with ping and nameserver.

But this cannot be the cause, as it works fine, directly after rebooting the esxi.

Any idea how i can fix this issue?

 

[GuenterKrembsle]

i did some investigation.

I can loggon via ssh. type in cd /var/log

but an ls -i or cat Xorg.log brings the ssh session to an end - the screen is no longer responding.

This is really, really strange ?

[ShoHRock]

what does logs say at the time of disconnect? hostd.log, vmkernel.log?

[GuenterKrembsle]

the first time i created a log bundle it did not even complete. Simple actions like "cat" or "ls -l" did not work in ssh console. They just did not bring up any response.
So i decided to do a fresh install with the regular esxi. This is currently "under test".

But before i did this, i was able to get some log files but i do not really see the proble in there.

There's one in hostd.log:

2021-08-02T01:33:30.168Z info hostd[2099720] [Originator@6876 sub=Libs opID=sps-Main-761121-10-ce-71-00ec user=vpxuser:VMWARE.LOCAL\vpxd-extension-25f17767-ac7c-49cc-8754-781d96ad3053] New error before the previous is handled

---

i will attach both - maybe you can find something interesting in there. need to zip them as log is not supported.

What i think - i might be a problem with a VIB from HP

 

 

[casaub]

Keep in mind: Gen8 does not support ESXi 7. Latest supported version on that machine is ESXi 6.0 U3


https://techlibrary.hpe.com/us/en/enterprise/servers/supportmatrix/vmware.aspx

https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=server&productid=20215

[GuenterKrembsle]

yes, i am aware of this but to be honest - even no longer "supported" system normally worked fine. It - most of the time - seems to be mor a marketing issue than a technical one.
Until now the regular esxi7 seems to work without the above mentioned problem ...

[GuenterKrembsle]

It took some longer time but again and with the "regular" esxi version - the system got somehow stucked.
Started an ls -l command in ssh and this takes very, very long time. I can see the result coming to the shell about 1 line per minute.

Overall it feels as if the ressources for the host itself to manage are to low?

While login,and standard tasks like cd and ls work as expected, a simple grep or cat is again bringing the system in a kind of sleep.

This is really strange. Any help?

 

[GuenterKrembsle]

Getting no help in this forum brngs me to the question what it's intention is?
Well, i was able to find the cause:

Bootbank cannot be found at path '/bootbank'

This is handled in a kb from vmware:

https://kb.vmware.com/s/article/83376

As i am using an SSD on SATA to boot the problem seems not to be focused on "slow" USB SD cards.

There's an informative other thread in a much better functioning forum:

https://kallesplayground.wordpress.com/2021/04/25/esxi-7-0-u2-bootbank-cannot-be-found-at-path-bootbank/

It looks the same there - even ssd's don't fix the problem.

And on dell forums the same problem can be seen

https://www.dell.com/community/PowerEdge-Hardware-General/VMware-7-0-U2-losing-contact-with-SD-card/td-p/7842787/page/5

So - even using a not supported HPE GEN 8 - i think this is a problem that should be fixed be vmware.

[Scott Vessey]

VMTN is a user community forum, where contributions are made voluntarily by members in their own time, not sure what you were expecting.

You have had replies from 2 other community members.

If you want to raise an issue with VMware, open a support request.