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?
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
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.
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.
In daily work I see that NTFS with obscure history can appear as:
- 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
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.
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.