System storage VOBs introduced in vSphere 8.0
Article ID: 313162
Updated On:
Products
Issue/Introduction
Symptoms:
The following vSphere errors or warnings are observed on an ESXi host when potential problems are detected in the scratch or ESX-OSData configuration.
VOB messages:
esx.problem.osdata.partition.full
"OSData is low on available space ({1} MiB free). This may result in system failure. Please refer to KB article: KB 87212.
esx.problem.osdata.path.notfound
"Configured OSData cannot be found. Please refer to KB article: KB 87212.
esx.problem.scratch.partition.full
"Scratch is low on available space ({1} MiB free). This may result in system failure. Please refer to KB article: KB 87212.
esx.problem.scratch.on.usb
"Scratch is configured to SD-Card/USB device. This may result in system failure. Please add a secondary persistent device."
For more information about VOB messages, see Using the VMkernel Observations for Creating Alarms
Cause
- ESX-OSData/scratch partition is running out of storage space.
-
ESX-OSData/scratch is configured to an unsupported device type or one which is prone to failure.
-
ESX-OSData is configured to a VMFS datastore.
Resolution
Given below are the error messages with resolution :
vob.user.osdata.partition.full and vob.user.scratch.partition.full: The configured ESX-OSData/scratch partition has less than 5% free space available. Remove unnecessary files on the partition or reconfigure ESX-OSData/scratch to a volume where more space is available.
vob.user.osdata.notsupported.on.device and vob.user.scratch.notsupported.on.device: Configure ESX-OSData/scratch to point to supported device type.
vob.user.osdata.on.vmfs : Assigning ESX-OSData to a workload VMFS datastore may exhaust the partition's storage. ESX-OSData should be configured to a dedicated VMFS-L partition on a high-quality device.
Additional Information
Feedback
