Hi,
Have you checked the friendly name of the storage subsystem on which you are trying to create the storage pool? You can get the storage subsystems by running Get-StorageSubSystem.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have an exisiting three node HyperV cluster with storage provided by an S2D storage pool across the three nodes. The existing nodes are all Dell servers of various ages, two R740's and an R750. One of these nodes is now coming to end of life so I am trying to replace this and expand to a four node cluster.
Two new hosts, Dell R760s, have been added to the cluster and new storage drives added to these two and one of the existing nodes. I am now attempting to create a new storage pool using the new storage drives in these three hosts and running into errors.
Cluster validation has been run, including the Storage Spaces Direct checks. there are no failures reported from the cluster validation. There are a couple of warnings. These are related to a different number of physical drives being connected to different hosts and a legacy network.
Get-PhysicalDisk -CanPool $true
The above returns the 24 new storage drives, 8 on each of the three hosts. So i try to create the new storage pool witht the following:
$Disks = Get-PhysicalDisk -CanPool $true
New-StoragePool -StorageSubSystemFriendlyName "Cluster*" -FriendlyName "S2D_SSD_2" -ProvisioningTypeDefault Fixed -PhysicalDisks $Disks
This initially looks like it is doing something, but then returns the error:
New-StoragePool : Object Not Found
Activity ID: {5178898e-36e4-0000-b38b-6d55e436db01}
At line:1 char:1
+ New-StoragePool -StorageSubSystemFriendlyName "Clustered Windows Stor ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (StorageWMI:ROOT/Microsoft/...torageSubSystem) [New-StoragePool], CimExcep
tion
+ FullyQualifiedErrorId : StorageWMI 8,New-StoragePool
I have been unable to find anything in the event logs corresponding to this.
Trying to create the storage pool using the disks in any two of the nodes results in the same error. Nodes have been evicted and rejoined to the cluster.
Any advice on how to move forward and get the storage pool created?
Thanks
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
Hi,
Have you checked the friendly name of the storage subsystem on which you are trying to create the storage pool? You can get the storage subsystems by running Get-StorageSubSystem.
Hi,
Have you checked the friendly name of the storage subsystem on which you are trying to create the storage pool? You can get the storage subsystems by running Get-StorageSubSystem.
Yes. I have checked that and run the command again with the full friendly name of the storage subsystem. Same result.
What if you use the unique ID to specify the storage subsystem?
New-StoragePool -StorageSubSystemUniqueId "..."
Also see if the Storage SubSystem object works
$StorageSubSystem = Get-StorageSubSystem New-StoragePool -InputObject $StorageSubSystem -FriendlyName "S2D_SSD_2" -ProvisioningTypeDefault Fixed -PhysicalDisks $Disks
Thank you for the suggestion.
Unfortunately, this give the same result.
New-StoragePool -InputObject $StorageSubsystem -FriendlyName "S2D_SSD_2" -ProvisioningTypeDefault Fixed -PhysicalDisks $Disks
New-StoragePool : Object Not Found
Activity ID: {5178898e-36e4-0000-b38b-6d55e436db01}
At line:1 char:1
+ CategoryInfo : NotSpecified: (StorageWMI:ROOT/Microsoft/...torageSubSystem) [New-StoragePool], CimException
+ FullyQualifiedErrorId : StorageWMI 8,New-StoragePool