Help - need tool to recover flat vmdk file or load VM with missing disk file

[smartgroupvoip]

On VM with two virtual disks we deleted from the datastore by error one of the hard disks file -flat.vmdk (there were 5 snapshots)

We thought the deleted hard disk was not important (it was just for data that we have elsewhere) and that we would delete it form the VM and then start the VM without it, but the VM wont load. We are getting a "Error - Unable to enumerate all disks."

Is there any known good tool to recover the file? we didn't write anything new, so the info could be there...

We don't know why the VM keeps referencing to the missing hard drive even if we deleted from the VM configuration.

We were hoping the file could be recovered or a way to load the VM without it.

Appreciate any help.

Regards

Rod

[a_p_]

Welcome to the Community,

just to make sure I understand this correctly. You don't need the virtual disk that you've deleted, do you?

If you need the files/data from the deleted disks, stop reading here, and try to contact continuum​.

If you are sure that you don't need the disk, then we need to find out what's causing the current error. Is it just a configuration issue, or did you accidentally delete more files than just the ones for the disk in question?

To find out about this, please connect to the hoost using e.g. putty, run ls -lisa in the VM's folder, and post the resulting file list (as text please) in your next reply.

In addition to this, download the VM's .vmx, .vmsd as well as its latest vmware.log files, and attach these files to your reply.

André

[continuum]

If you deleted a flat.vmdk you MUST IMMEDIATLY stop all thin provisioned VMs and those with snapshots.

Provide vmfs-header-dump - see

Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay

If you use ESXi 6 and / or vmfs 6 you must react as quickly as possible - otherwise the vmfs-metadata to find the flat-vmdk-fragments is gone.

Also provide mire details: filelist, vmware.logs and other related details.

[smartgroupvoip]

Thanks for the answer.

If we are able to get the VM to start, then I shouldn't need the deleted file.

Looking at the vmsd the snapshots appear to be pointing to the secondary disk folder. I'm attaching everything, maybe in the logs we can see...

I have 2 VMs folders. One for each Virtual Disk:

The one I want to load with the VM (IDINET-Server)

ls -lisa

total 664798240

574622596      8 drwxr-xr-x    1 root     root          5460 Dec 21 10:13 .

      4   1024 drwxr-xr-t    1 root     root          1680 Dec 21 06:05 ..

796920708 10781696 -rw-------    1 root     root     11039981568 Jan  1  2013 IDINET-Server-000001-delta.vmdk

801115012      0 -rw-------    1 root     root           330 Dec 12  2019 IDINET-Server-000001.vmdk

822086532 68420608 -rw-------    1 root     root     70062227456 Jan  5  2013 IDINET-Server-000002-delta.vmdk

826280836      0 -rw-------    1 root     root           337 Dec 12  2019 IDINET-Server-000002.vmdk

25168772 93340672 -rw-------    1 root     root     95580372992 Jan 12  2013 IDINET-Server-000003-delta.vmdk

29363076      0 -rw-------    1 root     root           337 Dec 12  2019 IDINET-Server-000003.vmdk

50334596 137610240 -rw-------    1 root     root     140912410624 Dec 17 10:14 IDINET-Server-000004-delta.vmdk

54528900      0 -rw-------    1 root     root           387 Dec 12  2019 IDINET-Server-000004.vmdk

562039684 33555456 -rw-------    1 root     root     34360311808 Dec 21 05:37 IDINET-Server-000005-delta.vmdk

566233988      0 -rw-------    1 root     root           337 Dec 16  2019 IDINET-Server-000005.vmdk

486542212 1377280 -rw-------    1 root     root     1409859584 Dec 18 05:47 IDINET-Server-000006-delta.vmdk

494930820      0 -rw-------    1 root     root           391 Dec 18 05:08 IDINET-Server-000006.vmdk

792726404 4194304 -rw-------    1 root     root     4294967296 Dec 30  2012 IDINET-Server-Snapshot1.vmem

788532100   2048 -rw-------    1 root     root       1538103 Dec 30  2012 IDINET-Server-Snapshot1.vmsn

817892228 4194304 -rw-------    1 root     root     4294967296 Jan  1  2013 IDINET-Server-Snapshot2.vmem

813697924   2048 -rw-------    1 root     root       1515512 Jan  1  2013 IDINET-Server-Snapshot2.vmsn

20974468 4194304 -rw-------    1 root     root     4294967296 Jan  5  2013 IDINET-Server-Snapshot3.vmem

16780164   2048 -rw-------    1 root     root       1524572 Jan  5  2013 IDINET-Server-Snapshot3.vmsn

46140292 4194304 -rw-------    1 root     root     4294967296 Jan 12  2013 IDINET-Server-Snapshot4.vmem

41945988   2048 -rw-------    1 root     root       1539531 Jan 12  2013 IDINET-Server-Snapshot4.vmsn

654314372 5242880 -rw-------    1 root     root     5368709120 Dec 17 07:28 IDINET-Server-Snapshot5.vmem

650120068   6144 -rw-------    1 root     root       5620161 Dec 17 07:28 IDINET-Server-Snapshot5.vmsn

557845380 5242880 -rw-------    1 root     root     5368709120 Dec 18 05:48 IDINET-Server-Snapshot6.vmem

549456772   2048 -rw-------    1 root     root       1542209 Dec 18 05:48 IDINET-Server-Snapshot6.vmsn

599788420 292422656 -rw-------    1 root     root     299440799744 Dec 30  2012 IDINET-Server-flat.vmdk

469764996   1024 -rw-------    1 root     root          8684 Dec 18 05:48 IDINET-Server.nvram

603982724      0 -rw-------    1 root     root           654 Dec 18  2012 IDINET-Server.vmdk

591399812      8 -rw-r--r--    1 root     root          3001 Dec 18 05:47 IDINET-Server.vmsd

478153604      8 -rwx------    1 root     root          4339 Dec 21 10:13 IDINET-Server.vmx

473959300      8 -rw-------    1 root     root          3052 Dec 18 04:45 IDINET-Server.vmxf

461376388   1024 -rw-r--r--    1 root     root         62657 Dec 18 04:44 vmware-23.log

524290948   1024 -rw-------    1 root     root        804398 Dec 18 04:54 vmware-24.log

541068164   2048 -rw-------    1 root     root       1053382 Dec 21 05:37 vmware-25.log

595594116   1024 -rw-------    1 root     root        105194 Dec 21 05:41 vmware-26.log

629148548   1024 -rw-------    1 root     root        106083 Dec 21 05:41 vmware-27.log

645925764   1024 -rw-------    1 root     root        107411 Dec 21 05:48 vmware-28.log

671091588   1024 -rw-------    1 root     root        106081 Dec 21 05:49 vmware.log

The one where we deleted the file (DISCOS)

DISCOS] ls -lisa

total 3939336

708840324      8 drwxr-xr-x    1 root     root          1960 Dec 21 05:40 .

      4   1024 drwxr-xr-t    1 root     root          1680 Dec 21 06:05 ..

805309316  17408 -rw-------    1 root     root      17350656 Jan  1  2013 IMDEAidinet-000001-delta.vmdk

809503620      0 -rw-------    1 root     root           326 Dec 31  2012 IMDEAidinet-000001.vmdk

830475140  17408 -rw-------    1 root     root      17350656 Jan  5  2013 IMDEAidinet-000002-delta.vmdk

834669444      0 -rw-------    1 root     root           333 Jan  1  2013 IMDEAidinet-000002.vmdk

33557380  17408 -rw-------    1 root     root      17350656 Jan 12  2013 IMDEAidinet-000003-delta.vmdk

37751684      0 -rw-------    1 root     root           333 Jan  8  2013 IMDEAidinet-000003.vmdk

58723204 3851264 -rw-------    1 root     root     3943219200 Dec 17 10:14 IMDEAidinet-000004-delta.vmdk

62917508      0 -rw-------    1 root     root           383 Dec 17 09:42 IMDEAidinet-000004.vmdk

570428292  17408 -rw-------    1 root     root      17350656 Dec 21 05:37 IMDEAidinet-000005-delta.vmdk

578816900      0 -rw-------    1 root     root           333 Dec 16  2019 IMDEAidinet-000005.vmdk

499125124  17408 -rw-------    1 root     root      17350656 Dec 18 05:47 IMDEAidinet-000006-delta.vmdk

503319428      0 -rw-------    1 root     root           387 Dec 18 05:08 IMDEAidinet-000006.vmdk

Thanks!!

[a_p_]

We don't know why the VM keeps referencing to the missing hard drive even if we deleted from the VM configuration.

The secondary disk is still in the VM's configuration file.

scsi0:1.fileName = "/vmfs/volumes/50c529ad-f7f78a41-b037-7446a0fe2a44/DISCOS/IMDEAidinet-000005.vmdk"

The issue may as well be caused by the fact that the VM has active snapshots. Virtual disks must usually not be deleted from disk while the VM has snapshots.

Are you able to remove the second virtual disk from the VM's configuration?

André

[smartgroupvoip]

Hello,

There were no other VMs running. Maybe that helps.

Got vmfs-header-dump first part. The other can't get because of available space. I only have the affected datastorage connected. I'm trying to connect another disk to download it.

The rest I uploaded in the other answer.

Thanks!

[smartgroupvoip]

I was able to remove it. But it wouldn't load and I added it again.

Yes maybe the problem is deleting the disk when it had snapshots.

[continuum]

The rar is corrupt .

Try to split the dump like this:

dd if=/dev/disks/Device:1 bs=1M count=700 | gzip -c > /tmp/replace with your name-0.2048.gz

dd if=/dev/disks/Device:1 bs=1M skip=700 count=700 | gzip -c > /tmp/replace with your name-1.2048.gz

dd if=/dev/disks/Device:1 bs=1M skip=1400 count=700 | gzip -c > /tmp/replace with your name-2.2048.gz

empty /tmp after each dump ...

[a_p_]

That's strange.

What may be worth trying is to manually remove the secondary virtual disk from the VM's configuration using e.g. the vi editor on the host.

Please backup the .vmx file prior to modifying it!

Delete all the "scsi0:1" lines from the .vmx file that are related to the secondary virtual disk.

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "/vmfs/volumes/50c529ad-f7f78a41-b037-7446a0fe2a44/DISCOS/IMDEAidinet-000005.vmdk"

sched.scsi0:1.shares = "normal"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

Then - after editing the .vmx file - reload the VM (see https://kb.vmware.com/s/article/1026043)

André

[smartgroupvoip]

continuum Great! I was able to download the dump file by splitting it.

Here is a link to download of both header files:

https://we.tl/t-qwx39PMHe8

Thanks!

[smartgroupvoip]

OK, I can try that.

continuum​ should I try or wait until you check the dump files?

Thanks

[smartgroupvoip]

Hello,

I copied the files to another esxi and modified the .vmx to delete

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "/vmfs/volumes/50c529ad-f7f78a41-b037-7446a0fe2a44/DISCOS/IMDEAidinet-000005.vmdk"

sched.scsi0:1.shares = "normal"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

I'm still getting the same error.

[smartgroupvoip]

Is there a way for recreating the vmx file, having all the snapshot vmk files and the flat file?

[continuum]

Hi

sorry it was a busy day - I hope to find the time later this evening.

Ulli

[smartgroupvoip]

Hi,

OK, I'll wait for you, I don't want to do anything that can make it worst.

Thanks!

[smartgroupvoip]

continuum​ did you have time to take a look?

I don't want to bother, sorry.

[continuum]

Hi

I assume you are searching for this flat.vmdk ?

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=eb9deacf

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584843264 VMFS "IMDEAidinet-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "36405"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5cc4501ef58a0e8097a5299feb9deacf"

ddb.uuid = "0e be 5f e8 5f e8 e6 a9-a9 21 5e 31 0c 8b 9f f0"

Unfortunately the VMFS-metadata for that flat.vmdk has been deleted - there is no way to create a quick script to extract it again.

There is no unreferenced object of the expected size left in the VMFS-metadata.

As you are using esxi 6.5 with VMFS 5 this means that it looks like somebody deleted the file manually.

It may be possible to find the flat.vmdk with a scalpel - scan - according to the descriptorfile the vmdk was thick provisioned.

It probably was created in 2012 as one of the first objects inside that datastore so it may have been written in one piece.

A scalpel scan may take a day or more depending on the datastoresize ....

Maybe useful for further troubleshooting I attach a list with all the descriptorfiles I found.

Ulli

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=762c3b07

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 83886080 VMFS "Pruebas_0-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5221"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5273f70a23f483689e3e96a6762c3b07"

ddb.thinProvisioned = "1"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=40e185a1

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584845312 VMFS "IDINET-Server-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.encoding = "UTF-8"

ddb.geometry.biosCylinders = "36404"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosSectors = "63"

ddb.geometry.cylinders = "36404"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=1072a767

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 41943040 VMFS "RECUPERACION-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "2610"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "4b22ae3ee5ea31d6968e67251072a767"

ddb.toolsInstallType = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=10a16e80

parentCID=e3a8e3af

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000002.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000003-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "008be33ca90e2da6d42de2b510a16e80"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=e0ba8572

parentCID=ba7ae9ca

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000002.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000003-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "879206f9e977e60b80e3ad29e0ba8572"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=0dc2e5de

parentCID=10a16e80

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000003.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000004-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "e65104a8be034058eb37c7850dc2e5de"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=3e8991b1

parentCID=e0ba8572

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000003.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000004-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "c7c71e2b2388a96cf5e4c09b3e8991b1"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=762c3b07

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 83886080 VMFS "Pruebas_0-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5221"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5273f70a23f483689e3e96a6762c3b07"

ddb.thinProvisioned = "1"

ddb.uuid = "60 00 C2 9e eb bd 2a 97-30 5e 4f 5a 30 31 67 fa"

ddb.virtualHWVersion = "13"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=514aa69f

parentCID=0dc2e5de

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000004.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000006-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9df4bfd7dc4118cc4e99037c514aa69f"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=818bd5cc

parentCID=3e8991b1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000004.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000006-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9c08b46915590de549856dc0818bd5cc"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=12a8a791

parentCID=0dc2e5de

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000004.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000005-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "04001db8b0ba1afb65ed7b2312a8a791"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=d615ef9b

parentCID=3e8991b1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000006.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000005-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "dbcb63a08ccd4ed87228cac1d615ef9b"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=40e185a1

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584845312 VMFS "IDINET-Server-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.encoding = "UTF-8"

ddb.geometry.biosCylinders = "36404"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosSectors = "63"

ddb.geometry.cylinders = "36404"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "b7fff46c54805973d7cb9b0f40e185a1"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

ddb.uuid = "60 00 C2 92 01 4a 86 a9-68 45 8b ee 4f 46 25 4d"

ddb.virtualHWVersion = "11"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=eb9deacf

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584843264 VMFS "IMDEAidinet-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "36405"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5cc4501ef58a0e8097a5299feb9deacf"

ddb.uuid = "0e be 5f e8 5f e8 e6 a9-a9 21 5e 31 0c 8b 9f f0"

ddb.virtualHWVersion = "4"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=1072a767

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 41943040 VMFS "RECUPERACION-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "2610"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "4b22ae3ee5ea31d6968e67251072a767"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

ddb.uuid = "60 00 C2 99 fe 3c 4c 1f-ef f5 af 55 1c ab eb 0b"

ddb.virtualHWVersion = "13"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=c3289935

parentCID=40e185a1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000001-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "cc734ff02fd013e1521fb40fc3289935"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=4a6d8188

parentCID=eb9deacf

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000001-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "31cb2b237397d2b6a4da935e4a6d8188"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=e3a8e3af

parentCID=c3289935

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000001.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000002-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9f48c5a657aad2842d254699e3a8e3af"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=ba7ae9ca

parentCID=4a6d8188

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000001.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000002-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "f1303c15681351fb971d244cba7ae9ca"

#################################################################

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=fec1c02a

parentCID=fec1c02a

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

parentFileNameHint="imdeaenergia.dimdea.local.vmdk"

# Extent description

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s001.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s002.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s003.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s004.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s005.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s006.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s007.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s008.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s009.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s010.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s011.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s012.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s013.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s014.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s015.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s016.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s017.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s018.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s019.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s020.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s021.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s022.vmdk"

[smartgroupvoip]

Thanks for the help.

I will try recover with scalpel - scan

Any ideas for recovering the other disk for which i do have the flat file IDINET-Server.vmdk but wont load after loosing IMDEAidinet-flat.vmdk ?

Thanks again

[continuum]

> Any ideas for recovering the other disk for which i do have the flat file IDINET-Server.vmdk but wont load after loosing IMDEAidinet-flat.vmdk ?

Not sure if I can follow ?

That question was already by Andre - you reported that the attempt failed.

But reading the details I have too assume you made a mistake when you tried it.

With all info I have seen so fat simply setting

scsi0:1.present = "false"

should do the trick.

[smartgroupvoip]

No luck. setting scsi0:1.present = "false"

I'm guessing it's the same as what andre asked me to do by delete the lines referencing to scdi0:1 drive

Result stil the same: Unable to enumerate all disks.

Thanks anyway.

What I dont understand is that having all the files for this vm hd1 I'm unable to mount it.

I'm starting to think that even if I recover the missin flat file the result will be the same.

Unable to enumerate all disks.

Thanks both for the time and help