vmware - file specified is not a virtual disk

I have a virtual machine that will not start back up.  It is saying the file specified is not a virtual disk.  This is a virtualy disk, and due to storms in the area it was shut down and now will not boot up.  Here is the vmdk file code

# Disk DescriptorFile

# Extent description
RW 174063616 VMFS "EGHC-SRV-1-06-flat.vmdk"

# The Disk Data Base

ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "10834"
ddb.uuid = "60 00 C2 9f f9 a7 b1 ea-f1 71 13 10 a5 e9 f9 5b"
ddb.longContentID = "baeee61a9c9806155239d08b732a4b90"
ddb.virtualHWVersion = "7"

Any suggestions?
Who is Participating?
considerscsAuthor Commented:
I got it figured out.  The vmdk descriptor file was not the same size as the flat.vmdk file.  I recreated the descriptor file as the exact same size (cannot be 1 k off) and edited the file to point to the correct flat file.  When I uploaded the file, the machine booted right up as it had never been shut down.
Sounds like the file became corrupted when the server was shutdown unexpectedly. You do have a current back up of this file, right.
considerscsAuthor Commented:
No, that is the problem.  We need to find some way to get this back up.  This has the companies exchange and domain on it.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Found this

The VMware products check the integrity of the virtual disks on power on and will automatically repair them if possible. There is no separate/standalone tool to repair the virtual disk, since it's built into the product.

Just like a physical system, you should have a backup strategy in place in case of a disk failure. With virtual machines this task is simple, since you just need to copy the virtual machine files to a safe location / media.

You may want to create a new virtual machine and attach your virtual disk ( /data1/win2004.vmdk ) as a second virtual disk to the new virtual machine configuration to see if you can access the data.

Another option would be to download the VMware DiskMount Utility http://www.vmware.com/download/ and see if you can access the data.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Which VMware product are yoiu using?

if you temporaily remove the disk (do not delete) from the VM, does the VM start-up, complete this to check it is the vmdk disk that is causing the issue?

you could also attach this exchange/domain disk to another machine, and see if you can access the data.

otherwise Restore or consult a Data Recovery company such as http://www.krollontrack.com/data-recovery.
considerscsAuthor Commented:
I was able to resolve this, then posted the resolution on the board to show anyone for future reference.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.