Join our community for more solutions or to ask questions. So I loaded the converter directly on the server itself - This fails instantly with "A general System error occurred: Unknown Error" ------------------------- trimmed log section with error --------------------------- 2012-06-10T23:40:05.932-07:00 [02488 Keith 0 Message Active 6 days ago Author Comment by:piaakit2013-11-17 i have fixed the problem, in the source physical server, i need to add the two esxi hostname and ip rebooted... http://prcflow.com/vmware-converter/vmware-converter-5-1-platform-specific-error-2338.html
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2018582&sliceId=1&docTypeID=DT_KB_1_1&dialogID=325909453&stateId=0%200%20325915661I also found this blog post that mentions that changing the network speed fixed it: http://geekcubo.com/2011/11/vmware-converter-failed-clone-volume-c I would also run a chkdsk on the source machine. 0 The time to complete is calculated on current transfer speed, it is possible that after hours of working the speed and time to complete to be changed dramatically. Join Now Trying to get an old 2003 Server to Virtualize via VMWare Converter. Join the community of 500,000 technology professionals and ask your questions.
http://communities.vmware.com/message/6186630 Habanero OP B-C Jun 14, 2012 at 12:10 UTC all disks are basic... did notice that I did have both the agent and full converter When I try converting just the C:\ into a vmware workstation virtual machine and then onto the esxi host, no problems. Get 1:1 Help Now Advertise Here Enjoyed your answer? permalinkembedsaveparentgive gold[–]Gatorvi[VCP] 0 points1 point2 points 1 year ago(0 children)I am very happy with 5.5 using it 2-3 times a week lately permalinkembedsaveparentgive goldaboutblogaboutsource codeadvertisejobshelpsite rulesFAQwikireddiquettetransparencycontact usapps & toolsReddit for iPhoneReddit for Androidmobile
When you say there is a warning about this type of transfer, what do you mean? It may not be a limitation of the converter, but actually your version of vSphere with the 2TB limit. 5.5 removed the 2TB limit with the VMFS5. This time I received the error below. It is still at 5.1.
FAILED: An error occurred during the conversion: 'Platform-specific error 2338' VMWare p2v coversion fails at 1 % 0 Question by:piaakit Facebook Twitter LinkedIn Google LVL 34 Active today Best Solution byMahesh One issue is that on the destination storage I didn't have 1.6TB available, so I had to resize the volume. FAILED: An error occurred during the conversion: 'Platform-specific error 2338' I Googled that error and found this article. https://kb.vmware.com/kb/2018582 I noticed that you said you tried converting the disks individually to VMware Workstation - but have you tried them individually to the ESXi host (skipping the Workstation)?
VMware Tools are a suite of utilities that enhances the performance of the virtual machine's guest operating system and improves management of the virtual machine. The converter is installed on dedicated VM with external NIC that is reachable from the remote location and internal NIC that is connected to the vcenter and the ESXi hosts. permalinkembedsavegive gold[–]Moocha 0 points1 point2 points 1 year ago(1 child)Don't worry about that, unfortunately hal009 was less than ideally informed (see my reply to the comment.) Use Converter 5.5 like others have pointed We ended up converting the server with just the C: drive (to make it bootable) but left space for the D: and E: in the virtual disk (you have to adjust
I ended up converting with the C: drive only and then doing a robocopy to a "new" D: drive that I presented to the VM. 1 Jalapeno OP check my blog I can't remember exactly what, but it just didn't work. You could try cold cloning? 0 Mace OP Denis Kelley Jun 14, 2012 at 10:11 UTC In the error above, I see a note on dynamic disks. As for your error, were you ever able to rectify them?
If you make a post and then can't find it, it might have been snatched away. This is with SSL enabled. As for the drives that I am not sure of, I would assume dynamic because they are on dynamic disk but not sure. http://prcflow.com/vmware-converter/vmware-converter-platform-specific-error-18.html Are the drives basic or dynamic?
I can't remove and re-add the ESXi hosts since they have several VMs with FT enabled, but I can't imagine that is even the issue as all thumbprints were accepted. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs). It feels good to keep my guts this time! George1421 wrote: Hey, I'm glad you got it to migrate. Join Now I am in the process of converting 2 physical servers into virtual server using tghe latest vmware converter.
Join the community Back I agree Powerful tools you need, all for free. You can not post a blank message. http://www.experts-exchange.com/Software/VMWare/Q_28296452.html For anyone without an EE account, he was getting the same error with 5.1. http://prcflow.com/vmware-converter/failed-an-error-occurred-during-the-conversion-39-platform-specific-error-2338-39.html permalinkembedsaveparentgive gold[–]killer833 2 points3 points4 points 1 year ago(0 children) A General System Error Occurred: Platform Specific Error 2338 google says its converter 5.1 that doesnt support >2TB disks.
Join & Ask a Question Need Help in Real-Time? Covered by US Patent. Was a DC - Moved all roles DC,DNS,DHCP to another DC already Virtualized C:
I had to roll back a version or two. Will you re-paste it. 0 Jalapeno OP bmeiont Jan 16, 2013 at 5:17 UTC Warrior5Delta wrote: I noticed in the error about block size? while setting up I found an old ESXi host that isn't attached to vCenter and so far it looks like the data is copying. then re-installed converter standalone...
Any ideas other than supposedly removing and re-adding the ESXi hosts into vCenter? For this particular V2V, I had to resize the volume and make it a thin from thick, so I realize a slower file level copy is taking place instead of a Windows 2003 to be converted, and because you VM is using an old OS, you may need to downgrade the vCenter Converter Standalone 5.5, to 5.0. 0 Message Active 6 Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts His fix was to add the IP address and ESXi
c:\ and d:\. When we booted the cloned server it threw some errors about missing disks, but it booted. The issue is observed with Windows XP Professional 64-bit, without any service pack, and might be present in other versions of Windows XP or Windows Server 2003 as well. tricky but will try that one as well hopefully this weekend?
How could I tell? How could I tell? Download 5.5 and give it a go. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try
I also changed the useSSL on the Converter VM to "false". Quoth KB2003813: Frequently Asked Questions on VMware vSphere 5.x for VMFS-5: VMFS5 in ESXi 5.5 now supports upto 62 TB VMDK and non-passthrough RDM. Thanks for pointing that out! 0 Jalapeno OP bmeiont Jan 16, 2013 at 5:03 UTC _Justin_ wrote: What version of the Converter are you using? I saw that those errors are mentioned with Converter 4.3, but I'm using Converter 5.1 The source VM is Windows 7SP1 Attaching the log for more information.