DG's Hardware board

Latest Debian 12 VM-machine(s) installed on ESXi 6.7u3 Server have the following settings:

Compatibility
Guest OS Version: Debian GNU/Linux 10 (64-bit) - as latest option within ESXi 6.7u3 under OS Linux.
Compatibility: ESXi 6.7 U2 virtual machine



I found a VM with Compatibility: ESX/ESXi 4.x vitual machine



Checked all others, all are new, except the one (above).

VMware Tools
We found different VMware Tools versions on different Linux Debian virtual machines:
1 - open-vm-tools 12.2.0 build 21223074 ( Debian GNU/Linux 10 (64-bit) )
2 - VMware Tools 10.3.25 build 20206839 ( Other 4.x or later Linux (64-bit) )



No idea which is 'better'.

Boot
We also have to check which machines boot BIOS and which boot EFI:

DG.

We did a reboot of the ESXi after some weird issues occurred:



We were unable to reboot or shut down my old webserver on ESXi.
Eventually rebooted the complete ESXi server.

DG.

VMware Tools

We have changed all Linux machines to open-vm-tools 12.2.0.
Only Zoneminder still runs on Debian 11 and has therefore open-vm-tool 11.2.5.



We only have different Guest-OS for linux machines, we'll see what is the best settings.

DG.

The weird errors -as 2 posts above- are most probably due to a failing SSD:


Although ESXi web ui does show the SSD as working and active, the VM's running on it are unresponsive.
Second time in 1 week (Fri - Fri):


Trying ssh into ESXi and run 'ls -al /' already hangs the session as the OS wants to read from a non-responsive device.
Next I went to AMT of this machine to take over screen, and checked the logs:


Here is clearly the Kingston SA400S37480G the culprit (Failed).

Try to restart management services to re-gain access to web ui:


and:


Without success, now I get on any browser:


And this with all other VM's (including this one) still running and active.
That is a good thing, tho.
But the machine must be brought down to remove the faulty SSD, and re-establish web access.

DG.