Get-PhysicalExtent Fails on Virtual Disks Larger Than 3TB

Question

I am trying to discover the extent size of a virtual disks and when ever I use Get-PhysicalExtent on a virtual disks larger than 3TB, it fails. Anyone know why?

PS C:\Windows\system32> Get-VirtualDisk ps01

FriendlyName ResiliencySettingName FaultDomainRedundancy OperationalStatus HealthStatus Size FootprintOnPool StorageEfficiency

---

---

PS01 OK Healthy 10 TB 30 TB 33.33%

PS C:\Windows\system32> Get-PhysicalExtent -VirtualDisk (Get-VirtualDisk -FriendlyName ps01)
Get-PhysicalExtent : Failed
Activity ID: {52dc12f6-a925-0025-2fc4-de5225a9d801}
At line:1 char:1

• Get-PhysicalExtent -VirtualDisk (Get-VirtualDisk -FriendlyName ps01)
• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
• CategoryInfo : NotSpecified: (:) [Get-PhysicalExtent], CimException
• FullyQualifiedErrorId : StorageWMI 4,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand,Get-PhysicalExtent

Answer 1

Hello @Jim Gandy ,

Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.

I think only pooled storages would work with the Get-PhysicalExtent command and not the actual physical disks that are local to the machine.

Below is the output from my local machine when attempting to get the output for my physical disk.

Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Answer 2

Sorry I did not clarify. I am using the Get-PhysicalExtent on a Azure Stack HCI (S2D) cluster node as shown in the screenshot below.

Answer 3

I just checked my AzHCI cluster with the latest updates, still an issue.

Answer 4

Hi Jim,

I realize this is a rather old post, but it popped up in the list due to the question being edited. I figured I would provide an answer for others that may view this later.

It would appear this is happening due to the fact the volume is using storage tiers. You can tell this from the output above because the ResiliencySettingName and FaultDomainRedundancy columns are blank. This is likely due to the fact that the volume was created using Windows Admin Center which creates all volumes as tiered volumes. You can view the settings for the volume using Get-StorageTier.The Get-PhysicalExtent command does have an option to pass a storage tier, but this option was not working for my testing.

If I run the same command on a volume that was not created as a tiered volume, it works without issue.

If you have learned anything since this question was first posted, please respond and provide your update.

Hope this helps!