Hi,
I have a VM with two hard disks from which the .vmdk files somehow went missing. The flat.vmdk files are still there however. I followed KB 1002511 to rebuild the .vmdk files. After rebuilding the .vmdk files, the VM starts, but it boots to a Windows recovery screen and the drives are not properly recognized. The KB article indicates that the procedure does not work for VMs whose SCSI adapter is Paravirtual, which was the case for me. However, it suggests that the new descriptor file(s) can be updated with ddb.adapterType = "pvscsi" (instead of ddb.adapterType = "lsilogic"). I tried this, but unfortunately, the VM still does not boot properly. Here is a summary of what I have tried so far:
- When creating the new virtual disk, specifying "lsilogic" as the controller type (i.e., vmkfstools -c [file size of flat.vmdk] -a lsilogic -d thin temp.vmd) and leaving it as-is in the .vmdk files.
- When creating the new virtual disk, specifying "lsilogic" as the controller type and updating it in the .vmdk files to be "pvscsi".
- When creating the new virtual disk, specifying "pvscsi" as the controller type and also updating it in the .vmdk files to be "pvscsi" (i.e., vmkfstools -c [file size of flat.vmdk] -a pvscsi-d thin temp.vmd).
I also noticed that the ddb.virtualHWVersion in the new .vmdk files is set to 9, even though my VMs are all version 8 (and this is also what shows in the virtual machine settings in the vSphere Client), so I tested starting the VM with .vmdk file set to 8 and 9. Same result .
Any idea on what else I could try?
Thanks!