VMware Cloud Community
JaeJa
Contributor
Contributor
Jump to solution

Conversion to ESXI format fails - Error 23

Hi all,

I am trying to convert a VMWare server instance to an ESXI instance using the vCenter Converter Standalone. The tool cannot obtain the hardware information for the selected system. I tried a lot of different things, including opening the VM in VMWare Fusion and assigning a different OS type, rebooting it several times, creating a new snapshot, checking permissions and more.
The most recent error message I get from the tool is:
2013-02-27T04:56:32.315-08:00 [02116 info 'Default'] Creating vmx file parser
2013-02-27T04:56:32.315-08:00 [02116 info 'Default'] [BaseParserImpl::Parse] Config info is not cached
2013-02-27T04:56:32.317-08:00 [02116 info 'Default'] Parsing \\vm-nas\USBDisk2\DLP 11.6 VMs\Enforcedemo_V11.1\Enforcedemo_V11.vmx
2013-02-27T04:56:32.366-08:00 [02116 warning 'Default'] Invalid serial port file type thinprint
2013-02-27T04:56:32.972-08:00 [02116 info 'Default'] [,0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'The parent of this virtual disk could not be opened' (error code:23)
2013-02-27T04:56:32.972-08:00 [02116 info 'Default'] [,0] Error 23 opening disk \\vm-nas\USBDisk2\DLP 11.6 VMs\Enforcedemo_V11.1\Enforcedemo_V11-000002.vmdk.
2013-02-27T04:56:32.972-08:00 [02116 info 'Default'] [,0] Error 23 opening disk \\vm-nas\USBDisk2\DLP 11.6 VMs\Enforcedemo_V11.1\Enforcedemo_V11-000002.vmdk.
2013-02-27T04:56:32.972-08:00 [02116 error 'Default'] [BaseDiskSetComputer::DoOpen] OpenDisks failed, mntapi error: 370
2013-02-27T04:56:32.972-08:00 [02116 error 'Default'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 370 MNTAPI errorType = 2, errorCode = 23
2013-02-27T04:56:32.972-08:00 [02116 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2013-02-27T04:56:32.972-08:00 [02116 error 'Default'] Unknown exception while invoking VMOMI method queryComputerInfo
2013-02-27T04:56:41.137-08:00 [05048 info 'Default'] [Converter.Worker.DiagnosticManagerImpl] Generating LogBundle.
I think the problem here is Error 23, "The parent of this virtual disk could not be opened". Does anyone have an idea about how I can fix this?
Any help would be greatly appreciated.

Andreas.

0 Kudos
1 Solution

Accepted Solutions
POCEH
VMware Employee
VMware Employee
Jump to solution

When you run the VM not *full* disk is read (or written) but the Converter reads *full* disk, that's why you can run the VM without error or untill you try to use broken place. Do the copy of VM at other place and try again. HTH

View solution in original post

0 Kudos
5 Replies
vmroyale
Immortal
Immortal
Jump to solution

Hello and welcome to the communities.

Note: Discussion successfully moved from VMware ESXi™ 4 to Converter

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Error means "Data error (cyclic redundancy check)."

Check the VM copy.

HTH

JaeJa
Contributor
Contributor
Jump to solution

Thanks for your quick reply, POCEH.

Let me give some more background information. The VM is on an external USB drive and I can boot the VM fine once connected to my laptop.

I use Converter from within a different VM with the USB drive connected to a QNAS networked storage device. I successfully converted another VM that was on the same drive this way. Can you give me a tip on what I can do to verify the VM copy, other than booting it and making sure that it runs without problems on my VMware Fusion?

0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

When you run the VM not *full* disk is read (or written) but the Converter reads *full* disk, that's why you can run the VM without error or untill you try to use broken place. Do the copy of VM at other place and try again. HTH

0 Kudos
JaeJa
Contributor
Contributor
Jump to solution

Thanks again POCEH. I found out that it's related to how the USB drive is connected to the NAS. I connected it to a laptop instead and now it's transferring. I think that somehow converter cannot access the vmdk the same way when it's connected via a NAS, as when it's connected straight to a laptop.

0 Kudos