Windows 10 pro 32.vmwarevm/Virtual Disk-000001-s001.vmdk" failed. THis is error message generated. system freezes, pressing continue or retry does help....persistent message...annoying... Is there a solution; deleting last update or editing files?
system fusion 8.5.10
macos high sierra
windows 10 pro 32
Hi Gene,
No worries.. not everyone is active on forums, you can't know it all.
Happy to hear that you are back to business!
re. driver issue versus failing disk.
Your theory gets more plausible after having copied the virtual machine to an external disk without seeing any error messages from macOS.
It's pretty unexpected, but as I noted in the reply where I commented on the log, I _did_ indeed see an issue with the driver. I have never seen a display driver crash trigger a "not being able to read a file" error before, but it now does seem more plausible. The display driver crash did happen just before the file read error... While correlation might not be causation, it _is_ suspicious!
If OTOH you have a failing disk then now at the very least you have a copy of your VM on an external disk. So you're all covered there!
--
Wil
Only Fusion 10.x and 11.0 to 11.5 are supported on High Sierra: https://kb.vmware.com/s/article/2088571
Fusion 8.5 has been working for 5 years...2017 till august 2021....After the driver update 8.17.2.14 it generated this problem...
What driver did you update before things stopped working?
It’s still not supported, which means it’s not tested/validated.
Have you actually checked the files inside the VM package to see if they look like they should?
DRIVER 8.17.2.14. INSTALLED 8/1/21
HOW DO YOU ROLL BACK DRIVERS?
First, find the CAPS LOCK key on your keyboard 😉
Sounds like a hard disk problem at the host to me... possibly some antivirus product getting in the way.
What driver in the guest OS was that? A display driver?
Not likely to be going to cause an issue with reading a disk slice in VMware Fusion itself (you would see a guest OS error, a VMware Fusion error is not a common thing to see after a driver fails)
Btw, that driver was installed on August 1st ... we're half way down September.
--
Wil
RUNNING APPLE HIGH SIERRA WITH MCAGEE ANTIVIRUS. WINDOWS HAS DEFENDER ON IT. THE DRIVER WAS OFFERED TO ME WHILE RUNNING WINDOWS UPADTE; 8.17.2.14. DONT KNOW IF IT WAS A DISPLAY DRIVER OR NOT. THE PROBLEM HAS PERSISTED SINCE THE BEGINNING OF AUGUST , ITS JUST NOW BEING ADDRESSED. IF YOU COULD PERHAPS TELL ME HOW TO ROLL BACK THE DRIVER TO ITS PREVIOUS STATE. IF NOT, ARE THERE ANY OTHER SOLUTIONS?
THANKS,
GENE
DRIVER 8.17.2.14. OBTAINED VIA WINDOWS UPDATE.... EARLY AUGUST...
HI,
WRITING WITH ALL CAPS IS CONSIDERED AS SHOUTING.
I don't like shouting contests...
If you have a backup you can put the snapshot back. If you have made a snapshot before the update, you can go back to that snapshot. If you're asking how-to roll back a windows driver.. that's a windows question and is found in Windows under Windows updates.
The error you showed indicates that there is a problem at the macOS level, not windows.
--
Wil
Hi,
Ok, looked at the logs you provided in the first post.
In your defense I do see something weird with the display driver.. but ... in my defense..
2021-09-15T22:05:12.612-10:00| mks| I125: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.
2021-09-15T22:05:20.541-10:00| Worker#4| I125: FileIOErrno2Result: Unexpected errno=5, Input/output error
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: Retry on read "/Users/gene/Downloads/Windows 10 pro 32.vmwarevm/Virtual Disk-000001-s001.vmdk" : Input/output error.
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: system : err=50002 errCode=5 freeSpace=820014678016
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: "/Users/gene/Downloads/Windows 10 pro 32.vmwarevm/Virtual Disk-000001-s001.vmdk" : read s=278422528 n=32768 ne=8, fai=0
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[0]=1AF4DB000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[1]=1AF4E2000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[2]=1AF4E1000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[3]=1ACEE0000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[4]=1AC5DF000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[5]=1B33DE000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[6]=1ACEDD000:4096
2021-09-15T22:05:20.541-10:00| vmx| I125: VMXAIOMGR: v[7]=1AA6DC000:4096
2021-09-15T22:05:29.757-10:00| Worker#9| I125: FileIOErrno2Result: Unexpected errno=5, Input/output error
2021-09-15T22:05:29.759-10:00| vmx| I125: VMXAIOMGR: Retry on read "/Users/gene/Downloads/Windows 10 pro 32.vmwarevm/Virtual Disk-000001-s001.vmdk" : Input/output error.
2021-09-15T22:05:29.759-10:00| vmx| I125: VMXAIOMGR: system : err=50002 errCode=5 freeSpace=820012830720
2021-09-15T22:05:29.759-10:00| vmx| I125: VMXAIOMGR: "/Users/gene/Downloads/Windows 10 pro 32.vmwarevm/Virtual Disk-000001-s001.vmdk" : read s=278422528 n=32768 ne=8, fai=0
File I/O errors while trying to read a file... are a VERY high indicator that your disk is dying.
So yes the driver might be trouble.
No, it isn't the error you are seeing.
First thing you _should_ do at this stage is to try and copy the VM to an external disk. (With the VM shut down and Fusion not running)
I suspect that you will see errors then too.
--
Wil
I have seen the VMware driver updates from Windows Updates break the display on a VM on ESX 5.5 so I think he does have a an issue with the video driver update.
Copied the VM Fusion Program over to an. external drive 887mb. Did not see any errors while copying the program. What type of errors should be visible? How can you tell the HD is dying? Ready for the next step.
Gene
Didnt know proper etiquette, learn something new, thanks. Furthermore, restore the state of VM fusion back to June, up dated data and now It seems to be working fine. Running 2 hours without any problems. Thank you very much. Your insight has alleviated a good deal of aggravation.
Sincerely,
Gene
Hi Gene,
No worries.. not everyone is active on forums, you can't know it all.
Happy to hear that you are back to business!
re. driver issue versus failing disk.
Your theory gets more plausible after having copied the virtual machine to an external disk without seeing any error messages from macOS.
It's pretty unexpected, but as I noted in the reply where I commented on the log, I _did_ indeed see an issue with the driver. I have never seen a display driver crash trigger a "not being able to read a file" error before, but it now does seem more plausible. The display driver crash did happen just before the file read error... While correlation might not be causation, it _is_ suspicious!
If OTOH you have a failing disk then now at the very least you have a copy of your VM on an external disk. So you're all covered there!
--
Wil
WILA,
Once again thanks for the insight to my future problem. Will deal with the failing disk and avoid the driver update.
Sincerely,
Gene