Fusion Operation on File Failed Error

[vDesktop101]

I continue to receive the following error on fusion 8.5.6 (5234762)

The operation on file (VMDK Filename) failed.

If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly.  If the file resides on removable media, reattach the media.  Select retry to attempt the operation again.  Select Cancel to end this session.  Select continue to forward the error to the guest operating system.

I have tried moving to different directories on MAC.  I have even tried moving to NAS device.   I even re-imaged with different directory.   No luck.  Any other ideas would be greatly appreciated.

The Mac is 10.12.3. 12-Cores, 128 GB of memory.

The VM is 4 proc on 2048 GB of memory.

[Mikero]

Could you tell us more about the environment?
What Mac model are you using?

Is the VM local to the machine?

Did you do anything to it recently?

The error is generic, and could indicate a number of things going wrong, and it depends on what you're doing.

If you could post the output of your Help > Collect Support Information, that would be helpful as well.

[vDesktop101]

Yeah.. it is an odd one.

Here are the specs for the MAC:

Mac Pro (Late 2013)

Processor 2.7 GHz 12-Core Index Xeon E5

Memory 128 GB 1066 Mhz DDr3

The VM is local.   I have stopped any and all replication items like drop box, google drive, etc.  I have even moved the VM from one directory to another with no luck.

I have uploaded the support log to the post.

[Mikero]

Thanks for the extra detail.

The system.log file by itself isn't very helpful unfortunately. Typically we'll look at that when we've identified errors and associated timestamps within the VMware logs. I.e. error in vmware.log at 1:30, check system.log at 1:30 to see what's happening there around the same time. This is why we gather a bunch of different logs and config files when you click help > collect support information, it's all about event correlation.

[vDesktop101]

This is the repeat of the error on the VMware log.  Is as if it can't even open the file.  It seems to work for a few hours and then times out.   I ran a hardware check on the HD and it came back clean.   I even did the Apple diagnostic with no luck.

2017-03-29T18:18:03.129-06:00| usbArb| I125: Log for VMware USB Arbitration Service pid=490 version=12.5.5 build=build-5234762 option=Release

2017-03-29T18:18:03.129-06:00| usbArb| I125: The process is 64-bit.

2017-03-29T18:18:03.129-06:00| usbArb| I125: Host codepage=UTF-8 encoding=UTF-8

2017-03-29T18:18:03.129-06:00| usbArb| I125: Host is Mac OS X 10.12.3 (16D32) Darwin 16.4.0

2017-03-29T18:18:03.124-06:00| usbArb| I125: VTHREAD initialize main thread 3 "usbArb" tid 5062

2017-03-29T18:18:03.125-06:00| usbArb| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-03-29T18:18:03.126-06:00| usbArb| I125: PREF Optional preferences file not found at /Library/Preferences/VMware Fusion/config. Using default values.

2017-03-29T18:18:03.126-06:00| usbArb| I125: DictionaryLoad: Cannot open file "/Applications/VMware Fusion.app/Contents/Library/settings": No such file or directory.

2017-03-29T18:18:03.126-06:00| usbArb| I125: PREF Optional preferences file not found at /Applications/VMware Fusion.app/Contents/Library/settings. Using default values.

2017-03-29T18:18:03.126-06:00| usbArb| I125: DictionaryLoad: Cannot open file "/Applications/VMware Fusion.app/Contents/Library/config": No such file or directory.

2017-03-29T18:18:03.126-06:00| usbArb| I125: PREF Optional preferences file not found at /Applications/VMware Fusion.app/Contents/Library/config. Using default values.

2017-03-29T18:18:03.127-06:00| usbArb| I125: DictionaryLoad: Cannot open file "/var/root/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-03-29T18:18:03.127-06:00| usbArb| I125: PREF Optional preferences file not found at /var/root/Library/Preferences/VMware Fusion/config. Using default values.

2017-03-29T18:18:03.127-06:00| usbArb| I125: PREF Disabling user preferences because disableUserPreferences is set.

2017-03-29T18:18:03.127-06:00| usbArb| I125: PREF Failed to load user preferences.

2017-03-29T18:18:03.131-06:00| usbArb| I125: DICT --- GLOBAL SETTINGS /Applications/VMware Fusion.app/Contents/Library/settings

2017-03-29T18:18:03.131-06:00| usbArb| I125: DICT --- NON PERSISTENT

2017-03-29T18:18:03.131-06:00| usbArb| I125: DICT --- USER PREFERENCES

2017-03-29T18:18:03.132-06:00| usbArb| I125: DICT --- USER DEFAULTS /var/root/Library/Preferences/VMware Fusion/config

2017-03-29T18:18:03.132-06:00| usbArb| I125: DICT --- HOST DEFAULTS /Library/Preferences/VMware Fusion/config

2017-03-29T18:18:03.132-06:00| usbArb| I125: DICT --- SITE DEFAULTS /Applications/VMware Fusion.app/Contents/Library/config

2017-03-29T18:18:03.133-06:00| usbArb| I125: USBArbRuleStore: Loading device rules from '/Library/Application Support/VMware/usbarb.rules'.

2017-03-29T18:18:03.133-06:00| usbArb| I125: VMware USB Arbitration Service Version 15.2.0

2017-03-29T18:18:03.594-06:00| usbArb| I125: USBArbM: UsbArbBackendInit: Successfully opened VMware USB Arbitrator service.

2017-03-29T18:18:03.594-06:00| machPoll| I125: VTHREAD start thread 4 "machPoll" tid 5119

2017-03-29T18:18:03.701-06:00| usbArb| I125: USBArbM: com.vmware.kext.vmioplug.15.2.0 loaded by VMware USB Arbitrator service.

2017-03-29T18:18:03.704-06:00| usbArb| I125: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.

2017-03-29T18:18:03.705-06:00| usbArb| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-03-29T18:18:03.706-06:00| usbArb| I125: SOCKET connect failed, error 2: No such file or directory

2017-03-29T18:18:03.706-06:00| usbArb| I125: USBArb: Failed to connect to the existing arbitrator.

2017-03-29T18:18:03.715-06:00| usbArb| I125: USBArb: UsbArbPipeConnected: Connected to client, socket:4

2017-03-29T18:18:03.716-06:00| usbArb| I125: USBArb: Client 274 connected (version: 7)

2017-03-29T18:18:06.227-06:00| usbArb| I125: USBArb: Closing client, error:22

2017-03-29T18:18:06.227-06:00| usbArb| I125: USBArb: Client 274 disconnected

2017-03-29T18:18:06.295-06:00| usbArb| I125: USBArb: UsbArbPipeConnected: Connected to client, socket:4

2017-03-29T18:18:06.295-06:00| usbArb| I125: USBArb: Client 558 connected (version: 7)

2017-03-29T18:18:06.296-06:00| usbArb| I125: USBArbM: USBArbBackendCleanup

2017-03-29T18:18:06.296-06:00| usbArb| I125: MachPoll: mach_port_extract_member failed for port 6423 (12)

2017-03-29T18:18:06.296-06:00| usbArb| I125: USBArbM: USBArbBackendCleanup: Closed VMware USB Arbitrator service.

2017-03-29T18:18:06.297-06:00| usbArb| I125: USBArb: Client 558 disconnected

2017-03-29T18:18:06.298-06:00| usbArb| W115: USBArb: Exiting with error:0

[wila]

Hi,

PMJI, your vmware.log snippet complains about something else..

Those entries are about the USB arbitrator.

IOW the parts that take care of USB integration, your error on the first post does suggest you never get that far.

Please just attach the whole vmware.log or post the support bundle that Mike asked for.

Also please do not copy&paste the contents, but instead use the attach button in the bottom right of your reply window.

It would be the vmware.log file that is located in your virtual machine bundle that we would need to see.

Another thing I noticed is that your virtual disk has -flat.vmdk in the name.

That suggests that this VM is originally coming from vSphere and while that should work, the flat format is not a standard VMware Fusion format.

Did it ever work on this VMware Fusion?

Have you checked file permissions?

--

Wil

[vDesktop101]

So the image of the MAC is NET New.  The VM was created fresh and placed into the following directory /Applications/Virtual Machines.localized/

In regards to the logs, they were too large to attach.   We tried this at the beginning.   So, I placed them here for download.  Dropbox - VMware Fusion Problem Report 2017-03-31 at 08.34.46.zip

As it pertains to the permissions, they are set for read/right for everyone.

I hope this helps

[wila]

Hi,

Your system.log is over 1.3 GB in size.. that's not normal.

I had a look at the vmware.log file and it ends with this:

2017-03-30T16:11:32.776-06:00| Worker#6| I125: FileIOErrno2Result: Unexpected errno=5, Input/output error
2017-03-30T16:11:32.777-06:00| vmx| I125: VMXAIOMGR: Retry on read "/Applications/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-flat.vmdk" : Input/output error.
2017-03-30T16:11:32.777-06:00| vmx| I125: VMXAIOMGR: system : err=50002 errCode=5 freeSpace=713262776320
2017-03-30T16:11:32.777-06:00| vmx| I125: VMXAIOMGR: "/Applications/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-flat.vmdk" : read s=167133184 n=4096 ne=1, fai=0
2017-03-30T16:11:32.777-06:00| vmx| I125: VMXAIOMGR:             v[0]=18FD98000:4096
2017-03-30T16:11:32.798-06:00| Worker#2| I125: FileIOErrno2Result: Unexpected errno=5, Input/output error
2017-03-30T16:11:32.798-06:00| vmx| I125: VMXAIOMGR: Retry on read "/Applications/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-flat.vmdk" : Input/output error.
2017-03-30T16:11:32.798-06:00| vmx| I125: VMXAIOMGR: system : err=50002 errCode=5 freeSpace=713262690304
2017-03-30T16:11:32.798-06:00| vmx| I125: VMXAIOMGR: "/Applications/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-flat.vmdk" : read s=167133184 n=4096 ne=1, fai=0
2017-03-30T16:11:32.798-06:00| vmx| I125: VMXAIOMGR:             v[0]=18FD98000:4096

Normally that means hardware errors and the size of your system.log seems to correlate with that (sorry as I'm a volunteer helping out I'm not that inclined to go search in a >1GB size system.log)

But I'd say that if you go search in the system.log around that same time as in the log that it will be filled with hardware read errors.

IOW I suspect your physical disk is failing.

edit: ..and another thing. The /Applications folder is protected in in macOS, you should not try to put any user data under there as  the location is "virtualized" so will indeed not be found. So that is a strange location to try and put your virtual machines. This would have been OK in older versions of OS X, but not now anymore.

--

Wil

[ccalabro]

I have the same error on a machine where I know it is the physical hard drive being on its last legs.