What does HRESULT 0x400D005A (NS_I_START_DISK) mean?

NS_I_START_DISK

NS_I_START_DISK — 0x400D005A

A productive reading of administrator-requested disk start begins at the component boundary where a NetShow administrator explicitly requested that a configured content disk be brought online.

Operational meaning

Administrative information messages record who requested a transition and which object was targeted. In the context of administrator-requested disk start, they do not guarantee that the requested start, stop, rebuild, or removal completed, so the follow-up object-state event is essential. Locate the first component that changes state and distinguish later summary errors.

Important distinction. This message records the control action, not the successful completion of disk initialization.

Facts worth preserving

• Administrator network location, target disk identity, request timestamp, and authorization context
• Disk state before the request and the follow-up start, failure, or rebuild event
• Server mapping for the disk and any maintenance lock
• Reason recorded in change control or automation logs

Collect enough to identify the attempt without copying private media or secrets; hashes, object IDs, timestamps, and configuration exports are normally sufficient.

Reproduce the condition safely

1. Issue the start from one supported administration path and correlate the resulting disk event. Retain a known-good stream, session, or server object so a broad restart is not mistaken for repair of the reported failure.
2. Compare a healthy offline disk with a disk held by rebuild or failure state.
3. Verify that the same identity cannot start an unassigned disk. Keep media bytes, server identity, and unrelated publishing-point settings fixed.

What not to infer

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: Resolve any state or metadata error reported after the request; do not treat repeated start commands as repair.

Accept the repair only when one authorized request produces a disk-running event for the intended object and the disk serves content afterward.

Technical references

Use these Microsoft references for the formal contract and combine them with the exact server or catalog evidence from the incident: 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.
• 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.