| Previous | Next |
| STATUS_VOLMGR_DISK_NOT_ENOUGH_SPACE | STATUS_VOLMGR_DISK_SECTOR_SIZE_INVALID |
STATUS_VOLMGR_DISK_REVECTORING_FAILED
The attempted bad-sector recovery action itself failed
STATUS_VOLMGR_DISK_REVECTORING_FAILED is returned after Volume Manager cannot complete forced revectoring for bad sectors. It is not a volume-type mismatch and it is not equivalent to a stale LDM database entry.
Revectoring concerns the storage path below the logical volume layout: the request is trying to deal with sectors that cannot be used reliably. A failure can originate in physical media, a controller, firmware, or the backing storage of a virtual disk; the NTSTATUS value alone does not distinguish those causes.
Retrying layout operations without checking the underlying I/O history can hide the sequence that led to the error. Capture the disk identity and failing operation, inspect hardware diagnostics and storage events, and decide whether the disk should be removed from service before attempting volume regeneration.
What to inspect
- Look for preceding disk or controller I/O errors and note the physical or virtual disk that reported them.
- Use vendor or platform health diagnostics where available; do not infer healthy media from a readable file system.
- If the disk belongs to a mirror or parity volume, evaluate the redundancy state before replacing or offlining it.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_DISK_REVECTORING_FAILED.
- Microsoft Disk Management troubleshooting for dynamic disks with I/O errors.
- Microsoft VDS health states for failing and rebuilding storage objects.
Looking for a different code? Search another status or error code.