VMware Cloud Community
paddymack
Contributor
Contributor

Lost local datastore: VOMA failed to check device : Not a VMFS volume 6.5 datastore

Hello, I've lost a local datastore and was if someone could help me recover it?  It looks like the partition is there but the datastore went missing. 

Reply
0 Kudos
11 Replies
continuum
Immortal
Immortal

Hello

if you provide a VMFS header dump - see Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay
and provide a download link I may be able to help.

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
paddymack
Contributor
Contributor

Ulli, thanks much - here are the files:

The datastore was comprised of two standalone disks

slot2:

https://drive.google.com/open?id=1KEKQboujZaGKcRE9Sbh8poJ8XKpEHWcc

slot6:

https://drive.google.com/open?id=1Nik-woNQwcpjACCCpe9u9NQN-bbNoLrD

Reply
0 Kudos
continuum
Immortal
Immortal

Hello

unfortunately both dumps you created are truncated - didn't gzip complain about a "short write" ?

slot 6: this datastore had the friendly name SLOT 3 and the naa-number naa.600605b005a0042024644a5a387c2ddb:1

The datastore contained the directories:

ubuntu-file-server

cedge-br2

cedge-dc2

cedge-br3

csr1000v-ucmk9.BLD_V1611_THROTTLE_LATEST_20190521_031238_V16_11_1_28-vga

It maybe possible to recover

ubuntu-file-server_2-flat.vmdk - 64 GB
ubuntu-file-server_1-flat.vmdk - 1.2 TB

slot 2: this disk may have been used as an extent for another datastore.
Cant say more about slot 2 - the dump is just 300mb - not  enough to say more than just " may have been used as an extent for another parent datastore."

As the VMFS-version is 6 even a full 1536 MB dump is not enough to create an extraction script for both ubuntu-vmdks.
Anyway - please explain

1. what you need to recover
2. how exactly were both disks used ?
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
paddymack
Contributor
Contributor

Ulli,

Yep it did say short write and I didn't realize that meant it was truncated.  Also I think I have confused which device ID for which slot on slot 3 - I think I renamed one of them from within ESXi at some point, because VOMA reports two slot 3's - so perhaps it is the other one!

The two standalone disks in slot 2 and slot 6 were used as a datastore, one was used to extend the other's size.  No RAID here.

My end objective is I would like to recover the VM's on this datastore - the various ova's and iso's that were on there aren't important.

Should I re-upload the files but larger size?  Or do you have instructions for the script and I can try to tackle it?

Reply
0 Kudos
paddymack
Contributor
Contributor

Ulli,

Can see if these are the correct files?  These are each 1.5G.  But I can't figure how to open them to verify anything - tried various text editors.

A sample of the VMs I'm looking for are:

router1, router2, router3, router4, vbond, vbond2, vbond3, vsmart, vsmart2, vsmart3....

slot2:

https://drive.google.com/open?id=1znQKadZSMDH7TrpB7JU0Axeat7w-G1_S

slot6

https://drive.google.com/open?id=11xxF7_Lo-Ze6bK5TJDV2Wf9vxkDb7NY2

Thanks!

Reply
0 Kudos
continuum
Immortal
Immortal

Posted this before I saw last reply ....

Let me sum it up:

you provided 2 dumps:

SLOT6.1536

device: naa.600605b005a0042024644a5a387c2ddb:1
this VMFS volume apparently used the datastorename SLOT 3

this VMFS volume apparently was NOT expanded with a further extent

this VMFS volume probably had the following VMs

ubuntu-file-server

cedge-br2

cedge-dc2

cedge-br3

csr1000v-ucmk9.BLD_V1611_THROTTLE_LATEST_20190521_031238_V16_11_1_28-vga

SLOT2.1536
device: ??? unknown
this VMFS-partition very likely was used as an extent to expand another datastore but probably not naa.600605b005a0042024644a5a387c2ddb:1

To me this looks like a third vmfs-volume is involved ....
Anyway : lets start with the basics :

show a file-listing of the devices in /dev/disks

also show the result of
esxcfg-scsidevs -m
For the further communication lets reference the disks by their naa-number.
Yes - we will need complete dumps for all involved partitions - once we know which partitions that are.

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
continuum
Immortal
Immortal

slot6.1536 is 785 MB - but needs to be 1536 Mb


________________________________________________
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

https://drive.google.com/open?id=11xxF7_Lo-Ze6bK5TJDV2Wf9vxkDb7NY2
that file is still too small ! - a complete dump has 1536 MB
other dump is ok now


________________________________________________
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
paddymack
Contributor
Contributor

dang, google drive and my workstation are thinking it's 1.5G

re-published here: if this doesn't work I'll do the data dump again

https://drive.google.com/open?id=1PcPeLT1EbXUTKPoYsBtK-G8HQPPlYtwH

Reply
0 Kudos
continuum
Immortal
Immortal

slot6 is ok now - but it is not the volume that has the VMs:

router1, router2, router3, router4, vbond, vbond2, vbond3, vsmart, vsmart2, vsmart3....

please provide the details I asked for.


________________________________________________
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
paddymack
Contributor
Contributor

ahh ok, I think I'm toast then - the only other volumes are disks that are present and accounted for.

i do appreciate your help today!

Reply
0 Kudos