![]() Based on the install method for the Mac itself, the most likely culprit is the Mac Migration Assistant, which was used to move from an old Mac to the new one (both already on El Cap and Fusio n 8.1.0)ĩ. This caused the installer to fail, as it was trying to do things as "root", which should have had permissions (as UID 0), but was failing due to lack of permission, as UID 502Ĩ. Looking at some Mac account info, it was noticed (by "dariusd") that the root user had the wrong UID:ħ. In some of those functions it showed the Repair tool as referencing UID 502 instead of UID 0, like The logs showed that " VMware Fusion| W115: InstallFusionMakeValid: Repair tool failed:" followed by log lines showing all the sub functions.ĥ. The installer drops useful log files in ~/Library/Logs/VMWare Fusion/ with names like "vmware-fusion.log" and "vmware-fusion-NN.log" which are the logs from prior installer runs.Ĥ. In this case, the installer couldn't complete one of the steps. It was a problem with Mac OS X (see below).ģ. It was also NOT a corrupt download problem. In this case, the installer and VMWare software wasn't the problem. VMWare Fusion is damaged, etc message can be caused by many things.Ģ. Let me summarize here, so people don't have to read the whole thread:ġ. I can open and run all my VMs, so the VMWare Fusion portion of this is done. I was just so gobsmacked, since Fusion and Mac OS has been so stable for me, for years, that I just wasn't expecting it to not "just work".Īnd, if all else fails, then I'll re-install. Since I'm already this deep into this, I might as well sort it before some other VMWare Fusion user gets hit with it too. I suspect that the last remaining problem ("can't see previously existing VMs") will also turn out to be another permission problem. Better that I deal with it and sort it out than one of our end users. Tracking down all the b0rk'ed permissions will be interesting, too.Īlso, we have enough of a fleet of Macs at work, that someone will likely come across this again. Changing the UID of root to make the fix is just amusing, for a very demented definition of amusing. I've dug into UNIX/Linux systems at the kernel and driver level, so I think at this point it's just going to be finding the Mac-specific bug or perm problem. I'm pretty comfortable with the command line (my first UNIX was Programmers Work Bench), I'm just always learning the new and fascinating ways that Apple has abused poor little BSD. The installer was just the victim here And I'm collateral damage! I originally thought this was an installer bug, which was completely wrong. At this point, it's almost become a challenge.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |