AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Monterey downgrade to big sur1/19/2024 ![]() VM_ALLOCATE (reserved) 40K 3 reserved VM address space (unallocated) Rosetta IndirectBranch (reserved) 32K 1 reserved VM address space (unallocated) ReadOnly portion of Libraries: Total=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%) Termination Reason: Namespace SIGNAL, Code 0x5Īssertion failed [header->version /usr/lib/dyldĠx7ffdffe62000 - 0x7ffdffe91fff runtime (203.58) /usr/libexec/rosetta/runtimeĬalls made by other processes targeting this process:Ĭalls made by all processes on this machine: Path: /Applications/Skype.app/Contents/MacOS/SkypeĪnonymous UUID: C7BA2416-51A1-0A2A-0260-D3A2672D9A06Įxception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffe7ed38 (brk 1) ![]() I've heard people say that a Time Machine backup will preserve all your settings, but that obviously didn't work out for me. In conclusion, would-be beta testers beware. It's a good thing I'm retired, because this took hours (admittedly, my records regarding license keys should be a lot more centralized). Unfortunately almost everything had to be reactivated email accounts had to be recreated and so on. I also copied various extensions, etc., hoping that I wouldn't have to reactivate all my software. Once the MacBook was booted into the fresh Big Sur install, with the same account name as I'd used previously, I was able to browse the problematic Time Machine backup using the Finder and did get back all my applications, data, a Parallels Windows VM, etc. Yes, I "should have known" all this, but it's a horrible process. Googling that problem, I was reminded that you not only have to erase the SSD using Disk Utility, you also have to "erase computer" using another menu in the Recovery environment, and you have to make sure that the M1 MacBook has been removed from your Apple account before you continue. I tried to install three times and each time it would hang at the user account creation screen. I wound up having to reinstall Big Sur from a bootable USB stick (created via MDS running on another machine). odd since this was the sole backup that had ever been run and my SSD is only 250GB. Right before installing Monterey I had made a Time Machine backup on an external drive, telling myself "I could always revert quickly - what could go wrong?" To make a long story short, I was unable to use Migration Assistant to restore from my Time Machine backup, because the Assistant for some reason decided that my backup was over 650GB in size. When it was on the machine, most things worked - with some exceptions that have been discussed in other threads - but I decided that I'd be better off reverting to Big Sur. I decided to try Monterey on my M1 MacBook Pro and wish I could get back the day that it cost me. ![]()
0 Comments
Read More
Leave a Reply. |