VMware Cloud Community
kasunc_1a
Contributor
Contributor

VM power on issue

Dear Team,

The following error occurs when the VM is turned on(ESXI 5.5.0). Module DiskEarly power on failed. Cannot open the disk 'SQL_srv-000001.vmdk' or one of the snapshot disks it depends on. The system cannot find the file specified VMware ESX cannot find the virtual disk "SQL_srv-000001.vmdk". Verify the path is valid and try again.

How to resolve without data loss. 

Regards, Kasun

Reply
0 Kudos
7 Replies
NathanosBlightc
Commander
Commander

Please verify file existence through the CLI via running the following command:

cd /vmfs/volumes/[datastore-name]/[vm-name]

ls *.vdmk -lrth

For each of the virtual disks for that VM, you should see something like this:

  • sql_srv.vmdk
  • sql_srv-flat.vmdk
  • sql_srv-000001.vmdk
  • sql_srv-000001-sesparase.vmdk
Please mark my comment as the Correct Answer if this solution resolved your problem
continuum
Immortal
Immortal

You need:
SQL_srv-000001-delta.vmdk
SQL_srv-000001.vmdk
SQL_srv-flat.vmdk
SQL_srv.vmdk

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

kasunc_1a
Contributor
Contributor

only for following details are available. How can i fixed it.

SQL_srv-aux.xml                           SQL_srv_1-000003.vmdk
SQL_srv-flat.vmdk                        SQL_srv_1-flat.vmdk
SQL_srv.vmdk                               SQL_srv_1.vmdk
SQL_srv.vmsd                               eco_vet_db.nvram
SQL_srv.vmx                                 vmware-15.log
SQL_srv.vmxf                                vmware-16.log
SQL_srv_1-000001-delta.vmdk    vmware-17.log
SQL_srv_1-000001.vmdk             vmware-18.log
SQL_srv_1-000002-delta.vmdk   vmware-19.log
SQL_srv_1-000002.vmdk             vmware-20.log
SQL_srv_1-000003-delta.vmdk    vmware.log

Reply
0 Kudos
kasunc_1a
Contributor
Contributor

only for following details are available. How can i fixed it.

SQL_srv-aux.xml                           SQL_srv_1-000003.vmdk
SQL_srv-flat.vmdk                        SQL_srv_1-flat.vmdk
SQL_srv.vmdk                               SQL_srv_1.vmdk
SQL_srv.vmsd                               eco_vet_db.nvram
SQL_srv.vmx                                 vmware-15.log
SQL_srv.vmxf                                vmware-16.log
SQL_srv_1-000001-delta.vmdk    vmware-17.log
SQL_srv_1-000001.vmdk             vmware-18.log
SQL_srv_1-000002-delta.vmdk   vmware-19.log
SQL_srv_1-000002.vmdk             vmware-20.log
SQL_srv_1-000003-delta.vmdk    vmware.log

Reply
0 Kudos
NathanosBlightc
Commander
Commander

It's VMware official method to recover/recreate the VMDK files:

https://kb.vmware.com/s/article/1002511

I strongly suggest watching the video first.

Please mark my comment as the Correct Answer if this solution resolved your problem
Reply
0 Kudos
swaheed1239
Enthusiast
Enthusiast

Try to consolidate the snapshots if you don't need them so that the snapshot vmdks are consolidated to the base vmdk and you can try to power on the VM. If not, try to migrate the VM files to another datastore using storage vmotion and try.

Reply
0 Kudos
a_p_
Leadership
Leadership

Prior to following any advice, please run ls -lisa > filelist.txt in the VM's folder to create a complete file listing.
The compress/zip the following files, and attach the resulting .zip archive to your next reply.

SQL_srv.vmdk
SQL_srv_1.vmdk
SQL_srv_1-000001.vmdk
SQL_srv_1-000002.vmdk
SQL_srv_1-000003.vmdk
SQL_srv.vmx
SQL_srv.vmsd
vmware.log
filelist,txt

In addition to the files, please explain hat happened, that may have caused the issue, i.e. whether the datastore ran out of disk space, or if snapshots were consolidated/deleted, ... This may help to find out how to solve that issue.

André

Reply
0 Kudos