Thanks for the tutorial but unfortunately its not possible for me to change the space size. I really hope you are able to assist as the techs from Microsoft support are scratching their heads...

I had 2 x 8tb HD's installed when i made a pool (drive D) using storage spaces. After some time i had to add an extra HD because disk space was getting low. So i bought the exact same brand/type/size HD and i added it to the pool.

Unfortunately as you can see, for some reason i cant change the size of the pool to the 21.8tb which it is supposed to be.

The strange thing is, is that in windows explorer the D drive also does not show the correct maximum amount of storage space. This is also the case in Disk Manager but when i installed the extra HD, i first added it by using Disk Manager before continuing with Storage Spaces and adding it to the pool.

I also did the 'upgrade group' option so ignore that message in the screenshots and im using W10 version 1909

Yes, and when i try to change the size per your tutorial i get this message;

storage space cannot be extended because the number of clusters will exceed the maximum number of clusters supported by the file system

Unfortunately i have no clue to what this means and how i am able to resolve without losing data. Can you help?

thanks for your help and explanation. I will backup all my data and then see if this 3rd party software works, Minitool Partition Wizard as they claim its possible through their software to change the clustersize, without formatting.

If that does not work i will start from scratch

I have a similar problem, but as my storage pool is well below 16TB (2.85TB, in fact) it cannot be to do with the cluster size.

Being new to storage spaces I decided to experiment with a simple setup: three physical disks of different sizes, all wiped and cleaned to an uninitialized state. I couldn't use the Manage Storage Spaces control panel applet to create the storage pool, as it gave an 0x0000...57 error, so I used PowerShell instead, following the Microsoft documentation:

Code:

$PhysicalDisks = (Get-PhysicalDisk -CanPool $True)
New-StoragePool -FriendlyName MyStoragePool -StorageSubsystemFriendlyName "Windows Storage on Vera" -PhysicalDisks $PhysicalDisks -ResiliencySettingNameDefault Simple -ProvisioningTypeDefault Fixed -Verbose

This worked without errors, and the storage pool appeared in Manage Storage Spaces. I then created a new volume/storage space, specifying UseMaximumSize:

Code:

New-Volume -StoragePoolFriendlyName "MyStoragePool" -FriendlyName "MyVolume" -ResiliencySettingName "Simple" -FileSystem NTFS -AccessPath "M:" -ProvisioningType Fixed -UseMaximumSize

This also worked without errors, and I can access the new drive M: in Windows. However, not all the space is being used – MyVolume is only 1.75TB out of the storage pool's 2.85TB. I expected the size to be slightly smaller, but not so much smaller using Simple resiliency (i.e. none).

If I try to increase the size of the volume in Manage Storage Spaces, even by a very small amount, it fails with the error "Can't change the storage space: not enough available capacity".

Is this expected behaviour, and if so, why is there so little usable capacity? Or is there an actual problem with my setup, in which case how can I overcome it?

I am attaching a screenshot of the Manage Storage Spaces dialog:

Thanks. That seems unlikely, as the MS article says the problem is specifically with Parity storage spaces and that Mirror and Simple spaces are not affected (mine is Simple). However, the machine in question has been upgraded to 2004, so I suppose there could be some other bug. Can you confirm that the behaviour I'm seeing is abnormal/faulty?