Windows 10: Storage Spaces on WIndows 11 For Workstation says New-VirtualDisk is not supported.

So Ive used storage spaces plenty in the past and never had issues, but this is my first time trying to use it on Windows 11 for Workstation, so maybe something is different now with what you can do? I made my storage pool just fine, but I go to create the virtual disk with the settings I want and it is giving me an error that New-VirtualDisk isnt a supported command? I know normal Windows 11 doesnt support many Storage Spaces commands or ReFS which is why I paid extra for the For Workstation edition, which should give me access to these things I wanted. I quadruple checked the spelling of the

:)

 

Unable to increase size of storage space

Hello, f1sherman

Welcome to the Microsoft community.

I understand that you are experiencing problems with the storage space not changing, you can try the following:

Search for PowerShell in the Start menu and select "Run as administrator"

You can list all storage pools and their associated storage using the following command

Check the size of the storage pool and how much space is allocated. This information can help you determine how much storage space you can expand.

You can use the following command to view the details of a specific storage pool (replace "YourStoragePoolName" with the actual name of the pool):

After determining how much storage you want to expand, use the Resize-VirtualDisk cmdlet. replace "YourStorageSpaceName" with the name of the storage space and specify the new size. For example, to resize a storage space named "MyStorageSpace" to 3TB, use the

Note: Ensure that the specified size is not larger than the available space in the storage pool.



Verify the changes. After resizing, you can verify that the size of the storage space has been updated using the same command you used in step 2.

Remember to back up any important data before changing the storage configuration to avoid data loss.

Storage Spaces in Windows - Microsoft Support

Please let me know if you have any other questions or if I haven't explained something clearly.

Best Regards,

Aaron- MSFT | Microsoft Community Support Specialist

 

Windows 10 Storage Spaces Mirrored VirtualDisk crashed after single HDD failure

I have suffered yet another fatal Storage Spaces crash after 1 of my 8 HDDs failed. I have a mirrored VirtualDisk which is 1TB and it become detached, lost communication with the failed PhysicalDisk HDD. I have 3 other mirrored VirtualDisks which are still
working fine. I cannot connect the unhealthy VirtualDisk and cannot repair the VirtualDisk. Windows 10 SS GUI will not automatically fix this issue, and Powershell commands have not worked. The only difference between the failed VirtualDisk and those that
are still running is that the failed VirtualDisk was evidently at almost 100% full, whereas the other VirtualDisks were about 60%. The PhysicalDisk that failed is Lost Communication. Evidently, SS tried to remove data off the HDD which started at about 60%
usage and was able to move data off to about 11% usage before the drive totally died.

I have added 2 additional HDDs so I now have 13 TB used out of 30 TB pool. I don't understand how a mirrored VirtualDisk in a pool of 8 HDDs can be taken offline and crash from a single HDD failure. In theory, should there not be a second, complete copy
of every file in the mirrored VirtualDisk?

If anyone has any idea of how to work around this failed HDD and get my VirtualDisk back online, at least long enough to move the files, I would be very thankful. Again, the failed PhysicalDisk is dead, not just unhealthy. The VirtualDisk is detached, unhealthy,
but I cannot get it back online.

 

Windows 10 Storage Spaces Improvements?

Here is an example where a 3-way mirror space named VDiskMirrorPS is created on an existing storage pool named Pool01

Archived MSDN and TechNet Blogs

New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Mirror -Size 200GB

-FriendlyName VDiskMirrorPS -ProvisioningType Fixed -NumberOfDataCopies 3 -NumberOfColumns 3

For a 12 column dual parity space his command would be:

New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Parity
-Size 200GB

-FriendlyName
MyNewParitySpace -ProvisioningType Fixed -NumberOfDataCopies 2 -NumberOfColumns 12

If you are unfamiliar with managing storage spaces via PowerShell I suggest you create some virtual disks (Disk Management > Create VHD) of sizes maybe 20GB-50GB and spend a long time researching and testing various dummy
storage space configurations. It is the easiest way to understand where the overhead comes from, what column size to choose, what happens when you mix disk sizes, how much space is gained when you add a new disk to the pool, etc.