| Previous | Next |
| STATUS_PACKAGE_UPDATING | STATUS_FT_WRITE_FAILURE |
STATUS_NOT_READ_FROM_COPY
One requested copy is unreadable, but redundancy may still preserve the data
STATUS_NOT_READ_FROM_COPY identifies failure to read a specific copy of requested data. In redundant volume handling, that is narrower than saying the logical volume has lost the data. Another copy can still be readable, which is exactly why fault-tolerant volume designs maintain more than one copy.
Correlate this status with STATUS_FT_READ_FROM_COPY or other recovery results for the same range. The combination can identify a known-readable copy and an unreadable member. Keep those identities explicit; a repair or resynchronization procedure must not accidentally select the failed or stale copy as the source.
Repeated application-level reads may hide the distinction if the volume layer automatically tries another copy. Capture member-level errors, volume-management state and the failing range before replacement or rebuild. A logical read that eventually succeeds is still compatible with a member that requires attention.
What to inspect
- The requested copy identifier, member mapping, and exact data range that failed.
- Read results from other copies and the copy that ultimately supplied the data, if recovery succeeded.
- Media, controller and volume events for the failing member before any rebuild changes the layout.
References
- Microsoft Open Specifications: VDS glossary
- Microsoft Open Specifications: Disk Management Remote Protocol glossary
- Microsoft: Basic and Dynamic Disks
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.