Hello de saint jean sebastian
Please accept my apology for the answers you received until now.
Unfortunately we have to live with a rising number of over-motivated users that apparently do not check the stuff they write
against any ethical codec such as for example the Hippocratic oath
| ethical code | Britannica.com
Do not post if there exists a risk that the given advice is dangerous / harmful.
Do not post if there are any doubts about the previous question.
For your future reference ....
I highly recommend to be very very careful when you read posts that have a line like this:
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
If in doubt please ignore these guys.
The motivation of these guys is questionable.
Probably they are replying to your question because they see a chance to earn some quick reward points.
The following statements that you have seen in this post:
- If you have snapshot taken earlier try to revert back so that you dont miss on data what is been written at time of removal of that disk .
-Sorry to say but there is no option to undo the changes with respective to disk or restore within vmware with respective to disk unless you have back up.
Are first of all no help for you at all.
Second they are not correct - or do not give you the complete story.
But this 2 are comparably harmless - this advice is the one that really makes me angry:
> VMware Knowledge Base This explains you on how to create descriptor file.
Using that advice in your scenario would be one of the most stupid mistakes ever.
This tip is one of the most dangerous pieces of VMware documentation that exist inside the Knowlegebase
When ever you see someone recommend that KB you can safely assume that that guy is:
- clueless
- never has tried that stuff himself
- does not care what the consequences will be.
@ Gayathri Shivaprasad
Consider this as a warning - if I see that you continue to post BS like this again I will use my influence here to make sure that this forum only has to deal with one of us.
Dude - the vast majority of the users here will do all they can to offer good support - some of us do this since 15 years or more.
We will not allow guys that post according to the rule "more is better"
will spoil the overall good results this community has acchieved so far.
-------------------------------------------------------------------------------------------------------------------------------------
@
de saint jean sebastien
Sorry for that rant - nothing of that has to do anything with you ...
Lets get to work.
Please immediatly stop all activities on that datastore - if you have not already done so.
Then read my instructions here: Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay
If we are lucky we may be able to restore the lost files.
Once I have seen the dump-file I can give you a reliable answer.
If possible call me via skype so that we can discuss your options ....
Ulli
skype = sanbarrow
________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...
