VMware Cloud Community
MohammadJ
Contributor
Contributor

ESXI 6.5 - Failed - Unable to enumerate all disks.

Hi,

So basically I have VM on datastore1 which was VMFS5

I installed a new SSD, created a new datastore (VMFS6) and tried to move the files from datastore1 to datastore2. Unfortunately, the size was not enough too; I then tried to put them back to datastore1 but couldn't because disk got full before all files were moved.

I installed a new HDD and created datastore3 (VMFS6), and copied all files from both datastore1 and datastore2. The VM failed to poweron with an error "Failed - Unable to enumerate all disks"

What troubleshooting steps I should try ? Is there a way to verify the integrity of the files or the tree structure ?

Thanks.

Reply
0 Kudos
6 Replies
scott28tt
VMware Employee
VMware Employee

This should be in the ESXi Discussions area - the {code} area is for SDK matters - post reported.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
a_p_
Leadership
Leadership

From what you explain, it seems to me that something got lost along the way.

As a first step, please post a complete list of files in the VM's folder. No screenshot please, but the text output of ls -lisa from the command line!
In addition to this, please compress/zip the VM's vmware.log file m, and attach it to your next reply to see whether it contains helpful information.

André

Moderator note: Moved to ESXi Discussions

 

Reply
0 Kudos
MohammadJ
Contributor
Contributor

Thanks for the immediate reply.

Below is the result of the command line:

total 508726592
2244 128 drwxr-xr-x 1 root root 77824 May 26 16:31 .
4 1024 drwxr-xr-t 1 root root 73728 May 26 16:29 ..
37752068 36176896 -rw------- 1 root root 37044609024 May 20 11:34 FirePower-000001-delta.vmdk
3332 0 -rw------- 1 root root 322 May 17 15:02 FirePower-000001.vmdk
71306500 210404352 -rw------- 1 root root 215453523968 May 20 13:01 FirePower-000002-delta.vmdk
67112196 0 -rw------- 1 root root 307 May 20 11:38 FirePower-000002.vmdk
88083716 64 -rw------- 1 root root 28541 May 21 11:22 FirePower-Snapshot1.vmsn
92278020 64 -rw------- 1 root root 28548 May 21 11:22 FirePower-Snapshot2.vmsn
117443844 262144000 -rw------- 1 root root 268435456000 May 26 15:08 FirePower-flat.vmdk
20974852 64 -rw------- 1 root root 8684 May 17 16:18 FirePower.nvram
33557764 0 -rw------- 1 root root 536 May 21 10:43 FirePower.vmdk
100666628 0 -rw------- 1 root root 684 May 26 12:15 FirePower.vmsd
121638148 0 -rw-r--r-- 1 root root 2261 May 26 16:31 FirePower.vmx
8391940 0 -rw------- 1 root root 47 May 17 16:18 FirePower.vmxf

Regarding the vmware.log file, please bare my ignorance as I believe I deleted it previously somehow by mistake and it is not generating a new one upon failing in trying to power on the VM.

Note: host version is 6.7.0 Update 3 and not 6.5 as stated in the main topic.

Thanks !

Reply
0 Kudos
a_p_
Leadership
Leadership

The issue in this case is most likely that you've copied the files manually to the VMFS6 datastore. With VMFS6 the "delta" snapshot format is not supported anymore, but only the "sesparse" format. A migration wold have converted snapshot files to the correct format.

The reason why I said "most likely" is that the time .vmdk files' stamps are not as I would expect them to be. The base (flat) .vmdk file is newer than the snapshot files!?
What's the VM's current .vmdk file in "FirePower.vmx"?

To find out whether the snapshot chain is consistent, run: vmkfstools -e FirePower-000002-delta.vmdk

André

Reply
0 Kudos
MohammadJ
Contributor
Contributor

@a_p_  that's correct I tried to manually copy them.

vmx points out to FirePower-000002.vmdk

I tried vmkfstools -e FirePower-000002-delta.vmdk :

Failed to open disk link /vmfs/volumes/60a26e5e-ed042866-7036-dc4a3e46d4af/FirePower/FirePower-000002-delta.vmdk :The file specified is not a virtual disk (15)Disk chain is not consistent : The file specified is not a virtual disk (15)

 

I then tried on the other one without delta vmkfstools -e FirePower-000002.vmdk:

Failed to open disk link /vmfs/volumes/60a26e5e-ed042866-7036-dc4a3e46d4af/FirePower/FirePower-000002.vmdk :The specified feature is not supported by this version (24)Disk chain is not consistent : The specified feature is not supported by this version (24)

 

What do you think I should do to fix the whole thing? Should I try pluggin in a new HDD as VMFS5 and copy the files to it and try or is there a way to downgrade VMFS6 to VMFS5 ?

Thanks

 

Reply
0 Kudos
a_p_
Leadership
Leadership

Sorry about the wrong file name in the command (a copy&paste error).

There's unfortunately no way to downgrade a VMFS file system, so yes, you'll need to create a VMFS5 datastore.

André

Reply
0 Kudos