582 replies to this topic

[erwan.l]

Sorry, but this version from today does not have .vhds available for creation/open

 

Until this is confirmed working, you have to enter the path like c:\temp\mydisk.vhds.

Once confirmed, in a future clonedisk version, the openfile dialog will then propose vhds next to vhd and vhdx (currently).

See this as a "hidden" beta feature for now : just for you

 

Currently, Clonedisk will detect, based on the extention, IF it needs to use VHDSET provider.

 

If the mydisk.vhds is created, then you got a winner - if not, clonedisk will moan about "missing provider".

[sebus]

Excellent!.

Works fine.

Ofcourse this cannnot be mounted/attached because Windows does not provide that option, but created set is perfectly usable while attached to VM on Server 2016+ Hyper-V

[erwan.l]

Excellent!.

Works fine.

Ofcourse this cannnot be mounted/attached because Windows does not provide that option, but created set is perfectly usable while attached to VM on Server 2016+ Hyper-V

 

Wow, lucky day  I was not too sure about what I was doing since no way to test and this format is totally new to me (not being too much of a server/system guy nowadays).

 

I will add VHDS as a choosable format in the dropdown lists then next to VHD and VHDX in next release.

[erwan.l]

I have uploaded a new version where VHDS will appear as a support VHD file.

 

I am unclear thus what you can do or not : create yes? mount? expand? merge? resize?

For now, VHDS appears in all screens.

 

EDIT : vmount (x32) also supports vhd, vhdx and vhds.

[sebus]

W:\temp>vmount createdynamic .\trial.vhds 127000
CreateVHD not ok:The parameter is incorrect

[sebus]

Clone volume to volume creates wrong volume size?

 

[erwan.l]

Clone volume to volume creates wrong volume size?

 

 

Uhm, not good...

Could it be that 222gb matches a numeric boundary (intteger, int64, etc).

Which "clone" function did you use? from the main screen? in the volume window? in the partition window?

222Gb would roughly be 238 370 684 928 bytes.

 

I'll run some tests using virtual dynamic disk (thus allowing me to simulate huge disks but in reality only taking a few mb on underlying disk).

[sebus]

That were physical disks

V-2-V from Volume section / Volume Names

 

That was V-2-V copy in WinPE

 

Once booted from that drive I could NOT expand (greyed out), I could Shrink, but only by 289Mb, but it failed each time with invalid parameter

 

In the end done disk clone & extend which worked fine