| Previous | Next |
| STATUS_VID_REMOTE_NODE_PARENT_GPA_PAGES_USED | STATUS_VOLMGR_INCOMPLETE_DISK_MIGRATION |
STATUS_VOLMGR_INCOMPLETE_REGENERATION
Regeneration ran, but the surviving copies could not supply all data
STATUS_VOLMGR_INCOMPLETE_REGENERATION is not the same as a regeneration that never started. Volume Manager attempted to rebuild redundant data, yet bad sectors on the active plexes prevented a complete copy.
Microsoft defines a volume plex as a complete copy of a volume, and its recovery protocol describes resynchronizing mirrors and regenerating RAID-5 volumes. This warning means the source side of that recovery was itself imperfect: some requested data could not be read from the copies that remained active.
A volume can therefore exist and even return much of its data while still having unrecovered regions. Preserve the exact disks and event sequence, identify which plexes were active during regeneration, and treat successful reads elsewhere as insufficient evidence that the rebuild is complete.
What to inspect
- Check the health and rebuilding state of every plex or RAID-5 column involved in the recovery.
- Locate read errors that occurred during regeneration and map them to the source disk rather than only the replacement target.
- Plan data recovery before repeating rebuild operations if the remaining active copies also show media errors.
References
- Microsoft VOLMGR text for STATUS_VOLMGR_INCOMPLETE_REGENERATION.
- MS-VDS recovery behavior for mirror resynchronization and RAID-5 regeneration.
- Microsoft VDS health states including rebuilding and failing.
Looking for a different code? Search another status or error code.