Storage Spaces recovery

An offline Storage Spaces pool must be treated as a complete device set—not separate disks.

Windows Storage Spaces can stripe, mirror or parity-protect virtual disks across physical drives. Missing quorum, stale members, failed drives or metadata problems can place a pool or virtual disk into read-only, incomplete, detached or unhealthy states.

Start a recovery case Call 682-325-7712

Understand the symptom

Pool metadata and virtual-disk resiliency determine which members and extents are required.

WHY

What is happening

Storage Spaces writes metadata to member disks and maps virtual disks across them according to simple, mirror or parity layouts. A pool can become read-only after losing quorum, while an incomplete virtual disk lacks enough current members to attach. Recreating the pool or resetting disks can overwrite the configuration needed for virtual reconstruction.

What you may see

Symptoms that change the recovery path.

Pool shows read-only or incomplete

Missing or offline disks may prevent quorum or access to current metadata.

Virtual disk is detached

Policy, manual attachment or an unhealthy device set may keep it offline.

Physical disks show lost communication

Cable, enclosure, controller or disk failure may remove required members.

Files disappear after a repair

A stale member or interrupted repair can create inconsistent virtual-disk contents.

Protect the source

Actions that can make the situation worse.

Reset-PhysicalDisk removes pool identity

A reset can erase metadata used to recognize the original member relationship.

Repair writes across surviving disks

Repair is unsafe when disk health, freshness or required redundancy is uncertain.

New pool creation overwrites configuration

The same disks should not be initialized as a fresh storage set before recovery.

Do this now

Safe steps before evaluation.

Stop writes and repairs

Pause services, virtual machines and automatic maintenance using the affected virtual disk.

Export status information

Record pool, virtual-disk and physical-disk names, unique IDs, health and operational states.

Label every drive

Preserve slots, enclosures and removed or replacement members as one set.

Check transport without resetting

Document cables, HBAs and enclosures while avoiding actions that clear metadata.

NEPFOSYS process

How a data-first evaluation proceeds.

Configuration review

NEPFOSYS maps pool membership, resiliency, columns, interleave and failure sequence.

Individual member imaging

Readable physical disks are protected before virtual-disk reconstruction.

Virtual space reconstruction

Pool metadata and extent maps are used to recreate the logical volume away from originals.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Should I set the pool back to read-write?

Only after confirming every required disk and its health. Read-only can be a protective state when quorum or members are missing.

Can I reset a disk marked retired?

Not before recovery. Resetting can remove metadata needed to identify the original pool and virtual-disk layout.

Is Storage Spaces the same as hardware RAID?

No. It is software-defined storage with its own pool metadata and layouts, though recovery still depends on complete member preservation.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case