| Previous | Next |
| STATUS_VOLMGR_VOLUME_OFFLINE | STATUS_VOLMGR_NUMBER_OF_EXTENTS_INVALID |
STATUS_VOLMGR_VOLUME_RETAINED
The retained-partition state is already present
STATUS_VOLMGR_VOLUME_RETAINED is the opposite state mismatch from STATUS_VOLMGR_VOLUME_NOT_RETAINED. Volume Manager reports that the volume already has the retained-partition association, so the requested retain operation is redundant or out of sequence.
This status does not indicate that the disk failed or that the volume is healthy. The public error tables define only the association state; the diagnostic question is why the caller is attempting to establish it again.
Follow the management workflow that issued the command and verify how it records completion. A lost callback, stale cache, or retry after a client timeout can repeat an operation that succeeded server-side, leaving the client and Volume Manager with different views of the same state.
What to inspect
- Query the retained-partition association before issuing another retain operation.
- Correlate prior task completion or notification results with the volume identifier used in the retry.
- Make the workflow tolerate an already-present state instead of treating the condition as physical storage failure.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_VOLUME_RETAINED.
- MS-VDS wording for an existing retained-partition association.
- MS-DMRP behavior for asynchronous management tasks and notifications.
Looking for a different code? Search another status or error code.