Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when running the command New-VirtualDisk, when using the create script #13

Open
EthanScully opened this issue Dec 5, 2024 · 1 comment

Comments

@EthanScully
Copy link

For some background, I am using a simple single ssd and single hdd caching tier.
I am running Windows 11 Pro, Version: 23H2 Build: 22631.4541, which should be the latest version of mainstream windows.

Regarding the new-storage-space.ps1 script, when running the segment:

New-VirtualDisk -StoragePoolFriendlyName $StoragePoolName -FriendlyName $TieredDiskName -StorageTiers @($SSDTier, $HDDTier) -StorageTierSizes @($SSDTierSize, $HDDTierSize) -ResiliencySettingName $DriveTierResiliency -AutoWriteCacheSize -AutoNumberOfColumns 

it gives the error The value for PhysicalDiskRedundancy is outside of the supported range of values., where I will have to add the argument to the above command: -PhysicalDiskRedundancy 0
then after the corrected command, I get the error, The value for NumberOfDataCopies is outside of the supported range of values., where I will have to add the argument: -NumberOfDataCopies 1
after adding these two arguments, the command runs successfully, and I am able to complete the script successfully.

Those two arguments have default values that are inherited from the ResiliencySettingName Simple argument, where I used simple do to my configuration.

Anyway I just wanted to tell you all that there might be an issue with new versions of windows.

For more information regarding the command, I'll leave this link here:
https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/createvirtualdisk-msft-storagepool

@freemansoft
Copy link
Owner

I wonder if this is because you only have one of each so there are no copies and there is no redundancy.

Thanks for posting your solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants