| Previous | Next |
| NS_I_DISK_START | NS_I_DISK_REBUILD_FINISHED |
NS_I_DISK_REBUILD_STARTED
NS_I_DISK_REBUILD_STARTED — 0x400D0056
Treat this code as a record of content disk rebuild start: in the operation that returned it, the server began reconstructing the legacy content-disk structures identified in the event.
The contract behind the code
Rebuild events form a stateful sequence with one owner, an initial disk condition, reconstruction sources, progress, and a terminal result. In the context of content disk rebuild start, preserve the entire sequence and the pre-rebuild identity data; repeated starts can destroy the evidence that distinguishes source loss from destination failure. Locate the first component changing state in this condition and distinguish later summary errors.
Important boundary. Starting reconstruction does not mean data integrity has been restored; completion or abortion and post-rebuild reads must be examined. Record the exact constant and returning API.
Diagnostic worksheet
| Incident fact | What it separates |
|---|---|
| Disk ID, server name, rebuild start time, source peers or surviving stripes, and expected data set | Provides a stable before/after comparison for the proposed correction. |
| Free space, I/O error counters, filesystem health, and control-block version before reconstruction | Shows whether the status is expected information, a warning, or the first failure in the event sequence. |
| Rebuild progress events and any concurrent restripe or offline action | Ties the message to one server object and one transition instead of a later retry. |
| Operator action or automatic condition that initiated the rebuild | Separates configuration or identity from storage, parser, network, or lifecycle state. |
Collect enough to identify the attempt without copying private media or secrets; hashes, object IDs, timestamps, and configuration exports are normally sufficient.
Useful comparisons
- Measure whether source data and destination capacity remain stable throughout a small controlled rebuild. Use a disposable publishing point or maintenance window when the test can alter server or storage state.
- Verify that no second administrator or automation task is stopping or restriping the same disk. Retain a known-good stream, session, or server object so a broad restart is not mistaken for repair of the reported failure.
- Compare rebuild duration and I/O errors with a known healthy disk of similar size. Record the first server event, object state, or return value that changes.
Retry only after one controlled server, object, route, storage, or input condition changed; an uncontrolled service restart creates a new execution context and is not proof that the original condition was transient.
Read the result in context
When a minimal control succeeds, the failure is tied to the original object or its state rather than to the whole Windows subsystem. When the control fails identically, preserve host-level evidence first. If a different code appears, that is a moved boundary, not automatic success.
Also check severity: informational and warning values are observations or policy notifications and should be routed differently from a failure HRESULT even when an event viewer labels the source generically.
A defensible fix
Correction: Remove the underlying media, capacity, peer, or metadata obstacle and allow one rebuild owner to complete the operation. Keep the original server configuration, event sequence, object inventory, input hash, and topology snapshot so the change can be reversed and explained.
Accept the repair only when a finished event follows, control metadata is consistent, sample content validates, and no automatic rebuild immediately restarts. Repeat the original supported operation under the original identity and object state; a simplified media file, replacement server, new session, or different client is useful comparison evidence but not final regression proof.
Technical references
These sources describe the API, service architecture, and status values relevant to this diagnosis: Check version-specific behavior against the Windows Media Services and SDK generation that produced the event.
- Microsoft Open Specifications: HRESULT values — defines the formal status or component boundary.
- Microsoft: Windows Media Services 9 Series SDK — documents the relevant API or lifecycle.
- Microsoft: Windows Media Services SDK architecture — provides the architecture, format, or protocol context.
- Microsoft: programming the Windows Media server object model — supports the controlled verification criteria.
Looking for a different code? Search another status or error code.