robopet3

Virtualizing MS SQL Server on vSphere 8.0 Architecture Best Practices Guide
https://blogs.vmware.com/apps/2023/02/updated-virtualizing-ms-sql-server-on-vsphere-8-0-architecture-best-practices-guide.html

В ESXi 7.0 изменилась разбивка диска на партиции и появился новый режим Degraded Mode, Дункан Эппинг поясняет что это означает и на что влияет
http://www.yellow-bricks.com/2020/06/15/running-esxi-in-degraded-mode-what-does-that-mean

tl;dr - If you are going to use ESXCLI to upgrade your standalone ESXi host, please make sure to use the correct command or you will have issues. Below are the two commands you will need to determine which ESXi Image Profiles are available given an offline bundle and then updating to a specific image profile.
https://www.virtuallyghetto.com/2020/04/important-nvme-ssd-not-found-after-upgrading-to-esxi-7-0.html

Disk partition layout for ESXi in vSphere 7 -

However, in current release, there are bunch of changes. We do not have similar layout.

The new layout seems to be more compact. Though we still have boot banks, however, there are changes to the sizing of boot banks. Now both boot bank partitions are of 500 MB each.

ESXi 7.0 requires a boot disk of at least 8 GB for USB or SD devices. Although an 8 GB USB or SD device is sufficient for a minimal installation, you should use a larger device. The additional space is used for an expanded core dump file. In the screenshots above, we have used ESXi instance from this device type only.

At least 32 GB space for other device types such as HDD, SSD, or NVMe. When booting from a local disk, SAN or iSCSI LUN, a 32 GB disk is required to allow for the creation of system storage volumes, which include a boot partition, boot banks, and a VMFS-L based ESX-OSData volume.

https://blogs.virtualmaestro.in/2020/04/disk-partition-layout-for-esxi-in.html?m=1

Quick Fix – No Datastores after ESXi 7.0 Upgrade on SuperMicro with Intel Based SATA Adapters
As usual, I like to jump right into software upgrades to test out new functionality (on none production systems of-course). With the GA of vSphere7 overnight, I went about upgrading my Homelab vCenter and ESXi host. The vCenter upgrade went well, but I ran into an issue after I upgraded the ESXi Host using the online bundle upgrade.

So my assumption was that because the Intel Drivers where only compatible up to ESXi 6.7, with the Default VMware drivers disabled, there was no fall back. As William Lam states here, the original performance issue was fixed in Update 1 of 6.5, and suggested to re-enable the Default VMware AHCI driver. After re-enabling the drivers, I rebooted and tried the upgrade again… this time with success and with all the Datastores listed.
https://anthonyspiteri.net/datastore-esxi7-upgrade-supermicro/

AHCI (vmw_ahci) performance issue resolved in ESXi 6.5 Update 1
https://www.virtuallyghetto.com/2017/07/ahci-vmw_ahci-performance-issue-resolved-in-esxi-6-5-update-1.html