VMware Communities
Kevin_Pidd
Contributor
Contributor
Jump to solution

vmware-vdiskmanage Failed to convert disk: One of the parameters supplied is invalid (0x3e80)

vmware-vdiskmanage Failed to convert disk: One of the parameters supplied is invalid (0x3e80) when I try to convert preallocated disks to resizable on Windows guests. It works fine on linux guests. Command I an using is vmware-vdiskmanager -r IDM\ 45\ App\ Server-cl2.vmdk -t 0 IDM\ 45\ App\ Server-cl2-new.vmdk

Reply
0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

Bingo !
That will not work.
Follow my instructions to the letter please.
1. create a new empty directory
2. move "IDM 45 App Server-cl2-flat.vmdk" into that new directory
3. create new "IDM 45 App Server-cl2.vmdk"  inside the new directory with this content:

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=cad4bf9c

parentCID=ffffffff

createType="monolithicFlat"

# Extent description

RW 125829120 FLAT "IDM 45 App Server-cl2-flat.vmdk" 0

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.virtualHWVersion = "8"

4. run the command
vmware-vdiskmanager -r  "IDM 45 App Server-cl2.vmdk" -t 1 "new.vmdk"
after changing to the new directory


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

Reply
0 Kudos
6 Replies
continuum
Immortal
Immortal
Jump to solution

Depending on the WS version you may need to convert to "t 1" format if the source vmdk is larger than 2032GB.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Kevin_Pidd
Contributor
Contributor
Jump to solution

same error

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Can you post the descriptorfile for "IDM 45 App Server-cl2.vmdk" ?
If the descriptor is embedded you can extract it like this:
dd if="IDM 45 App Server-cl2.vmdk" of=descriptor.txt bs=1 skip=512 count=1024


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Kevin_Pidd
Contributor
Contributor
Jump to solution

Thanks

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=cad4bf9c

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 125829120 VMFS "IDM 45 App Server-cl2-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsisas1068"

ddb.deletable = "true"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "de7851fef3dd9cfe82a6a94ecad4bf9c"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "9410"

ddb.uuid = "60 00 C2 9b 92 76 d8 42-17 c7 cf 1f 93 a8 06 b2"

ddb.virtualHWVersion = "4"

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Bingo !
That will not work.
Follow my instructions to the letter please.
1. create a new empty directory
2. move "IDM 45 App Server-cl2-flat.vmdk" into that new directory
3. create new "IDM 45 App Server-cl2.vmdk"  inside the new directory with this content:

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=cad4bf9c

parentCID=ffffffff

createType="monolithicFlat"

# Extent description

RW 125829120 FLAT "IDM 45 App Server-cl2-flat.vmdk" 0

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.virtualHWVersion = "8"

4. run the command
vmware-vdiskmanager -r  "IDM 45 App Server-cl2.vmdk" -t 1 "new.vmdk"
after changing to the new directory


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Kevin_Pidd
Contributor
Contributor
Jump to solution

Thankyou!

That worked.

Reply
0 Kudos