Moving VMs - The system cannot find the file specified

[curVV]

Hi there,

I have 2 identical servers both running ESXi-4.1. I moved one virtual machine (win2k3 64bit) from host1 to host2 using Veeam FastSCP.

(I tried using VMWare converter from both windows and linux machines but it keeps coming up with error "unable to obtain hardware information" so I used Veeam FastSCP)

After the move I used the vSphere Client to browse the data store on the destination host, right-clicked the vmx and chose add to inventory.

It then asked me if the VM was moved or copied. I tried the whole process twice, selecting copied and moved.

Whether I select moved or copied, when I power on the VM I get the following error:

Power On virtual machine:File <unspecified filename> was not found Reason: The system cannot find the file specified Cannot open the disk '/vmfs/volumes/4bede759-8fc98ce2-e16e-1cc1dee9f7ff/CCCXXX01/CCCXXX.vmdk' or one of the snapshot disks it depends on. VMware ESX cannot find the virtual disk "/vmfs/volumes/4bede759-8fc98ce2-e16e-1cc1dee9f7ff/CCCXXX01/CCCXXX01.vmdk". Verify the path is valid and try again.

I have checked in the CCCXXX01.vmx file for any references to the original volume. There are none. The paths are all correct. To make 100% sure I copied the path in the error and pasted into ssh window:

cd /vmfs/volumes/4bede759-8fc98ce2-e16e-1cc1dee9f7ff/CCCXXX01/

It definitely exists.

I've also set the permissions using chmod on all the files exactly like it was on the original host.

Still getting this error.

Any ideas please? ?:|

[AndreTheGiant]

I suggest to first delete the snapshots, then copy the file.

About I_moved or I_copied, the first keep the same MAC and UUID of the original VM, the second will build new identifier.

Andre

[curVV]

Hi Andre,

Thanks but there are no snapshots. This is a list of the files:

/vmfs/volumes/4c4ba84a-a4bc2db5-9712-1cc1dee9473d/CCCXXX01 # ls -lh -rw------- 1 root root 10.0G Oct 28 13:48 CCCXXX01-flat.vmdk -rw------- 1 root root 8.5k Oct 28 08:09 CCCXXX01.nvram -rw------- 1 root root 496 Oct 27 06:32 CCCXXX01.vmdk -rw-rr 1 root root 0 Oct 27 06:32 CCCXXX01.vmsd -rwxr-xr-x 1 root root 3.5k Oct 28 13:48 CCCXXX01.vmx -rw-rr 1 root root 264 Oct 28 08:18 CCCXXX01.vmxf -rw------- 1 root root 10.0G Oct 28 13:48 CCCXXX01_1-flat.vmdk -rw------- 1 root root 472 Oct 28 08:18 CCCXXX01_1.vmdk -rw------- 1 root root 28.0G Oct 28 13:48 CCCXXX01_2-flat.vmdk -rw------- 1 root root 472 Oct 28 08:18 CCCXXX01_2.vmdk -rw------- 1 root root 10.0G Oct 28 13:48 CCCXXX01_3-flat.vmdk -rw------- 1 root root 472 Oct 28 08:18 CCCXXX01_3.vmdk -rw------- 1 root root 28.0G Oct 28 13:48 CCCXXX01_4-flat.vmdk -rw------- 1 root root 472 Oct 28 08:18 CCCXXX01_4.vmdk -rw------- 1 root root 4.0G Oct 28 13:48 CCCXXX01_5-flat.vmdk -rw------- 1 root root 470 Oct 28 08:18 CCCXXX01_5.vmdk -rw-rr 1 root root 231.7k Oct 28 13:48 vmware.log

Any other ideas?

[AndreTheGiant]

Seems fine.

Have you check the vmx and all the small vmdk files to see if there is some reference to the original datastore?

Or open the VM setting with the vSphere client and check if each disk has the right size.

Andre

[curVV]

I checked the .vmx and .vmxf files. I started the copy from scratch because I may have screwed things up.

Will check VM setting when done... (it takes a while accross the network)

[curVV]

OK I copied everything again then checked the VM settings, (referenced this doc ) but didn't really change anything and clicked OK. It started up asked if moved or copied, I said Moved and boots up fine without issues.

Maybe something went wrong during the previous copy process or maybe I just screwed something up.

Thanks for help!