Help! After moving VM to another datastore VM won't start

Hi,

I am using ESXi 3.5.

I moved a VM from a local datastore to  a NFS datastore, by powering down the VM and using the option in the VI client to move to another datastore.

I removed the old VM from inventory and re-added the VM from the new datastore, choosing to keep the UID.

Now when I try to start the VM, I get to 95 % before failing with a file not found error.

I have checked the datastore for the 'missing file' it is refering to the .vmdk file, the file in the datastore is sbs2008-flat.vmdk.  I think this may have something to do with snapshots, but I have never used them on this virtual machine.

I copied the relevent part of the logs below.

Creating Stat vm.suspendTime

Jun 07 08:24:13.262: vmx| MStat: Creating Stat vm.powerOnTimeStamp

Jun 07 08:24:13.320: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Jun 07 08:24:13.356: vmx| Unable to find file SBS2008.vmdk

Jun 07 08:24:13.429: vmx| Unable to find file SBS2008.vmdk

Jun 07 08:24:13.429: vmx| DISK: OPEN scsi0:0 'SBS2008.vmdk' persistent R[(null)]

Jun 07 08:24:13.476: vmx| Unable to find file SBS2008.vmdk

Jun 07 08:24:13.513: vmx| DISKLIB-LINK  : "SBS2008.vmdk" : failed to open (The system cannot find the file specified). 

Jun 07 08:24:13.513: vmx| DISKLIB-CHAIN : "SBS2008.vmdk" : failed to open (The system cannot find the file specified).

Jun 07 08:24:13.513: vmx| DISKLIB-LIB   : Failed to open 'SBS2008.vmdk' with flags 0xa (The system cannot find the file specified).

Jun 07 08:24:13.513: vmx| Msg_Post: Error

Jun 07 08:24:13.513: vmx| http://msg.disk.fileNotFound VMware ESX Server cannot find the virtual disk "SBS2008.vmdk". Please verify the path is valid and try again.

Jun 07 08:24:13.513: vmx| http://msg.disk.noBackEnd Cannot open the disk 'SBS2008.vmdk' or one of the snapshot disks it depends on.

Jun 07 08:24:13.513: vmx| http://msg.disk.configureDiskError Reason: The system cannot find the file specified.----

Jun 07 08:24:13.521: vmx| Module DiskEarly power on failed.

Jun 07 08:24:13.522: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

Jun 07 08:24:13.522: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Jun 07 08:24:17.181: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Jun 07 08:24:17.182: vmx| VMX idle exit

Jun 07 08:24:17.501: vmx| Flushing VMX VMDB connections

Jun 07 08:24:17.502: vmx| IPC_exit: disconnecting all threads

Jun 07 08:24:17.502: vmx| VMX exit (0).

Jun 07 08:24:17.502: vmx| VMX has left the building: 0.

Cheers

Mick.