Backup & Recovery

Dear members

im try to attach my flat vmdk file but vmware cannot open or show a error

how im can attach vmdk in machine or extract contents?

Thanks

Almir

Hi Almir MicroMarket​,

If you have the flat.vmdk  files, you can re-create the missing VMDKs --> VMware Knowledge Base

Hope that helps

I did this procedure but it doesn't work, see photo

Moderator: Thread moved to the vSphere Backup & Recovery area.

What files do you have, and do you not have?

You mentioned an error but didn’t say what it was and when you saw it?

im have the flat.vmdk

Did you edit the VMDK to point to existing flat disk ? Run following commands inside VM folder and share the outputs:

1. ls -l 

2. cat newcreated.vmdk

You still didn't give any info on the specific error or when you encountered it, but from the little you have said the KB article should help if you follow the process correctly.

im dont receive any error

but virtual disk power on without space and in raw format

You can not  attach a flat.vmdk to a VM.

You must assign the descriptor-vmdk for the flat.vmdk instead.

Please do NOT create a new descriptor-vmdk following the Knowledgebase-article that was referenced here - that can make matters worse.

Please provide the error messages you received so far.

Please also look up the exact size of the flat.vmdk in bytes - then we can create a new descriptor - in case that is even necessary.

im not attach flat vmdk ! im follow the instructions  and create the vmdk file

but after vmdk power on the virtual hard disk are without files

see the image

what is the solutions to rescue the disc?

have any windows software to extract the files ?

Take a deep breath and relax.

Now tell us what you exactly have ...

Dear Continuum

this vmdk is a secondary disk and have important files

im need help

im do this tutorial but without sucess VMware Knowledge Base

please help me

see image

Hi There,

Screenshots from Windows is not much of a help. As requested earlier, we need details about the VM files within vSphere

Please share the following:

1. SSH to ESXi host --> navigate to VM folder --> Run  the following command to list all VM files: ls -al

2. Run following against the flat.vmdk for which we need to re-create base vmdk file: ls -l   flat.vmdkfile            ==> replace the file name here with the actual flat.vmdk file

3. Run following command against the new VMDK which was created after referring the KB provided earlier:  cat  vmname.vmdk    ==> Replace the file name here with the newly created vmdk file

I hope the instructions are clear

im do this steps but vmdk power up blank

Again. Is there an issue sharing the information requested a couple of times now ?. If you do not want to share the VM name, you can censor the name and share the file extensions and their size

We need to first validate the VM files we have within vSphere to begin some troubleshooting and without that information, we are just going in circles and cannot come to any conclusion.

So let's start from the beginning. Please share information requested about the VM files.

Can I try to send or vmdk to voice try to help me?

he has 65gb

If you could provide the output of 3 commands I requested earlier, I can provide some instructions. We cannot view the contents of flat.vmdk.

As of now, we don't even know if the VMDK files which we have are good or corrupted.

what commands? im do these steps
VMware Knowledge Base

I am not sure if the replies are being skipped or you are not getting my replies.

I believe this is the 3rd time, I am requesting for these information. Let me paste it again for your reference:

1. SSH to ESXi host --> navigate to VM folder --> Run  the following command to list all VM files: ls -al

2. Run following against the flat.vmdk for which we need to re-create base vmdk file: ls -l   flat.vmdkfile            ==> replace the file name here with the actual flat.vmdk file

3. Run following command against the new VMDK which was created after referring the KB provided earlier:  cat  vmname.vmdk    ==> Replace the file name here with the newly created vmdk file

you are not understand

im will explain ! um do the clone of second hd

and my storage crashes

im only have the second hard disk vmdk file inside folder

and im do these steps , is the same processhttps://kb.vmware.com/s/article/1002511

see this site - VMware Knowledge Base

Hi

If you are posting a issue here, you need to ensure that detailed information about the issue is posted here, otherwise nobody can help you.

So far, we are going in circles and have not received any information from you that can be used to help you further. If you cannot provide the information requested, we cannot help you.

Once again, you need to provide the list of files you had before following the KB and what you have now.

I had taken some time and provided some commands in my last reply(3 times so far). Any reason, why you do not want to share that information ?

Expecting you to reply with the information requested.

Hi

please stop experimenting with that knowlegebase-article.

The actions described there are Never necessary !

The idea to create a new flat file and by that allocating lots of entries in the file inventory of the vmfs

just because you need a 500 bytes file - in lucky conditions you dont do a lot of harm - but more often it makes matters worse.

Please ignore it for now ...

Apparently your descriptor-file passes the test and is accepted.

When you can boot the guest - it means the disk does not induce a panic in the guest.

Good

In daily work I see that NTFS with obscure history can appear as:

- clean

- listed as NTFS - but not mountable until you run checkdisk

- raw - minimal checkdisk run can be enough

- raw - checkdisk makes lots and lots of changes

- raw -checkdisk no longer helps

- if it gets worse - maybe testdisk can fix boot-sectors ?

- if it gets worse - use recovery software

....

So far I see no reason to modify the descriptor !

Boot normally into Windows

get a commandline as administrator

and run

chkdsk.exe /f /x /r E:

That may do the trick.

If not or if you feel unsure - call me and we can do it via Teamviewer.

Ulli

im tried but appears this message

the type of the file system is RAW

CHKDSK is not avaiable for RAW drivers

Next try testdisk, for a valid ntfs partition you need an identical bootsector at the start and at the end of the volume.