o) Create a new VMWare machine of the same guest OS.
o) Assign the corrupted VMDK file as additional HDD to the new machine. VMWare machine config allows you to add an existing HDD (VMDK file) to a machine.
o) Browse your corrupted virtual HDD. Enjoy!
Advertisements
Worst fix ever!
LikeLike
Agreed– Dan said it best: Worst fix ever! This is just stupid!
LikeLike
Guys, this is a plain disaster recovery solution.
I was in a panic when my VMDK was unusable for booting. Attaching it as an additional drive to a functional VM helped me get the data back. Nonetheless, I welcome your critic.
LikeLike
This should work, especially if the disk isn’t too badly damage, but you’re getting frustrated when the machine runs into the damaged area and the entire VM shuts down without allowing you to continue despite the error.
LikeLike
How if the Vmdk file can not open because of medium files error?
LikeLike
I am unaware of solution to such a problem 😦
LikeLike