So it's been a while. Got a new job... enjoying the work from home life finally.
Anyway this post isn't about that, it's about MacOS, Big Sur and alleged changes to the boot volume/container. So at work now part of my teams job is to support the virtual platform used my all other employees. Yeah, the odd emplyee who needs a vmg uest for <insert reason> can login to an internal portal and spin one up; Windows, Linux, MacOS. Anything is game.
Anyway so I have this ticket to assist a user with expanding the primary volume on this MacOS 11.0 guest. So I tried the Disk Utility.app first.. gave me an error about not having enough MAP space. To resolve that I ran a sudo diskutil repairdisk disk0 which completed successfully. Followed up with a sudo diskutil resizeDisk0 0 which also completed successfully. I thought this was the end.
Turned out to be not.. I'd seen mention of a resizeContainer so next I tried that. One done I checked the gui Disk Utility and only Disk0 showed the full new size. All other objects underneath did not.
I've spoken with folks on ##apple and was told that this is a new Big Sur-specific change in that now MacOS boots up into what he called a 'signed snapshot'. Super interesting right? I can't find ANY documentation on this.
I really, REALLY hope someone out there has something on this.. can confirm. Please comment if so.
Thanks
No comments:
Post a Comment