After replacing a failed capacity tier drive in a vSAN Original Storage Architecture (OSA) environment, the new drive may show as "Unclaimed" or incorrectly appear as a Cache Tier option. Standard disk group recreation may fail due to metadata locks.
Unable to remove device: Failed to get VsanInfo operation lock for diskOpLockIndividual capacity disk is not allowed to be decommissioned from a diskgroup-level dedup disk groupIn vSAN 8.0 OSA with Deduplication enabled, stale metadata in the Cluster Monitoring and Membership Directory Service (CMMDS) can prevent correct tier identification. The vsanmgmtd process may hold a persistent lock on the disk operation, preventing manual removal until the lock file is cleared and the service is cycled.
vdq -inaa.#### ID./etc/init.d/vsanmgmtd stoprm -f /tmp/.vsanDiskOpLock.lock.LOCKcmmds-tool delete -u ####-####-####-####-####/etc/init.d/vsanmgmtd start/etc/init.d/hostd restartesxcli storage core device partition label clear -d naa.####esxcli storage core adapter rescan --allNote: Stopping hostd will temporarily disconnect the host from vCenter, though it does not impact running virtual machines.