Troubleshooting Automation-Driven "InvalidDeviceSpec" Errors during Hot-Add Operations in vSphere

Products

• VMware vSphere ESX 8.x

Issue/Introduction

Automation workflows sometimes encounter "InvalidDeviceSpec" errors when triggering disk hot-add operations in vSphere. This document provides steps to isolate whether the failure is environmental or caused by automation timing discrepancies.

• "Invalid configuration for device '0'" error reported during automation tasks.
• Log File: /var/run/log/hostd.log
OBJLIB-FILEBE : FileBEOpen: can't open '####' : Could not find the file.

Environment

• VMware vSphere 8.x
• vCenter Server Appliance 8.x

Cause

The automation workflow may be initiating the disk reconfiguration request before the ESXi host metadata or storage commit process is complete, leading to a race condition.

Resolution

1. Perform a manual hot-add/remove of the disk via the vCenter User Interface.
   
   1. Select the affected Virtual Machine
   2. Edit Settings > Add Device > New Hard Disk
2. If the manual operation succeeds, verify that the vSphere storage stack is functioning normally.
3. Review automation logs for task timing or sequencing errors.
4. Implement a retry mechanism or a delay (e.g., 5-10 seconds) within the automation workflow to allow for metadata synchronization before re-triggering the disk add operation.