In Windows, a space created across several disks has disappeared and the system offers to create a new pool. If you need data from the original storage, do not confirm this offer. A new pool is not a way to reconnect the original content. The first question is: which member disks and which layer are still available? Only then does it make sense to choose the next step.
A missing drive letter alone does not prove a lost pool. The problem could be with the volume, the connection, one of the disks, or the configuration. Nor can you tell from a single screen whether all files are intact. With an inaccessible company archive, first limit your attempts and preserve the original setup.
A disk, a pool and a space are not the same thing
Microsoft describes Storage Spaces as grouping physical disks into a pool, from which storage spaces are created. One space therefore does not have to correspond to a single physical disk. This matters when handing things over: the disk Windows flags as problematic may not be enough to assess the entire storage.
The original layout matters too. A Simple space provides no protection against disk failure. With redundancy layouts, the actual configuration and availability of the required members decide; you cannot say that any array will survive any number of failures. Also, don’t confuse Storage Spaces with Storage Spaces Direct or with a hardware RAID controller.
The server documentation distinguishes the state of physical disks, pools and virtual disks. That’s a useful framework for taking inventory, not a guide to import a server repair command into home Windows. The controls and available details differ by edition.
What not to confirm right now
Until you have a verified copy of the data you need, do not create a new pool on the member disks, do not initialize them and do not format them. Don’t replace missing configuration with guesswork. An option called Repair or Reset is not automatically safe just because the system offers it.
The point is not to ban Storage Spaces management forever. It’s about the order of work: an operational intervention designed for a known configuration is not a universal first aid for losing access to the only copy of your data. Before any write, you need to know which media it will affect and how it will be possible to return to the original state.
Drive not responding, clicking or reporting errors? Stop trying anything else.
What not to try any more:
- do not keep powering the drive on or reconnecting it,
- do not run data recovery software, CHKDSK or formatting on the failing drive,
- do not open or take the drive apart.
How it works with us and what it costs: hard drive data recovery.
Initial HDD and SSD diagnostics free of charge — we find out what can be recovered and quote the price in advance; you decide only then. NONSTOP line 775 556 063.
Non-standard cases (drive opened by another service, overwriting/formatting, complex analysis) cost 1 210 Kč including VAT (1 000 Kč excluding VAT) — we tell you in advance.
A safe inventory of the available state
If the computer is on, the disks are not disconnecting and there are no signs of physical failure, record the information already available. Even reading puts load on the medium; a „read" label does not mean zero risk on a faulty disk.
- Write down what exactly disappeared: the drive letter, a specific space, or the entire pool in its management. Photograph the complete message, not just the red icon.
- Compare the original number of members with what the system currently detects. Save the available models, capacities and identifiers. If you don’t have the old list, don’t treat the current count as proof of completeness.
- Open the Storage Spaces management available in your edition of Windows and only record the state. In Disk Management, decline any offers to initialize. Don’t make repair changes just to get a prettier screenshot.
- In Event Viewer, record related events from the time the problem appeared. Save the export or photo outside the affected space; the log may contain internal names and is to be passed only to an authorized administrator.
The result is a list and a timeline, not a repaired storage system. If you don’t see an item, write down precisely that uncertainty. Don’t try to remove it with a series of restarts or by swapping disks around.
How to read the result without a premature diagnosis
| Observation | What to verify | Safe boundary |
|---|---|---|
| Drive letter missing, pool is displayed | State of the space and volume | Don’t create a new pool |
| Pool missing, disks are visible | Completeness of members and configuration changes | Don’t initialize visible disks |
| One member is not detected | Original identification and connection history | Don’t blame the disk alone |
| Access fluctuates, reads fail | Timing of errors and attempts so far | Stop repeated reconnecting |
No row is a definitive diagnosis. A missing disk may be related to the medium, the power supply or the cabling. A displayed disk, in turn, may not provide error-free reading. Even the pool returning after a cable change doesn’t prove that all business files match the last required state.
If the space is genuinely stably readable, first copy the important data to a different healthy storage device. Open the selected copies and verify their content with the owner. Don’t mistake successfully copying one directory for verifying the entire archive. If a new error or disconnection occurs, end this do-it-yourself branch.
When further attempts no longer add useful evidence
New unusual sounds, repeated disconnections, severe read errors or a known health warning are reasons not to continue with ordinary attempts. Don’t run a benchmark, a long surface test or repeated reads of the entire array just to confirm the same symptom.
If a cable check or removing the disks is necessary, don’t do it in a powered-on setup without knowing its conditions. For a server, coordinate the shutdown with the responsible administrator. Document the placement and labeling before anything is disconnected. Disassembly is not a mandatory step of home diagnostics.
What to hand over along with the disks
Prepare the original number of members, available models and identifiers, the known space layout, the Windows version and the course of the incident. The original configuration or its record is useful, along with encryption information and a list of interventions performed. Don’t send passwords and recovery keys into an ordinary public inquiry; agree on a secure method of handover separately.
Keep all available members, not just the one with the error message. Don’t throw away the inaccessible piece, and don’t let another computer overwrite its structures. Also separate the question of data recovery from the later return of the setup to operation: successfully retrieved files do not mean healthy original disks.
Frequently asked questions
Will a new pool with the same name bring the data back?
No. The name is not the original configuration. Creating a new pool on these disks can alter the structures needed to assess and recover the original data.
Is a read-only check on a faulty disk risk-free?
It is not. It doesn’t deliberately change the content, but it still makes the medium work. If the disk disconnects or read errors appear, don’t keep collecting more nearly identical results.
Should I repair the displayed pool right away?
Not just because a button is available. First you need to know the configuration, the state of the members, the available backup and the consequences of the specific operation. When it comes to the only copy of important data, protecting it comes first.
Is it enough to give the specialist one failing disk?
It may not be. The space’s data may be spread across multiple members. Agree to hand over the entire available setup and its records before removing any disk.
Does a Healthy status prove the files are complete?
No. The state of the storage layer does not replace verification of content, the latest versions of documents or their required completeness. These checks belong to validating the copy of data you obtained.
If a pool with the only copy of important data is missing, describe the situation to ITHOPE. Attach the messages, the number of members and the history of interventions. From these materials, further assessment can be agreed without promising a result before diagnostics.
Sources and limits of the procedure
Documentation verified on 7 October 2026. For a different edition of the system, verify the corresponding procedure from the manufacturer.
Where to find us
ITHOPE is a company based in Brno, Czechia: we do data recovery from disks, RAID and NAS, PC and laptop service and IT for business, all in our own lab at Viniční 3587/216, 615 00 Brno.
Phone +420 775 556 063 (24/7 line). You can bring the device in person, or send it by courier (Zásilkovna, PPL).