Cannot start VM Machine

Dear All,

  yesterday we had a FreeNas going down. This FreeNas was one of our datastores on an ESXi 4.1. We managed to retrieved the machines and uploaded them to another datastore. Most of them are ok but some of them are not coming up giving us an error that "The file specified is not a virtual disk". Please see the part of the log file with the error below. Any help will be appreciated.

Thanks


Dec 17 16:21:06.502: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk' persistent R[]
Dec 17 16:21:06.504: vmx| DISKLIB-VMFS  : VmfsExtentCommonOpen: possible extent truncation (?) realSize is 78009403, size in descriptor 83886080.
Dec 17 16:21:06.504: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2-flat.vmdk" : failed to open (The file specified is not a virtual disk): Size of extent in descriptor file larger than real size. Type 3
Dec 17 16:21:06.505: vmx| DISKLIB-LINK  : "/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk" : failed to open (The file specified is not a virtual disk).  
Dec 17 16:21:06.505: vmx| DISKLIB-CHAIN : "/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk" : failed to open (The file specified is not a virtual disk).
Dec 17 16:21:06.505: vmx| DISKLIB-LIB   : Failed to open '/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk' with flags 0xa The file specified is not a virtual disk (15).
Dec 17 16:21:06.505: vmx| DISK: Cannot open disk "/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk": The file specified is not a virtual disk (15).
Dec 17 16:21:06.505: vmx| Msg_Post: Error
Dec 17 16:21:06.505: vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/4e43eccd-816f6f1a-c02e-9c8e99f8a1a5/VMMachineNew/VMMachine 2.vmdk' or one of the snapshot disks it depends on.
Dec 17 16:21:06.505: vmx| [msg.disk.configureDiskError] Reason: The file specified is not a virtual disk.----------------------------------------
Dec 17 16:21:06.515: vmx| Module DiskEarly power on failed.
Dec 17 16:21:06.515: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
Dec 17 16:21:06.519: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
Dec 17 16:21:07.536: vmx| Vix: [352244 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
Dec 17 16:21:07.539: vmx| Vix: [352244 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
Dec 17 16:21:07.539: vmx| Transitioned vmx/execState/val to poweredOff
Dec 17 16:21:07.539: vmx| Vix: [352244 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
Dec 17 16:21:07.539: vmx| Vix: [352244 mainDispatch.c:3597]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
Dec 17 16:21:07.539: vmx| VMX idle exit
Dec 17 16:21:07.539: vmx| VMIOP: Exit
Dec 17 16:21:07.540: vmx| Vix: [352244 mainDispatch.c:652]: VMAutomation_LateShutdown()
Dec 17 16:21:07.541: vmx| Vix: [352244 mainDispatch.c:602]: VMAutomationCloseListenerSocket. Closing listener socket.
Dec 17 16:21:07.542: vmx| Flushing VMX VMDB connections
Dec 17 16:21:07.548: vmx| VMX exit (0).
Dec 17 16:21:07.548: vmx| AIOMGR-S : stat o=1 r=3 w=0 i=0 br=49152 bw=0
Dec 17 16:21:07.548: vmx| VMX has left the building: 0.

LVL 2
AJKBOCAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You could possible try

1. Winimage to open the VMDK
http://www.winimage.com/

2. VMware Mount Utility
http://www.vmware.com/download/eula/diskmount_ws_v55.html
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The virtual disk is corrupted.
0
 
AJKBOCAuthor Commented:
Is there any method we can use to retrieve any files from this disk?
0
 
AJKBOCAuthor Commented:
Ok. I will try the aboe on Monday and get back to you.

Thanks!
0
 
AJKBOCAuthor Commented:
We tried Winimage and even though we managed to open the VMDK file we couldn't browse in the Users folder of the server which is where the files we needed were. We ended up using a similar program, USF Explorer, which could browse in the Users folder and we were able to retrieve our files. Thanks for pointing us to the right direction.
0
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.