VMware Cloud Community
sergefeldmansky
Contributor
Contributor

Error converting Windows 2008 R2 Server with two disks

Hi,

I am trying to convert a Windows 2008 R2 Server that has two drive (C:\ drive is 80 GB and D:\ drive 1 TB). This machine is residing on ESX4.0 server and its production server so I can't afford shutting it down.

I am using converter 5.0 standalone and converting it to vSphere 5. Covvertion starts normally and successfully converting C:\ drive, but when it tryes to convert drive D:\, it fails after 30 seconds with following error:

[02160 info 'Default'] [task,379] [task-88] -- ERROR -- Convert: converter.fault.CloneFault
--> (converter.fault.CloneFault) {
-->    dynamicType = <unset>,
-->    faultCause = (vmodl.MethodFault) null,
-->    description = "BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[BE-E3-35-90-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)",
-->    msg = "",
--> }

I am attaching full log files just in case.

I already run diskcheck (didn't found anything), dissable all services, uninstall and resinstall converter agent, still getting the same error at exactly the same time.

Does anyone has any other ideas on what I can try.

Thank you in advance.

Serge

Reply
0 Kudos
17 Replies
kjb007
Immortal
Immortal

There were errors relating to invalid partition in the log.  Can you convert the vm selecting only the c: drive and see if the converted vm will boot, or at least the conversion will complete?

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
ivivanov
VMware Employee
VMware Employee

The error code indicates a network error between the source and host holding the target VM. Looking at the log archive there is no agent log bundle (Agent is installed on the source and it carries out the actual conversion and there is more information about what is happening). I suggest you switch the GUI to task view, select the failed cloning task, right click on it and try again to export the log bundle.

For other suggestions I would say to try converting *only* volume 😧 just to see is it failing again at the same point? BTW is it failing in the beginning of cloning 😧 or at a later point after some data from 😧 has been already transferred?

I would also suggest ot set the logging level on Worker (on Converter Server machine) and Agent (on the source) to verbose. For more information about how to change logging levels you can look at http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2008019.

__________
It is worse!
Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

I did convertion and it completed succesfully.

Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

To ivivanov

I did and attached the bundle to my original post. I can go to the source server and attached agent file that way. The clonning of D drive fails about 30 seconds into it. I tryed to convert D drive by itself and it went to about 10% and then I stopped.

I will change loggining level and rerun the job. I will attach the log files assson as I am done.

Serge

Reply
0 Kudos
ivivanov
VMware Employee
VMware Employee

I looked at the attached log bundle but there are no agent logs in it. Did you export logs while the GUI was in jobs view? In this case only server and worker logs are included in the bundle. My suggestion was to switch the GUI to *task* view, select the failed task and export the logs for the *task* again from the context menu. There is already a log bundle created for the failed task as seen from the worker log:

2012-03-31T11:01:16.391-07:00 [01688 info 'Default'] [Converter.Worker.DiagnosticManagerImpl] Created log bundle "task-6-bwwfabtz.zip" with size "194992" and CRC "-608756037"

but it is not included in the archive you have posted, which makes me think you have exported logs while the GUI has been in Jobs view.

__________
It is worse!
Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

Yes you are right, i was in Job view. Attached is the log bundle created in Task view.

Reply
0 Kudos
ivivanov
VMware Employee
VMware Employee

So the error seems to happen when starting cloning of volume D:. For some reason network connectivity fails when trying to open the second disk for writing. I don't have an idea what could be causing this.

One more experiment that comes to my mind - can you try to shrink volume 😧 on the target if the drive is not filled up (in case the problem is somehow related with the 1 TB size of the disk)? If there are e. g. only 500 GB of data, you can create a 500 GB target disk and if it works you can expand it later. Just an idea, I don't know if it is going to actually work since I am not able to identify the reason for the failure...

__________
It is worse!
Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

i am running another convertion with a verbose setting. Maybe it will give us more info on what is going on. If it fails, I will try your idea with shrinking drive D although if I do D by itself, conversation running without hickups.

Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

Did another conversion. Failed at the same spot. I am attaching a vebose log. Hopefully someone can figure this out.

Reply
0 Kudos
ivivanov
VMware Employee
VMware Employee

Another wild guess - can you try to disable SSL encryption over data channels? Instructions how to do it can be found at http://communities.vmware.com/thread/333786.

__________
It is worse!
Reply
0 Kudos
kjb007
Immortal
Immortal

Does your d: drive contain appliation installation files, or purely data?

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
continuum
Immortal
Immortal

just my 2 cents ....
I would declare defeat and use robocopy to move the data in case thats possible


________________________________________________
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
kjb007
Immortal
Immortal

That's what I was leading to as well.  As long as the C was successful, D can be copied fairly easily.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
sergefeldmansky
Contributor
Contributor

I am close to decalring defeat Smiley Sad One more try with SSL dissable and then DoubleTake to the rescue.

I would still like to know why I can convert C:\ and D:\ by itself but not together.

Does anyone know if I use two separate volumes and then combine them together, will it work?

Reply
0 Kudos
continuum
Immortal
Immortal

> Does anyone know if I use two separate volumes and then combine them together, will it work?

You do not really want to do that. With Windows VMs the most troublefree approach is to use one vmdk per partition or driveletter.
This way you can expand vmdks easier , you can easily switch datadisks to another VM, .... lots of advantages ...


________________________________________________
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
patanassov
VMware Employee
VMware Employee

It might be possible to success if you combine the 2 volumes on a single vmdk on the destination (with the inconveniences continuum mentioned). The log shows that the nfc tickets for both disks have been taken in the beginning. Eventually the ticket for the second disk may have timed out during the cloning of the first volume (no guarantee, just a guess).

HTH

Plamen

Reply
0 Kudos
gparker
Enthusiast
Enthusiast

Hi all,

I've just experienced a similar issue, i.e., "BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[59-4E-26-28-00-7E-00-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)".


I'm running Converter Standalone v5.1.0 Build 1087880 and when I attempted to P2V a Windows 2003 server with a C: and 😧 drive, the C: drive completed successfully and then it failed as it started the 😧 drive. The speed of the P2V was *EXTREMELY SLOW*, I'm talking 566KB/s!!! After reading through all these posts, I disabled the SSL encryption as per Re: Increasing the cloning performance and that fixed my problem. The physical server I'm converting is a very old Proliant model and I'm thinking that its CPU just couldn't handle the load from the encryption.


Thanks,

George.

Reply
0 Kudos