Since upgrading to version 5.3 vranger when i try and restore one of my servers after the restore when i power it on i get the following msg
"Error loading operation system"
Possible things to check:
Did the Restore in the previous version vRanger successful and you can boot the VM OK?
Is the actual restore job in vRanger 5.3 successful?
Is the restore going to different version of ESX host like 5.0, where the hardware version is 8?
Is the disk controller same under Edit Settings in vSphere client?
Have you try to restore from different date archive and see?
Does FLR work for this backup? What is guest OS? Was backup performed with ABM enabled?
Have you tried to re-register vm and backup? You need to power down, remove from inventory, re-add using datastore browser.
It is also possible that the hardware geometry is not matching up in the headers files between Source VM and Restored VM.
Was this VM created by P2V conversion?
The best way to check the hardware geometry is to compare the two Disk Descriptor Files of the Soruce VM and the Restored VM...
Changing the geometry for the system disk vmdk fixed the issue.
Any time you have a P2V conversion you will probably have disk geometry that is not a whole even number (is a fraction). That is what is causing this behavior, vRanger is not involved in the problem at this point. In cases like this, it is usually beneficial to have a best practice procedure put in place to verify the disk geometry after a P2V conversion, which is what causes the problem. The error that vRanger throws from that is a symptom, that something is not correct, and has to be addressed.
