| Previous | Next |
| ERROR_SPACES_NUMBER_OF_COLUMNS_INVALID | ERROR_SPACES_EXTENDED_ERROR |
ERROR_SPACES_NOT_ENOUGH_DRIVES
The provider counts usable placement resources, not every visible disk
ERROR_SPACES_NOT_ENOUGH_DRIVES means the requested layout or operation cannot be completed with the physical disks currently eligible. A machine can show many disks and still lack enough candidates because some are allocated, retired, unhealthy, reserved for journal/cache use, incompatible, or located in the same fault domain.
The required count also depends on resiliency, copies, parity, columns, enclosure awareness, and repair state. Reducing the virtual-disk size will not help when the blocker is placement geometry rather than capacity.
Build an eligibility inventory
- List
CanPool,Usage, health, operational state, and allocated size for every disk. - Identify disks already claimed by another pool or storage subsystem.
- Count distinct enclosures or scale units required by fault-domain awareness.
- Include disks needed to preserve mirror copies or parity during the operation.
- Check sector-size and media/tier compatibility before counting a device.
- Do not reset or erase disks until their ownership and data significance are understood.
References
- Microsoft: New-StoragePool disk selection
- Microsoft: fault-tolerance requirements
- Microsoft: physical-disk states
Looking for a different code? Search another status or error code.