What does HRESULT 0x400D0196 (NS_I_RESTRIPE_DISK_OUT) mean?

NS_I_RESTRIPE_DISK_OUT

NS_I_RESTRIPE_DISK_OUT — 0x400D0196

The built-in message is only the immediate status; the useful boundary is that a content disk was successfully removed from active stripe placement as part of a restripe operation.

Operational meaning

Restriping redistributes media-server placement and ownership across disks or Content Servers. In the context of disk removal by restriping, it is a coordinated topology operation rather than a generic filesystem optimization, so pre/post stripe maps, peer identity, capacity, and representative media reads are the relevant evidence. Locate the first component changing state in disk removal by restriping and distinguish later summary errors.

Important distinction. Restriped out is a logical placement result; it does not necessarily erase data or remove the physical volume from Windows.

Facts worth preserving

• Disk/server identity, operation ID, content count before removal, and final capacity map
• Destination disks that received content previously assigned to this disk
• Remaining references to the disk in catalogs, playlists, or administrative configuration
• Disk state and whether physical removal or maintenance is planned

Reproduce the condition safely

1. Enumerate references to the disk after the restripe completes.
2. Stream representative content formerly placed on the disk. Keep media bytes, server identity, and unrelated publishing-point settings fixed.
3. Restart the server without the disk in a maintenance test and verify topology loads. Use a disposable publishing point or maintenance window when the test can alter server or storage state.

What not to infer

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, diagnose that new failure separately rather than treating it as 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.

Closing the incident

Correction: Remove stale configuration references and perform physical retirement only after content and metadata validation.

Accept the repair only when the server starts without depending on the disk, no content lookup targets it, and replacement placement remains stable.

Technical references

• Microsoft Open Specifications: HRESULT values — defines the formal status.
• 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.