Auto-deploy Fails to Apply Host Profile with Error: Disk Device Does Not Support OSDATA

Products

• VMware vCenter Server

Issue/Introduction

When applying a Host Profile during Auto Deploy in an ESXi 8.x environment, the task fails with the following error message:
Error: naa.######################: disk device does not support OSDATA.

This issue prevents the successful application of the host profile and results in the host being unable to proceed with configuration post-boot.

Environment

 

• Product: VMware vSphere ESXi

• Version: 8.x

• Deployment Method: Auto Deploy with Host Profile

• Storage Type: Software iSCSI Adapter

• Disk Device: iSCSI Disk presented via Software iSCSI

 

Cause

VMware has deliberately restricted the use of software iSCSI devices for OSDATA in Host Profile/Auto Deploy workflows.

While software iSCSI may be allowed during installation if the device is detected via a boot-capable HBA or NIC (boot-from-iSCSI), it is not supported for OSDATA configuration post-boot through host profiles. This is due to reliability concerns — such connections tend to initialize slowly, causing configuration failures during early boot stages.

From the syslog.log:

YYYY-MM-DDTHH:MM:SS Wa(12) hostprofile[2100039]: opID=MainThread: Adding missing key RuntimeError.summary
YYYY-MM-DDTHH:MM:SS Wa(12) hostprofile[2100039]: opID=MainThread: excObj is of unknown type: <class 'RuntimeError'>
YYYY-MM-DDTHH:MM:SS In(14) hostprofile[2100039]: opID=MainThread: Cleaned up Host Configuration
YYYY-MM-DDTHH:MM:SS In(14) hostprofile[2100039]: opID=MainThread: /sbin/applyHostProfile sending boot msg to console: Applying Host Profile task list...Error
YYYY-MM-DDTHH:MM:SS Er(11) hostprofile[2100039]: opID=MainThread: while applying tasks: (vmodl.fault.SystemError) {
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    dynamicType = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    dynamicProperty = (vmodl.DynamicProperty) [],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    msg = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    faultCause = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    faultMessage = (vmodl.LocalizableMessage) [
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:       (LocalizableMessageWithPath) {
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          dynamicType = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          dynamicProperty = (vmodl.DynamicProperty) [],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          key = 'com.vmware.vim.profile.engine.UnexpectedError',
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          arg = (vmodl.KeyAnyValue) [
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:             (vmodl.KeyAnyValue) {
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                dynamicType = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                dynamicProperty = (vmodl.DynamicProperty) [],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                key = 'error',
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                value = '[Disk_ID]: disk device does not support OSDATA'
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:             },
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:             (vmodl.KeyAnyValue) {
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                dynamicType = <unset>,
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                dynamicProperty = (vmodl.DynamicProperty) [],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                key = 'context',
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:                value = 'EngineModule::ApplyHostConfig'
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:             }
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          ],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:          message = 'Error: [Disk_ID]: disk device does not support OSDATA.'
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:       }
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    ],
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]:    reason = ''
YYYY-MM-DDTHH:MM:SS Er(11)[+] hostprofile[2100039]: }

Resolution

To resolve the issue, use supported storage media for OSDATA when using Auto Deploy and Host Profiles.

Supported Media for OSDATA:

• Local non-USB storage

• Boot device (non-USB)

• NVMe over Fabrics (NVMeoF)

• BIOS/CNA-based FCoE (independent hardware)

• Independent hardware iSCSI adapters
  
  

Workaround

If using software iSCSI is unavoidable, you may proceed in installer mode, where software iSCSI is allowed under certain conditions.

However, it is strongly recommended to switch to one of the supported OSDATA media types listed above for consistent and reliable Auto Deploy + Host Profile usage.

Additional Information

Storage Adapter and Multipath Info Sample:

esxcfg-scsidevs -a
vmhba64 iscsi_vmk         online         iqn.1987-05.com.cisco:<REDACTED>    iSCSI Software Adapter

localcli storage nmp path list -d <lun_naa.id>
...
Runtime Name: vmhba64:C0:T0:L0
   Device: <Disk_ID>
   Device Display Name: NETAPP iSCSI Disk (<Disk_ID>)
   Group State: active unoptimized
   Array Priority: 0
   Storage Array Type Path Config: {TPG_id=1000,TPG_state=ANO,RTP_id=1,RTP_health=UP}
   Path Selection Policy Path Config: PSP VMW_PSP_RR does not support path configuration.


This confirms the storage is presented via software iSCSI, which is not supported for OSDATA in this scenario.