It’s recommended by VMware to have a persistent scratch location for VMkernel logs in case that ESXi is installed on USB stick or SD card (1Gb is minimum size). ESXi scratch partition, for those particular cases, resides in memory – in RAM disk, which is limited in size. The size is only 512 Mb, which is taken out of the server’s available memory. Having scratch location in RAM might get problematic when running lots of VMs so the memory gets restrained.
Also, if you reboot the host, you’ll basically loose the VMkernel logs so having persistent scratch partition is a good thing. You would certainly want to keep the logs, don’t you? You can then use Splunk to present and seek the logs with through GUI, or use Syslog bundled with vCenter.
Which problems you can run into if you don’t configure persistent storage for the log files? You might experience HA agent issues on those miss-configured hosts, or you’re not able to activate HA at all. Other symptoms might show “general system Error” in vSphere Update manager (if you’re using it). You’ll basically need to create a persistent scratch location for ESXi. It’s straightforward process, which can be done through vSphere Client, PowerCLI or vCLI. Let’s see the vSphere client way.
How to configure scratch location for ESXi logs? Follow those steps
- Connect to vCenter Server or the ESXi host using the vSphere Client > Select your host > Sonfiguration > Storage
- Right click datastore (local or shared) and select Browse
- Create folder for this ESXi host named for example “scratch”> close the datastore browser.
- Select the host > configuration > Advanced (software section) > ScratchConfig > Change the ScratchConfig.ConfiguredScratchLocation
- Click OK > go and put the host in maintenance mode and reboot for the configuration to take effect.
Now, if you have for example 3 hosts in your cluster, just create a separate folder for each of your host, so the hosts don’t overwrite each other’s data.
Some more read and sources:
- ESXi host is unable to generate support logs because local storage is full – http://kb.vmware.com/kb/1007329
- Exporting diagnostic data fails on ESXi embedded – http://kb.vmware.com/kb/1006582
- Patch installation and log collection on ESXi 4.1 Update 1 fails when /tmp/scratch is missing – http://kb.vmware.com/kb/1037190
- ESXi hosts without swap enabled cannot be added to a VMware High Availability Cluster
- Creating a persistent scratch location for ESXi 4.x and 5.x
- Check for ESXi scratch persistence (Forbes Guthrie’s blog)
- Recommended disk or LUN sizes for VMware ESX/ESXi installations
- Storage requirements for ESXi Installations – VMware Pub