Spaces: Could not create storage pool. One of the physical disks specified is not supported by this operation

Question

_{Monday, September 3, 2012 12:47 PM}

i'm using the Windows Server 2012 Virtual Lab to investigate how stable Storage Spaces are.

When trying to create a Storage Pool i get the error:

Could not create storage pool. One of the physical disks specified is not supported by this operation.

This happens no matter which, or what combination of disks (empty, dynamic, Guid Partition Table) i choose.

And while we're on the subject of a lack of documentation, what is a Manual allocation (as opposed to a Data Store allocation, or a Hot Spare allocation)?

Edit: My question, just to be clear:

- what are the characteristics of a physical disk that are required for it to support this operation?

• where do i check those current characteristics?
• how do i change those characteristics so that they are supported by the current operation?

Note: This error happens when creating a storage pool. We're not even at the point yet where we choose the kind of Provisioning (Thin Provisioning or Fixed), or the kind of Layout (Simple, Mirror, Parity).

All replies (4)

_{Tuesday, September 4, 2012 4:35 AM ✅Answered}

Hello, 

I suggest you go through this FAQ once.

• What types of drives can I use with Storage Spaces?
  You can use commodity drives attached via Serial-Attached SCSI (SAS), Serial ATA (SATA), or USB. Storage layers that abstract the physical disks are not compatible with Storage Spaces. This includes VHDs and pass-through disks in a virtual machine, and storage subsystems that layer a RAID implementation on top of the physical disks.

The same you can find in:http://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx

Regards, Ravikumar P

_{Monday, September 24, 2012 2:24 AM}

> using the Windows Server 2012 Virtual Lab

_{Thursday, August 27, 2015 11:54 PM | 3 votes}

This error message will appear when creating a storage pool on a clustered node.

Destroying the cluster will probably get rid of this error - assuming this is a lab environment.

_{Sunday, February 7, 2016 1:57 PM}

If you are using GUI, visit the CluAdmin console & remove the Pool & Disks from underneath the cluster and it should go good.

yup