Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 293210

operation on file vmdk failed - this is a VMWARE issue NOT failing drive

$
0
0

I've been getting the following error on my VMware machine.

Operation on file "[My VM Disk Name].vmdk" failed.

If the file resides on a remote file system, please make
sure your network connection and the server where this
disk resides are functioning properly. If the file resides
on a removeable media, reattach the media.
Choose Retry to attempt the operation again.
Choose Abort to terminate this session.
Choose Continue to forward the error to the guest
operating system.

 

after weeks of VMWare support giving me the run around, telling me  that my drive was failing -- which BTW I had a pretty new computer and  only part on the drive was where VMWARE is located i found a link to  others who have been having the same issue. Turns out the problem is  with VMWARE NOT the drive.

 

I've  spent weeks without my files, the backup had also been written to by  VMWARE, lost lots of time unable to answer customers and over $500 doing  fixes that their support recommended.

 

You can see the thread from other users having same  issue here http://putraworks.com/2011/05/17/vmware-workstation-operation-on-file-vmdk-failed/

We should really be suing these guys...and yet when I call support they are asking me to now pay for them to even talk to me...the cheek of it!!!

 

 

Anyways. If you have this error too and have been able to resolve it I recommend that you post the thread here so that we can build our numbers to get these khs at VMWare to sit up and take notice and get real answers for FIXING this. Not a generic it's your IO.IT's NOT!!!!

 

The current recomendation is to download winimage get your files out of vmware and move on over to Parallels. Please let me know if you find other solutions too.

Thanks


Viewing all articles
Browse latest Browse all 293210

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>