This issue is resolved in VMware vSphere ESXi 7.0 U2c. For more information refer to
ESXi 7.0 U2c release notes .To download go to the
Customer Connect Patch Downloads page.
This issue is resolved in VMware vSphere ESXi 6.7 U3p. For more information refer to
ESXi 6.7 U3p release notes.To download go to the
Customer Connect Patch Downloads page.
NOTE:As a best practice, do not set dump partition on USB storage device and do not set USB devices under a heavy workload. For more information, see VMware knowledge base articles
Configuring ESXi coredump to file instead of partition and
High frequency of read operations on VMware Tools image may cause SD card corruptionWorkaround:
If SD card is lower tolerant devices, we can reduce heavy access to SD cards by following below steps
The ToolsRamdisk advanced option tells ESXi to copy vmtools, which exists on the SD-Card, to RAMdisk. It mainly happens on vsan or VDI environment. This creates the advanced option, giving it an accepted value of 0 (disable) or 1 (enable).
- To do this run below command
# esxcfg-advcfg -A ToolsRamdisk --add-desc "Use VMware Tools repository from /tools ramdisk" --add-default "0" --add-type 'int' --add-min "0" --add-max "1"
# esxcli system settings advanced set -o /UserVars/ToolsRamdisk -i 1
# reboot
This sets the ToolsRamdisk option to enable. On bootup ESXi will check the value of ToolsRamdisk and copy the files to the /tools ramdisk.To verify this, run the command:
# esxcli system visorfs ramdisk list
This command shows the ramdisks that have been created. In particular, the /tools ramdisk appears in this output, and it has a Used value of 200MB, so the tools have been copied to there successfully
For more information refer to VMware KB :
High frequency of read operations on VMware Tools image may cause SD card corruption Future ESXi 7.0.x version will have this advanced option set automatically. Refer VMware KB :
ToolsRamdisk option is not available with ESXi 7.0.x releasesThis issue may occur on several releases of ESXi, however the likelihood of experiencing the behaviour is higher on ESXi 7.0 due to some changes in the product that require better performance and endurance from the boot device as noted below:
Starting in ESXi 7.0, the boot partition is formatted as VMFS-L instead of FAT (previous releases) to improve I/O performance.