This did not work and my computer froze except for the mouse, so that a reset via the power button was necessary.The topic in itself is a surprising element to many users till this date as they wonder as to how it is possible to run Windows on Mac. P.S.: At first I tried to grow the container from the operating system, and not from the recovery mode, and run diskutil ap resizeContainer disk0s2 0 in the terminal without any unlocking. | APFS Volume Disk (Role): disk1s3 (Recovery) | APFS Volume Disk (Role): disk1s2 (Preboot)
| APFS Volume Disk (Role): disk1s1 (No specific role) Verify the result with diskutil list and diskutil ap list.ĭiskutil list: /dev/disk0 (internal, physical):Ģ: Apple_APFS Container disk1 121.1 GB disk0s2Ġ: APFS Container Scheme - +121.1 GB disk1ġ: APFS Volume Macintosh HD 60.1 GB disk1s1ĭiskutil ap list: APFS Container (1 found) The zero at the end is a magic number that makes sure the container is grown to the maximum. Grow the disk0s2 container: diskutil ap resizeContainer disk0s2 0 Run some checks on the disks, containers, and volumes that we are going to modify: diskutil verifyDisk disk0 Then run diskutil ap unlockVolume 9AFD4588-AA1A-3413-9335-6C8DA8EA3973Īnd enter your password. Unlock disk1s1 by running diskutil ap list and copy its UUID, in our case it's 9AFD4588-AA1A-3413-9335-6C8DA8EA3973. The commands diskutil list and diskutil ap list are helpful to single out the right ones. For some reason, when I booted into the Recovery mode my disk1 became disk2 and disk1s1 became disk2s1. This container accommodates the synthesized disk1, which, in turn, contains the volume disk1s1. The architecture of the hard drive is the following: disk0 is the physical storage, on top of it is the container disk0s2. Then open the Terminal via Menu Bar → Utilities Probably it is a good idea to make a Time Machine backup before messing with the hard drive.ĭelete disk0s3 by running sudo diskutil eraseVolume "Free Space" %noformat% /dev/disk0s3īoot into the Internet Recovery Mode by restarting your computer and holding Alt+ Cmd+ R while booting. Here are the steps that led to the solution: This was probably the bootloader for the other OS.
One hint to this is is the volume disk0s3 that one can see on the first screenshot. The problem seemed to be that in the past I installed a different OS using Bootcamp, and after I deleted it Bootcamp failed to return the space that was allocated for it, so that 50GB of space got orphaned.
At this point I would like to thank him for all the time he took to help me. The amazing klanomath, who posted the first reply guided me through the debugging process and we were able to solve the problem.
0 kommentar(er)
