| Previous | Next |
| VDS_E_NO_MAINTENANCE_MODE | VDS_E_DISK_HAS_BANDS |
VDS_E_BLOCK_CLUSTERED
This is stronger than the maintenance-mode error. The VDS catalog says the specified disk or volume is managed by Microsoft Failover Clustering and must be removed from the cluster for the requested operation. Maintenance mode is therefore not the required boundary for this particular action; cluster ownership itself must be removed.
Why this state matters
Removing a clustered resource can affect dependent roles and storage availability. Microsoft documents Remove-ClusterResource as deleting the clustered resource and warns administrators to consider dependencies first. The HRESULT should trigger a cluster-ownership review, not an attempt to bypass the block with raw disk tools while the cluster still believes it controls the resource.
Diagnostic focus
- Map the disk or volume to its failover-cluster resource and enumerate resource dependencies and owning roles.
- Confirm that the intended VDS operation really requires removing cluster management rather than merely entering maintenance mode.
- Coordinate application/role downtime and remove the resource through supported Failover Clustering controls if the operation is intentional.
- Refresh VDS after cluster ownership changes so the storage object is not reused from a cache that still reflects clustered state.
Technical references
MS-VDS error codes · Remove-ClusterResource · Maintaining Physical Disk Resources · IVdsService::Refresh · VDS common return codes
Looking for a different code? Search another status or error code.