Hello everyone,
I want to do a P2V of a Windows NT4 to a VM but I have a problem.
When the wizard (VMware Converter v3.0.3-89816) is at the step "Verifying destination parameters" (when you select the datastore) there is a Unknown error :
I have all prerequisites : NT4 SP5, IE5.
I join the log file. I have read it but I didn't find anything to help me.
Thanks
Is there a drive O mapped to a network drive in the Windows NT 4 machine?
[#4] [2017-05-03 15:32:32.031 'App' 371 verbose] [attachedComputerWin32,649] [GetVolumesForComputer] volume O: corresponds to \Device\LanmanRedirector\O:\10.20.65.10\maxita device name.
[#4] [2017-05-03 15:32:32.031 'App' 371 warning] [attachedComputerWin32,759] [GetVolumesForComputer] Windisk_GetVolumeDeviceNumber for O: returned with error code 5 and device type 0
Assuming error code 5 is a Windows error code; it would mean "Access Denied".
Try unmapping this NT network drive.
Is there a Drive R that is a CDROM drive?
Can you disable the CDROM drive?
Thanks for your response.
So I disabled the mapping of the drive O:
But when I try again the P2V i have the same error and now in the log it's the drive R: which is the CD-ROM drive. But I did'nt find a way to disable it...
It's been almost 20 years since I have had to use NT 4.0; so it's a hard to recall how to properly disable a CDROM drive. It's funny though because I used to re-assign the CDROM drives with letter "R" also during the NT4.0 days.
I suggest maybe remount it because it is still looking for an R drive.
[#5] [2017-05-03 16:45:50.921 'App' 199 verbose] [attachedComputerWin32,649] [GetVolumesForComputer] volume R: corresponds to \Device\CdRom0 device name.
[#5] [2017-05-03 16:45:50.921 'App' 199 verbose] [attachedComputerWin32,726] [GetVolumesForComputer] Retrieving R: volume's device number as an alternative to retrieving volume extents typically for NT4 sources or to filter out cdrom devices.
[2017-05-03 16:45:50.937 'App' 201 info] [stub,42] error [Windisk_CheckNonFixedMediaDevice] Failed to retrieve media type for R:: Fonction incorrecte (1)
How about to disable it from the BIOS?
As to the network drive O, it would be better to ask the owners/users of this NT4.0 system whether they need that remap after this is virtualization is complete as there might be applications that need that mapping but it just so happened the correct credentials were not given to you for security reasons.
If there is no option to disable CDROM in BIOS or if the disable of CDROM still does not let you proceed;
Look for something in Control Panel - SCSI Drivers, see if you can stop a driver such as ATAPI CDROM.
I would AVOID disabling the driver.
I don't know if you had work on NT4.0 systems before; but it can be easy to mess things up and just cause everything to BSOD during boot (or maybe I was just good at messing things up and creating BSODs :smileylaugh:
Hi,
This morning I tried to do the P2V with a different destination. This time the host has an old version of ESX : ESX4.1 (yesterday it was on a host ESX5.5)
And this time i was able to start the convertion.
But it failed after 2% with this error :
The free space on the partitions :
It's a single disk of 8Go with 2 partitions.
Partition C: is a FAT volume.
Partition 😧 is a NTFS volume.
I attach the log too.
Thanks.
Looks like this has progressed a little bit further as it started to take snapshot and it failed.
[#6] [2017-05-04 09:46:40.781 'App' 211 verbose] [snapshotVolumeVSNAPWin32,127] Snapshotting \\.\C: using stcbasic.sys
[#6] [2017-05-04 09:46:40.781 'App' 211 error] [snapshotVolumeVSNAPWin32,137] stcbasic.sys not installed or snapshot creation failed. err=2
I also see quite a few SSL certificate errors that is basically mismatch between presented name and the name in the certificate but don't know enough whether this has any cause for concern.
Thanks,
So I have some news !
I log in the server with a local administrator account and launch a Repair of VMware Converter, restart the start and relaunch a P2V.
After that the error is gone.
BUT after 1 hour at 97% I have an error...
I join the logs too...
I tried to understand something from it but I didn't find anything that talk to me.
Thanks a lot.
Looks like getting errors at 2% or 97% during conversion with VMware Converter is very common.
I don't know what path (be it file or network) is the problem in the serialization error.
[2017-05-04 16:27:26.406 'P2V' 316 info] [postProcessingTask,85] Calling DoReconfig
[2017-05-04 16:27:26.421 'P2V' 323 error] [serialization,254] Serialization error: Le chemin spécifié est introuvable.
[2017-05-04 16:27:26.421 'P2V' 323 verbose] [jobManager,438] Raising event 4 for job 1
[2017-05-04 16:27:38.421 'P2V' 316 error] [task,295] Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)
[2017-05-04 16:27:38.421 'P2V' 316 verbose] [task,339] Transition from InProgress to Failure requested
Were the VMDKs created?
[#2] [2017-05-04 16:27:36.437 'App' 263 info] [extendedOsInfo,186] Getting extended OS info by parsing boot.ini and/or analyzing the registry failed
[#2] [2017-05-04 16:27:36.453 'App' 263 verbose] [disposable,69] Registering disposable session object id=localFile={\\.\vstor2-p2v30-E1FA0440007E00000000000003000000\msdos.sys}
[#2] [2017-05-04 16:27:36.453 'App' 263 verbose] [disposable,80] Associating disposable session object id=localFile={\\.\vstor2-p2v30-E1FA0440007E00000000000003000000\msdos.sys} with session id=D09ED852-30CA-11E7-BDE2-009027DE43A1
[#2] [2017-05-04 16:27:36.453 'App' 263 error] [extendedOsInfo,309] Error
[#2] [2017-05-04 16:27:36.453 'App' 263 verbose] [disposable,122] object explicitly disposed: localFile={\\.\vstor2-p2v30-E1FA0440007E00000000000003000000\msdos.sys}
[#2] [2017-05-04 16:27:36.453 'App' 263 info] [extendedOsInfo,207] msdos.sys is non-existent or inaccessible
[#2] [2017-05-04 16:27:36.453 'App' 263 error] [extendedOsInfo,220] FAILED parsing NTFS or Win9x_DOS partition
EDIT: Have a look at this, too
VMDK is created on a datastore of the VMware infra.
I have it but when I try to boot the VM I have a blue screen.
Hi
Before starting P2V process, you have to Inject the SCSI drivers in the Physical server. Follow this KB to Inject drivers
and then start the P2V process.
If the P2V process fails at 95% or 97 or 99%, don't worry
Just go the Datastore.
Browse Datastore
Right click the VMX file and add to inventory.
Then power ON the VM, it should work
Best of Luck..!!