![]() ![]() ![]() If you do, now is a good time to try restoring your backup. I am assuming at this point that you do not have a backup of the VM or its contents. If that still fails, we might be down to creating a new macOS virtual machine, attaching the existing virtual hard disk to the new VM, and using the Migration Assistant in the guest to transfer over any recoverable data from the old hard disk.Īfter running the disk checks, have you verified one more time that the virtual machine still does not boot? (Even if the disk checks say that they did not need to fix anything, I would give it a try.) If either of the above steps reported that any problems were corrected, try booting the virtual machine back into the Recovery Environment and run Disk Utility and Disk First Aid again. Hopefully it will report no problems – or at least report that it repaired any problems which were present. Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -R /Users/allenbirnbach/Documents/El\ Capitan-Birnbach.vmwarevm/Virtual\ Disk.vmdk To do this, launch Terminal and run the following command: I would also try using vmware-vdiskmanager to check the integrity of the virtual hard disk. ![]() I would suggest the following steps from here:įirstly, Run Disk First Aid on your host, just to make sure that there is no filesystem problem on your host which is creating or exacerbating the problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |