New-StoragePool

The New-StoragePool cmdlet creates a new storage pool using a group of physical disks, and a specific storage subsystem exposed by a storage provider.

This line uses the **Get-PhysicalDisk** cmdlet to get all PhysicalDisk objects than are not yet in a (concrete) storage pool, and assigns the array of objects to the $PhysicalDisks variable.
PS C:\> $PhysicalDisks = (Get-PhysicalDisk -CanPool $True)

This line creates a new storage pool using the $PhysicalDisks variable to specify the disks to include from the Storage Spaces subsystem (specified with a wildcard * to remove the need to modify the friendly name for different computers).
PS C:\> New-StoragePool -FriendlyName CompanyData -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks

This example creates a new storage pool named CompanyData using the Storage Spaces subsytem, using the minimum parameters, and assuming that there are no other storage subsystems attached to the computer that have available disks.

PS C:\> $PhysicalDisks = (Get-PhysicalDisk -CanPool $True)
PS C:\> New-StoragePool -FriendlyName CompanyData -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks -ResiliencySettingNameDefault Mirror -ProvisioningTypeDefault Thin -Verbose

This example creates a new storage pool named CompanyData using the Storage Spaces subsystem and sets default values for virtual disk creation.

The first line ([CODE_Snippit]$PhysicalDisks =[CODE_Snippit]…) gets the storage subsystem object for the Storage Spaces subsystem, passes it to the **Get-PhysicalDisk** cmdlet, which then gets the physical disks in the specified subsystem that are available to add to a storage pool, and assigns these disks to the $PhysicalDisks variable.The second line of the command has five parts, connected by the pipeline (|). The first part ([CODE_Snippit]New-StoragePool[CODE_Snippit]…) creates a new storage pool using the physical disks in the $PhysicalDisks variable, and then passes the new storage pool down the pipeline. All of the following commands are logically part of one command and should be entered as such.The second part ([CODE_Snippit]New-VirtualDisk[CODE_Snippit]…) creates a new virtual disk on the passed in storage pool and then passes the new virtual disk down the pipeline.The third part ([CODE_Snippit]Initialize-Disk[CODE_Snippit]…) initializes the disk that was passed in, and then passes the disk down the pipeline.The fourth part ([CODE_Snippit]New-Partition[CODE_Snippit]…) creates a new partition on the disk that was passed in, assigns it the next available drive letter, and then passes the partition down the pipeline.The final part of the command ([CODE_Snippit]Format-Volume[CODE_Snippit]) formats the partition that was passed in.
PS C:\> $PhysicalDisks = Get-StorageSubSystem -FriendlyName "Storage Spaces*" | Get-PhysicalDisk -CanPool $True 
PS C:\> New-StoragePool -FriendlyName "CompanyData" -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks |New-VirtualDisk -FriendlyName "UserData" -Size 100GB -ProvisioningType Thin |Initialize-Disk -PassThru |New-Partition -AssignDriveLetter -UseMaximumSize |Format-Volume

This example creates a new storage pool, and then makes use of the pipeline to create a new virtual disk in the pool, initialize the disk, create a new partition on the disk, and then format the new partition (volume). Alternatively you can use the New-Volume cmdlet to achieve a similar result in a single command.

CimInstance

You can use the pipeline operator to pass one or more MSFT_PhysicalDisk objects to the PhysicalDisks parameter.

CimInstance

You can use the pipeline operator to pass an MSFT_StorageSubsystem object to the InputObject parameter.

CimInstance

This cmdlet returns an object representing the newly created storage pool.