search

FSLogix / Invoke-FslShrinkDisk

This script will shrink a FSLogix Disk to its minimum possible size
MIT License
155 stars 55 forks source link

The input name ""Type"" cannot be resolved to a property #20

Closed mkools closed 3 years ago

mkools commented 4 years ago

I'm getting this error on a lot of VHDX files:

"Profile_xxx.VHDX","Failed to read partition information for disk - ""The input name ""Type"" cannot be resolved to a property."

Any idea what it means? Or better yet, how to solve it? As it now doesn't shrink these disks. I get it on most disk files I think 70%.

JimMoyle commented 4 years ago

This is usually the case where the script is being run form an underpowered machine, the default number of threads is 8.

If you are having issues either add more and faster cores, or restrict the thread count to the number of cores you have. If you still see the issue set the throttle limit to 1 and see where that gets you.

mkools commented 4 years ago

Hi Jim, that makes sense. I will increase cpu power on the machine and try again.

Thanks for the quick response!

Artic6 commented 4 years ago

This is usually the case where the script is being run form an underpowered machine, the default number of threads is 8.

If you are having issues either add more and faster cores, or restrict the thread count to the number of cores you have. If you still see the issue set the throttle limit to 1 and see where that gets you.

I have tried this on a powerful server using 4 threads and get the same result, so I tried the new script in 1 thread and it still does not help......

Went back to the older script that actually did something.

mkools commented 4 years ago

This is usually the case where the script is being run form an underpowered machine, the default number of threads is 8. If you are having issues either add more and faster cores, or restrict the thread count to the number of cores you have. If you still see the issue set the throttle limit to 1 and see where that gets you.

I have tried this on a powerful server using 4 threads and get the same result, so I tried the new script in 1 thread and it still does not help......

Went back to the older script that actually did something.

It works for me setting it to 1 thread now.

It might have to do with the fact that my VHDX files are on a NetApp network share which limits the throughput. I'm not sure but for me it works with a single thread. It takes forever though but oh well :)

Artic6 commented 4 years ago

It works for me setting it to 1 thread now.

Agreed, but takes agesssssssssssssssssssssss