Storage Spaces protects data by keeping more than one copy of each slab, or by keeping parity. When a member disk fails or the pool runs short of capacity, the pool can no longer place those copies and reports reduced resiliency. The volume still reads, which is exactly why the warning is easy to ignore until it becomes unrecoverable.
Each virtual disk is split into slabs, and the resiliency setting decides how many copies exist. A two-way mirror keeps two copies; parity keeps data and parity blocks across the members.
Reduced resiliency means at least one slab lost a copy. The volume keeps working because the remaining copy is readable, but a second failure in the wrong place takes the volume offline.
The common triggers are a member disk that dropped out, a pool with too little free capacity to rebuild, and a replacement disk smaller than the one it replaced.
Open the Storage Spaces page in Settings and note the pool name, the resiliency setting, the number of members, and which disk shows a warning.
Check the physical drives list for a disk marked as lost communication or missing. A single failed member is the usual cause, and it stays listed until it is retired.
Do not remove the failed disk yet. Removal requires the pool to evacuate its data first, and an already degraded pool may not have room to do that.
Add a healthy disk that is at least as large as the failed one and let the pool rebuild. A smaller disk cannot hold the largest slabs and is rejected or partially used.
If the pool is full but no disk has failed, the fix is capacity rather than repair. Thin provisioning can report free space inside the volume while the pool itself has nothing left to allocate.
Once the pool reports healthy, read a sample of older files. A pool can report healthy while returning errors on slabs written long ago.
Qiling Disk Master can copy the mounted virtual volume to a disk outside the pool. That copy is what lets you repair the pool without risking the only readable data.
Open the Backup and Recovery tab and choose File Backup. Use File Backup for the pool volume, and switch to System Backup only when the pool holds the operating system.
Expand Computer in the source tree and tick the drive letter that belongs to the pool volume. Match the capacity shown there with the pool report, so you tick the Storage Spaces volume and not another disk.
Click the destination path at the bottom of the window and choose a folder on an external disk or on a disk from another pool. Check that the free space is larger than the used space of the volume, click OK, and never point the task at a folder inside the same pool.
Name the task, click Proceed, and let the job finish. Open the backup point afterwards and restore a sample file to a temporary folder, which proves the copy is readable before you touch the pool.
It is readable but no longer protected. One more failure on the wrong member can take the volume offline, so copy the data now.
No. Redundancy requires capacity on healthy members. With one disk the pool cannot recreate the missing copies.
Yes, once it is added and the pool rebalances. A smaller disk does not restore all slabs.
Only after the data is copied. Rebuilding the pool destroys the volume layout, not just the redundancy.
For a pool that refuses to release a failed disk, see Storage Spaces disk missing and cannot be removed.