just looking for someone who maybe came across similar issue(s). My 2019 MBP had a h/w issue, and had its mainboard changed (thus ssd inclusive). I was using the last 12.x Fusion Pro, with macOS Mo...
See more...
just looking for someone who maybe came across similar issue(s). My 2019 MBP had a h/w issue, and had its mainboard changed (thus ssd inclusive). I was using the last 12.x Fusion Pro, with macOS Monterey 12.6.1. The repaired Mac came back with Ventura installed. After restoring the latest Time Machine backup, I had many compatibility issues reported by macOS, and I decided to upgrade to Fusion 13, something I'd have done soon anyway. Then, when I booted my Windows (10, 7, XP) VM's, it just asked whether they were copied or moved, and whether or not to upgrade these. They all started flawlessly. My Ubuntu 16.04 instead didn't boot, booting only showed the Grub menu, but no disk. I Looked in the logs but found nothing to chew, then I started the VM from CD (Ubuntu 22.04), and mounted the disk (/dev/sda1). I reported quite a bunch of errors, so I ran fsck, but afterwards many files (in particular, those I really needed...) contained just garbage... The very strange thing, is that I know I've used that VM successfully many, many times in the last past months, and now, regardless what backup I take from Time Machine (got about 10 months of history), 1) it doesn't boot, and 2) if I start from a live Ubuntu, the same files are always corrupted... Something looks basically wrong here (why the heck can't I start any of the previous versions of that VM), but I really can't figure out what... any idea/suggestion welcome.