So after spending many hours migrating all my VMs back to their uber performing datastores, I went to power on my secondary DC only to find it would not start up.
Something to do with a missing file.
“The system cannot find the file specified.
Cannot open the disk ‘DC02.vmdk’ or one of the snapshot disks it depends on.
VMware ESX cannot find the virtual disk “DC02.vmdk”. Verify the path is valid and try again. ”
I immediately checked the configuration settings in vCenter and all appeared correct. The datastore browser confirmed that it could see the 10GB vmdk file – so what could it be?
I never trust a GUI, so ssh’d over to the TSM and did a quick directory listing to find that whilst the -flat.vmdk file was there, the .vmdk file wasn’t! In the migration back, somehow the VM had lost the file that controls its understanding of disk geometry, controller type, provisioned format (thin/thick).
Knowing I had the -flat file was re-assuring, had the shoe been on the other foot and all I was left with was the vmdk file, I would have been a little lot more concerned.
The first step to resolution was to create a new identically sized virtual disk to the -flat file I had been left with. In turn, this would then create a new VMDK file that I could borrow.
1) Determine the existing -flat.vmdk file size
ls -l *-flat.vmdk
-rw——- 1 root root 4841537536 Feb 24 23:38 DC02-flat.vmdk
2) Determine the controller type associated with this disk
less *.vmx | grep -i virtualdev
scsi0.virtualDev = “lsilogic”
In this instance the VM used the lsilogic controller
3) Armed with this information, I now create a new vmdk
vmkfstools -c 4841537536 -a lsilogic -d thin temp.vmdk
(the -d thin parameter provisions the disk as thin as we don’t really want the -flat file anyway)
4) The result is a temp-flat.vmdk and a temp.vmdk file.
5) Rename the temp.vmdk file to match the VM name – in this case DC02
mv temp.vmdk DC02.vmdk
6) Edit DC02.vmdk using VI and update the extent description contents to match the server name
# Extent description
RW 20971520 VMFS “tempDC02-flat.vmdk”
7) If the original -flat.vmdk was thinly provisioned you do not need to modify any additional parameters in the file, however if it was thick, you must remove the following line:-
ddb.thinProvisioned = “1”
8) Delete the temp-flat.vmdk created in step 3 and you should be good to go!