VMware Cloud Community
JF_ID
Enthusiast
Enthusiast

VMFS datastore recovery need

continuum​ saw some of your post, probably you can help Smiley Wink

For sure there corruption on a VMFS 6 datastore for specific VM. We find the source of all these corruption. Now that fix, we try to recover one VM.

The client don't have any full vm backup (Vmdk) only internal data backup.

I have already try voma tool to check and fix(not available for VMFS6)   result : 1500 bad

Try recreate vmdk file, not working either

Look like corruption of 2 flat file (disk1 and 2). Attach file

The vm don't want to power on error "File system specific implementation of OpenFile[file] failed"

Thank for your help

27 Replies
continuum
Immortal
Immortal

Hi

I can have a look if you send a VMFS header dump - see Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay

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 ...

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Got the file, How you want to transfer the file ?

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

send you a message with the link

Reply
0 Kudos
continuum
Immortal
Immortal

Just saw your empty PM - please send another one with the link 🙂


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

My bad Smiley Happy, send you again with the link.

Reply
0 Kudos
a_p_
Leadership
Leadership

My bad , send you again with the link.

Not at all, it's a bug in VMTN's message system. It simply drops the body for new messages.

Workaround: After sending a new message, go to your inbox, and add a reply.

André

continuum
Immortal
Immortal

Wow - since when do we have that behaviour ?


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

Reply
0 Kudos
continuum
Immortal
Immortal

Dump arrived and is usable.

Please specify which vmdks you need - if possible specify name and size


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Srv-scjbdprod-flat.vmdk

Srv-scjbdprod_1-flat.vmdk

Reply
0 Kudos
continuum
Immortal
Immortal

ok

whats the size of the datastore ?


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Lun Size 2.4 TB   Datastore show 2.34 TB

Reply
0 Kudos
continuum
Immortal
Immortal

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=fffffffe

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 125829120 VMFS "srv-scjbdprod-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "7832"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "9c2f856bd61f526019620da7fffffffe"

ddb.uuid = "60 00 C2 9e 9e b3 74 d7-4b d0 00 d3 98 a8 85 b2"

ddb.virtualHWVersion = "13"

and this one

# Disk DescriptorFile

version=3

encoding="UTF-8"

CID=330ecafd

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 335544320 VMFS "srv-scjbdprod_1-flat.vmdk"

# Change Tracking File

changeTrackPath="srv-scjbdprod_1-ctk.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.deletable = "true"

ddb.geometry.cylinders = "20886"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "1356e0e0f1d18e7773ed4663330ecafd"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10279"

ddb.uuid = "60 00 C2 96 ac 59 e5 16-b2 c6 31 e3 c0 ee 86 d3"

ddb.virtualHWVersion = "8"

Are this the ones you need ?

Then I assume first one has a size of 60 gb and the second one has a size of 160gb ?

Do you agree ?


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Exactly.

Reply
0 Kudos
continuum
Immortal
Immortal

Can you still see the flat.vmdks via putty ?

If yes - please try to run

vmkfstools -p 0 srv-scjbdprod-flat.vmdk > /tmp/srv-scjbdprod-flat.map

vmkfstools -p 0 srv-scjbdprod_1-flat.vmdk > /tmp/srv-scjbdprod_1-flat.map

If that works attach the files to your next reply

This VM had atleast 2 more vmdks - what is the state of those ?


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Yes i can see both file

Both command give me

Could not open file: Invalid argument

The two others disks look good, Vmware.log indicate that his able to open _2 and _3 flat files

Reply
0 Kudos
continuum
Immortal
Immortal

Identifying the flat.vmdks by size is inconclusive.

Please give me the inode-numbers.

Run

ls -ilah * > /tmp/inodes.txt

please


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

Reply
0 Kudos
JF_ID
Enthusiast
Enthusiast

Here the result

Reply
0 Kudos
continuum
Immortal
Immortal

Can we switch to a Teamviewer session ?

Please show the size of the .sf files on that datastore.

cd to the root of the datastore

and run

ls -lah

and show the result


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

Reply
0 Kudos
continuum
Immortal
Immortal

Just saw this in your first post:

Try recreate vmdk file, not working either

Please explain what exactly you have done ! I hope you dod not follow the VMware Knowledgebase ???


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

Reply
0 Kudos