What does HRESULT 0x80830001 (ERROR_TIERING_NOT_SUPPORTED_ON_VOLUME) mean?

ERROR_TIERING_NOT_SUPPORTED_ON_VOLUME

Why this is narrower than a generic disk error: tiering not supported on volume

ERROR_TIERING_NOT_SUPPORTED_ON_VOLUME has unsigned value 0x80830001. In the tiering layer, the operation is rejected because the addressed volume has no storage-tier capability exposed by its storage provider and file-system stack. Diagnosis should follow file-to-tier placement metadata for the addressed volume through one controlled state transition.

Storage tiering operates above a tiered Storage Spaces virtual disk and records desired placement separately from normal file allocation. Optimization may move data according to heat, whereas pinning expresses an explicit placement preference for a supported file or volume object.

Storage facts that change the diagnosis

A/B test

1. Capture the API parameters and object map that led to this result; do not begin with cleanup.
2. Build a passing control with the same disks or image copy and preserve volume GUID path, storage-space and tier IDs, file ID plus file-system identity, cluster owner node, optimization job state and requested pin target.
3. Run the narrow transition described here: query the volume tier inventory and repeat the exact call on a known tiered Storage Spaces volume without changing the file or policy.
4. Compare resulting IDs, counts, health and ownership to prove the caller crossed the result invariant rather than suppressing it.

A useful diagnostic fork is ERROR_NOT_A_TIERED_VOLUME versus this result. This code concerns the addressed volume has no storage-tier capability exposed by its storage provider and file-system stack; the alternate code should remain observable after the fix, proving the application did not suppress the entire subsystem.

Mechanism-specific note

Capability must be queried from the actual backing virtual disk and provider. A fast SSD plus a slow HDD do not automatically make an arbitrary volume tiered. Confirm a Storage Spaces tier configuration and the file-system/provider support before exposing pin or tier-optimization controls.

Corrective action and regression check

Re-enumerate the volume, its storage tiers and the file object on the owner node; serialize optimization jobs and apply pinning only to supported objects on a live tiered volume. The repair is incomplete until a fresh enumeration and new handle observe the corrected state.

• The original request now reaches success or a documented later status with the intended layout and access mode.
• A new enumeration reports internally consistent IDs, counts, geometry and ownership for the corrected object.
• The application still distinguishes it from ERROR_NOT_A_TIERED_VOLUME and has no unbounded retry loop.

Technical references

• Microsoft: MSFT_FileStorageTier class — documents the supported management path relevant to this HRESULT.
• Microsoft: Set method of MSFT_FileStorageTier — defines the tiering objects used to interpret it.
• Microsoft: Optimize-Volume — primary API or object-model reference.
• Microsoft: fsutil tiering — use this source to verify tiering state and parameters.