Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Lost partition after BootCamp

franzkfk

franzkfk

macrumors regular
Original poster
Feb 14, 2011
243
167
Czech Republic
Hi,

I have tried to install BootCamp on my MacBook Air early 2015, 128GB

It did not go well. Somekind of an error. So after that I went again through BootCamp to make sure that the partitions will be merged into one again.

I have alocated cca 40GB for Win10

The problem is that after that I see only 84GB free space on my 128GB disc. It shows 121.33 GB disc but only 84GB I can use.

What should I do?

I did tried recovery mode and delete all containers and partitions. It still says 84GB instead of 121.33GB.

Thank you.
 
Put screenshots of Disk Utility's Partition overview (as in select the drive and click the Partition button - screenshot that. To select the drive itself, Disk Utility must be set to show all devices from the View menu bar option)
Also screenshot the output of running
diskutil list
from the Terminal
 
Snímek obrazovky 2020-10-14 v 13.55.13.png
Snímek obrazovky 2020-10-14 v 13.54.00.png

[automerge]1602676593[/automerge]
I am not an IT guy so please count with it:)
 
So, in Disk Utility like you have it there in your screenshot, click the partition button. I don’t speak Czech but it’s right next to First Aid. You’ll get like a Pie Chart. See if you can’t use that to “expand” the APFS container to the full disk. - If you get confused or you can’t expand it screenshot after you click Partition on the disk
 
Snímek obrazovky 2020-10-14 v 15.32.07.png

Yeah ... I cannot put it back into the original state even though it does show capacity of 121,33GB. I can only divide those 84GB. I can't do anything else.
 
So i Tried "diskutil ap resizeContainer /dev/disk1 100
Snímek obrazovky 2020-10-14 v 16.01.41.png

After that I have tried just sudo (I am really an amateur:) but it might help?
Snímek obrazovky 2020-10-14 v 16.01.49.png


After that I tried without percentage
Snímek obrazovky 2020-10-14 v 16.02.02.png

And lastly without any numbers
Snímek obrazovky 2020-10-14 v 16.02.10.png
 
Could've sworn percentages was allowed for that command - Looked it up apparently you just put 0 for reclaiming all available space on the physical storage.

A little general note, the term "running something as sudo" would mean doing it in the following form

sudo <command> <flags> <arguments>.

So in this case it would be

sudo ap resizeContainer disk1 0

Mind, for this command /dev/disk1 and just disk1 are equivalent
 
franzkfk said:
View attachment 966351 View attachment 966352
[automerge]1602676593[/automerge]
I am not an IT guy so please count with it:)
Click to expand...

I went back and studied the output from this again. disk0s3 and s4 are not there, yet there are weirdly uniform s5 6 and 7. That is a bit odd.

franzkfk said:
View attachment 966438
not a good news, isn't it? :/
Click to expand...

The easiest fix at this point is to create a backup, wipe the whole disk and reinstall macOS and restore from your backup.

We can proceed to fix this without doing so, but it very likely will be quite a process, and there's a risk of data loss and things getting messed up by it anyway.

If the partition table still has the APFS container at the top, removing the later partitions could fix this. If the alignment of the APFS container is pushed down the partition map, well, messing around with GPT and pushing around partitions gets hairy.

If you can make a backup and just wipe and reinstall that's far, far easier, but I am willing to help guide you through an attempt at fixing it on a live system
 
Oh also, I recommend Googling around for "resizing APFS container to full disk" - there's many articles out there on the various causes and explanations and such for all of what can happen and be done in these situations
 
I can wipe it. I don't mind. The problem is that I did it and during recovery it still shows 84GB. Or should I do it differently?
 
franzkfk said:
I can wipe it. I don't mind. The problem is that I did it and during recovery it still shows 84GB. Or should I do it differently?
Click to expand...

Inside recovery make sure to select the whole disk and not the volume or container group; In the View menu of Disk Utility make sure it is set to Show All Devices not just Show Volumes. Then pick the disk and click the Erase button, not the partition button; That should give you the ability to get the full disk back; If not, we'll use the eraseDisk command from Terminal, but try that first :)
 
What about the button called restore? Right next to the erase button. It shows “restore from Apple disc image media”.
 
franzkfk said:
Should I leave there GUID and Mac OS journal or do APFS?
Click to expand...

GUID yes, as for the file format, actually it doesn’t matter what you pick, so just choose APFS. Once you install macOS it will automatically convert it to APFS anyway
[automerge]1602688399[/automerge]
franzkfk said:
What about the button called restore? Right next to the erase button. It shows “restore from Apple disc image media”.
Click to expand...

Restore is for a form of cloning. So if you have a disc image - which is sort of like a snapshot of a disk, that you want to clone onto the disk itself you can use the restore button
 
Oh my GOD! It helped:D
So for those like me in the future. It is necessary just to click on “show all devices” in recovery and select the physical (base) disc. The first one.

casperes1996
Thank you! Thank you! Thank you! :)
Unfortunatelly we have a lockdown here.. sort of. Are you going to visit Prague in the nesr future? If so. Write me at franzkfk@gmail.com
You have a beer guide here and beer on me of course:)
Last question. Why does it says
container disk0s2 instead of lets’s say number 1 or 0? I mean ... why 2?
 
franzkfk said:
Oh my GOD! It helped:D
So for those like me in the future. It is necessary just to click on “show all devices” in recovery and select the physical (base) disc. The first one.

casperes1996
Thank you! Thank you! Thank you! :)
Unfortunatelly we have a lockdown here.. sort of. Are you going to visit Prague in the nesr future? If so. Write me at franzkfk@gmail.com
You have a beer guide here and beer on me of course:)
Last question. Why does it says
container disk0s2 instead of lets’s say number 1 or 0? I mean ... why 2?
Click to expand...

Hehe, you’re welcome. Sadly I don’t think I’ll be traveling anywhere soon but I really appreciate the offer. You can hook me up if you need a coffee guide to Aarhus Denmark as well, hehe - My details are on my website, www.theparallelthread.com

As for the numbering system, s0 is reserved for the partition map. So in this case it’s the GUID Partition Table, aka GPT. This describes where all the partitions is on disk.
s1 is reserved for EFI related things for before anything is booted up, and thus, the APFS container gets placed at s2
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back