Vm won't boot after moving to another server

[Stendec75]

Hi all,

After our production server went down with a broken mainboard, we setup another server (different hwardware) and installed vSphere 5.1. The existing virtual machines (database) (original server) are on a raid controller (two disks raid 1). We installed the RAID drivers in vSphere to make the database accessible (Areca RAID controller). Then, from the 'Configuration Tab' we opend the VM database (Browse Database) of the existing virtual machine, rightclickt on servername.vmx file and choose 'Add to inventory'. After that the VM are added to the Inventory of the VM client. The first time we started the VM it asked if the VM was moved or copied. Because we didn't know the right answer we choose 'copied'. It mentioned when we did not know the correct answer, choose 'copied'. After that, there is a lot of disk activity, but it ends it with an error that it can't find the  vmdk file.

Power On virtual machine

machinename.com

File []

/vmfs/volumes/504dbfc2-bc271df0-f9b3-001e67339752/machinename.com_2.vmdk was not found

Then the startup stops and nothing happends.

In the original situation all the disk storage took place within the disk array of the RAID controller, so there where no additional disks installed for snapshot storage.

Please help!

[weinstein5 · Accepted solution]

Did you add both virtual disks to the VM? The _2 in the file name machinename.com_2.vmdk typically indicates that this is the second virtual disk on the VM

[Stendec75]

When browsing trough the datastore, there exist some .vmdk files, bot not with then name mentioned in the error. I see vmdk file: machinename.com-000001.vmdk and machinename.com-000002.vmdk

[weinstein5]

Those are snapshots - can you open the snapshot manager and see if hey show up?

[Stendec75]

Thanks Weinstein5! There was indeed an second HDD attached, it eascape my attention. Thanks again, you saved my day!