A drive letter does not reveal how many disks back a Windows 8 storage space. Before migrating data, map pools, spaces and physical drives. This is a read-only inventory: it creates no pool, removes no disk and upgrades no storage format. Windows 8 is no longer supported; the inventory prepares migration but does not confirm target-system compatibility.
1. Document the existing view
Open Control Panel – System and Security – Storage Spaces. Record the PC, Windows version, inspection date and each existing pool with its status. Expand available details. If only the option to create a pool appears, do not create one: that does not prove connected disks are empty. Stop if an expected pool is missing and have the original configuration clarified.
2. Record three separate layers
- Pool: name, displayed total capacity, used or free capacity and warnings.
- Storage space: name, drive letter, owning pool, maximum logical size, usage and resiliency type such as Simple, Mirror or Parity. Record what is displayed, not an assumption based on disk count.
- Physical drives: count, displayed names, capacities, status and unique identifiers where available. Add existing enclosure or connection labels without disconnecting devices or opening an enclosure.
Similar disks may have identical names. An unresolved identification remains an open issue; a drive letter is not a serial number. Keep the inventory protected outside this pool. Recovery keys do not belong in screenshots or the general inventory.
3. Interpret capacity and protection
With thin provisioning, a space’s maximum logical size may exceed physically available capacity. Free space in Explorer alone therefore does not establish sufficient pool reserve. Several spaces may share one pool. Mirroring and parity need additional capacity; do not add logical sizes as if they were installed disk capacity.
A simple space offers no corresponding fault tolerance. Mirroring or parity can handle certain disk failures, but is not an independent backup against accidental deletion, malware or loss of the whole device. “Healthy” is not a recovery test. Record exact warning text and avoid additional write load; do not remove, initialize or format a suspected faulty disk on a guess.
4. Prepare an independent copy
List the required data for each space. If it can be read without errors, copy it to an approved destination outside the same pool. Check copy errors and open representative destination files. Another location in the same pool is not an independent copy. If reads fail or drives are failing, plan professional backup or recovery first instead of repeatedly forcing full copies.
A physical pool member is not a standalone readable file copy. Windows 7 in particular does not support Storage Spaces. Do not experimentally attach individual members to other systems or accept initialization there. Moving a complete pool and upgrading its format require separately verified compatibility and rollback planning. The inventory is complete when mappings, warnings, data scope, verified external copy and open issues are documented clearly.
Source: Microsoft: Virtualizing storage for scale, resiliency, and efficiency (2012).