Deleted Boot Camp Partition in Disk Utility, I cannot resize Macintosh HD to full size.

[samdaman222]

I deleted my boot camp partition through disk utility (i realise now this was a mistake). Disk utility now tells me I only have 619GB total storage (not 1TB). I’ve tried fresh installs and restoring the drive with time machine back up but have not had much promise.

Any suggestions would be welcome.

 

[casperes1996]

I deleted my boot camp partition through disk utility (i realise now this was a mistake). Disk utility now tells me I only have 619GB total storage (not 1GB). I’ve tried fresh installs and restoring the drive with time machine back up but have not had much promise.

Any suggestions would be welcome.

This is a result of CoreStorage.

You need to boot into recovery mode, and set the CoreStorage partition to fill the entire physical drive. I may be mistaken on the exact command, but I believe it is diskutil cs resize (UID of the CS volume) 100%
You can Google "resizing CoreStorage" for more details

And if you have any issues with it feel free to ask, I'll gladly help in more details if needed

 

[Darmok N Jalad]

If you're trying to do it from a High Sierra install, Disk Utility by default doesn't show "devices" anymore, it just shows the Volumes. If you're attempting a clean install, you have to set the Disk Utility "View" to all devices, and from there you should be able to Erase the entire disk and start over.

 

[Fishrrman]

This way is absolutely, positively guaranteed to work:

1. Get an external drive
2. Get CarbonCopyCloner (or SuperDuper). Both are FREE to download and use for 30 days.
3. Use CCC or SD to clone your Mac [HFS] partition to the backup
4. Boot from the [bootable] cloned backup
5. Use Disk Utility to COMPLETELY ERASE the internal drive. NUKE IT BACK to HFS+ with journaling enabled (only one partition)
6. Now, open CCC again, and RE-clone the cloned backup BACK TO the internal drive.
7. Done.

Tip for the future:
DO NOT use BootCamp UNLESS you have to have a "native-bootable" Windows installation.
Instead, use an "emulation solution" such as Parallels, VMWare fusion, or the free "Virtual Box".
Fewer problems...

 

[casperes1996]

This way is absolutely, positively guaranteed to work:

1. Get an external drive
2. Get CarbonCopyCloner (or SuperDuper). Both are FREE to download and use for 30 days.
3. Use CCC or SD to clone your Mac [HFS] partition to the backup
4. Boot from the [bootable] cloned backup
5. Use Disk Utility to COMPLETELY ERASE the internal drive. NUKE IT BACK to HFS+ with journaling enabled (only one partition)
6. Now, open CCC again, and RE-clone the cloned backup BACK TO the internal drive.
7. Done.

Tip for the future:
DO NOT use BootCamp UNLESS you have to have a "native-bootable" Windows installation.
Instead, use an "emulation solution" such as Parallels, VMWare fusion, or the free "Virtual Box".
Fewer problems...

Except this doesn't actually work if the CoreStorage volume the drive has on it isn't sized for the full drive. Disk Utility won't show the actual disk, only the Core Storage shim for the disk, in which case only that portion of the disk will become available.

 

[samdaman222]

This is a result of CoreStorage.

You need to boot into recovery mode, and set the CoreStorage partition to fill the entire physical drive. I may be mistaken on the exact command, but I believe it is diskutil cs resize (UID of the CS volume) 100%
You can Google "resizing CoreStorage" for more details

And if you have any issues with it feel free to ask, I'll gladly help in more details if needed

No core storage logical volume group has been found?
[doublepost=1516783587][/doublepost]

No core storage logical volume group has been found?

It seems that my recovery drive is 300~GB which is obviously the issue. How do I resolve this?

 

[casperes1996]

No core storage logical volume group has been found?

Fair enough - that's just usually what goes wrong for me in these situations.
Could you print the output of diskutil list?

It seems that my recovery drive is 300~GB which is obviously the issue. How do I resolve this?

I'd say the easiest approach would be to just kill the Recovery Partition, and if necessary recreate it later.
I believe this should work
"diskutil eraseVolume JHFS+ 'new name for your recoveryHD (no spaces)' /dev/disk(#disk number)s(#recovery partition number)

Must be done from internet recovery or a macOS install USB

There may be other ways of fixing it, but this was the first thing I thought of. Hope it helps

 

[bfrankindy]

I deleted my boot camp partition through disk utility (i realise now this was a mistake). Disk utility now tells me I only have 619GB total storage (not 1TB). I’ve tried fresh installs and restoring the drive with time machine back up but have not had much promise.

Any suggestions would be welcome.

I have this exact same problem. I bought a pre-owned 2017 iMac and tried to completely restore it to factory settings. Unfortunately I think I handled the boot camp incorrectly. My 1TB hard drive is missing 150GB. I do not see the missing part at all in Disk Utility. Also, I get an error when trying to boot in Windows so I know I did something wrong. I don't want boot camp or windows at all. I just want my 1TB. Please let me know if you discover a solution.

 

[casperes1996]

I have this exact same problem. I bought a pre-owned 2017 iMac and tried to completely restore it to factory settings. Unfortunately I think I handled the boot camp incorrectly. My 1TB hard drive is missing 150GB. I do not see the missing part at all in Disk Utility. Also, I get an error when trying to boot in Windows so I know I did something wrong. I don't want boot camp or windows at all. I just want my 1TB. Please let me know if you discover a solution.

From what I gather, there are two possible problems here. Nr. 1 is that when you deleted your Windows partition, if merged it with the Recovery Partition instead of your main disk, and you need to delete your Recovery Partition.
2) Is that CoreStorage messed up. This seems to be the less likely one, but it's happened to me. The fix for that one is to resize the CoreStorage volume from Internet Recovery, with "diskutil cs resize (UUID of cs) 100%"

 

[bfrankindy]

Thank

From what I gather, there are two possible problems here. Nr. 1 is that when you deleted your Windows partition, if merged it with the Recovery Partition instead of your main disk, and you need to delete your Recovery Partition.
2) Is that CoreStorage messed up. This seems to be the less likely one, but it's happened to me. The fix for that one is to resize the CoreStorage volume from Internet Recovery, with "diskutil cs resize (UUID of cs) 100%"

Thank you for your response. I'm not sure how to do either of these things but I'll Google it. I do have my computer backed up so don't mind if I delete everything and have to start from scratch.
[doublepost=1517254814][/doublepost]

From what I gather, there are two possible problems here. Nr. 1 is that when you deleted your Windows partition, if merged it with the Recovery Partition instead of your main disk, and you need to delete your Recovery Partition.
2) Is that CoreStorage messed up. This seems to be the less likely one, but it's happened to me. The fix for that one is to resize the CoreStorage volume from Internet Recovery, with "diskutil cs resize (UUID of cs) 100%"

I looked up your answer number one and found this in terminal. Assume I need to erase this recovery drive? It is a little difficult for me to figure out how to do this.

 

[casperes1996]

I looked up your answer number one and found this in terminal. Assume I need to erase this recovery drive? It is a little difficult for me to figure out how to do this.

It does indeed appear your recovery drive is too big, so yeah. Let's start then

In case you've rebooted or something since your last post, you need to run diskutil list again to make sure the disk numbers are the same, otherwise, just follow along!

Hold on, I see you have a Fusion Drive. – This is where CoreStorage becomes fun to mess with....

Anyways, here goes

1) "diskutil eraseVolume JHFS+ oldRecovvery /dev/disk0s3"
2) In Disk Utility, remove the newly created partition, oldRecovery. If it merges into the MacintoshHD, you don't need to do any of the following steps. If it doesn't move on to step 3 and onwards.

3) "diskutil cs list" Note the logical volume UUID from here

4) "diskutil cs resizeStack (insert the ID from above here) 100%"

Unless I've mistyped or forgotten anything that should work. If you get any errors or it doesn't work, PM me so I'll get an email about it, and I'll get back to you with the correction ASAP

 

[bfrankindy]

It does indeed appear your recovery drive is too big, so yeah. Let's start then

In case you've rebooted or something since your last post, you need to run diskutil list again to make sure the disk numbers are the same, otherwise, just follow along!

Hold on, I see you have a Fusion Drive. – This is where CoreStorage becomes fun to mess with....

Anyways, here goes

1) "diskutil eraseVolume JHFS+ oldRecovvery /dev/disk0s3"
2) In Disk Utility, remove the newly created partition, oldRecovery. If it merges into the MacintoshHD, you don't need to do any of the following steps. If it doesn't move on to step 3 and onwards.

3) "diskutil cs list" Note the logical volume UUID from here

4) "diskutil cs resizeStack (insert the ID from above here) 100%"

Unless I've mistyped or forgotten anything that should work. If you get any errors or it doesn't work, PM me so I'll get an email about it, and I'll get back to you with the correction ASAP

Here is what happened. Not sure what to do now.

 

[casperes1996]

Here is what happened. Not sure what to do now.

Did you do the above from Internet Recovery?

 

[bfrankindy]

Did you do the above from Internet Recovery?

Did you do the above from Internet Recovery?

No. I did not realize I was supposed to do it that way.

 

[Fishrrman]

The best solution is to NUKE IT and start over.

Essentially:
- use either CarbonCopyCloner or SuperDuper to create a BOOTABLE cloned backup of the Mac partition. Both CCC and SD are FREE to download and use for 30 days.
- Boot from the cloned backup
- Use Disk Utility to ERASE the internal drive. Put it back to one partition GUID partition map, Mac OS extended with journaling enabled.
- Once DU is done, test and verify that the drive is back to one partition and "all the space is there"
- Finally, open CCC (or SD) and RE-clone the backup BACK TO the internal drive.

This is 100% guaranteed to "do the job", so long as you use HFS.
Can't say for APFS, I don't touch it or recommend it.

My advice for the future:
DO NOT use BootCamp UNLESS you absolutely positively have-to-have Windows "bootability". Instead, use a "virtual emulation" -- Parallels, VMWare, or the free "virtual box".

 

[bfrankindy]

The best solution is to NUKE IT and start over.

Essentially:
- use either CarbonCopyCloner or SuperDuper to create a BOOTABLE cloned backup of the Mac partition. Both CCC and SD are FREE to download and use for 30 days.
- Boot from the cloned backup
- Use Disk Utility to ERASE the internal drive. Put it back to one partition GUID partition map, Mac OS extended with journaling enabled.
- Once DU is done, test and verify that the drive is back to one partition and "all the space is there"
- Finally, open CCC (or SD) and RE-clone the backup BACK TO the internal drive.

This is 100% guaranteed to "do the job", so long as you use HFS.
Can't say for APFS, I don't touch it or recommend it.

My advice for the future:
DO NOT use BootCamp UNLESS you absolutely positively have-to-have Windows "bootability". Instead, use a "virtual emulation" -- Parallels, VMWare, or the free "virtual box".

Thank you for taking the time to help me. I will try what you said later today. I’m concerned, though, that this partition is no longer showing up at all in Disk Utility or terminal when checking diskutil list (see most recent above). It went from being a huge recovery partition to completely gone. I worked through it on the phone with Apple last night and they just keep recommending wiping my hard drive and reinstalling OS from internet recovery. This cleans only the 853 GB. The other 150 GB is still non-existent.

 

[casperes1996]

Thank you for taking the time to help me. I will try what you said later today. I’m concerned, though, that this partition is no longer showing up at all in Disk Utility or terminal when checking diskutil list (see most recent above). It went from being a huge recovery partition to completely gone. I worked through it on the phone with Apple last night and they just keep recommending wiping my hard drive and reinstalling OS from internet recovery. This cleans only the 853 GB. The other 150 GB is still non-existent.

Since your drive is a Fusion Drive, you need to resize Core Storage to fill the entire span of your two drives again. Alternatively you can destroy the core storage management, and either rebuild your Fusion Drive, or have it stay as two separate drives

 

[bfrankindy]

Since your drive is a Fusion Drive, you need to resize Core Storage to fill the entire span of your two drives again. Alternatively you can destroy the core storage management, and either rebuild your Fusion Drive, or have it stay as two separate drives

How do I do this? I only want one big drive. I have no use for Windows or Boot Camp.

Since your drive is a Fusion Drive, you need to resize Core Storage to fill the entire span of your two drives again. Alternatively you can destroy the core storage management, and either rebuild your Fusion Drive, or have it stay as two separate drives

 

[casperes1996]

How do I do this? I only want one big drive. I have no use for Windows or Boot Camp.

Go back to my previous comment and follow along from either Internet Recovery or a separate boot drive from your internal boot drive

 

[bfrankindy]

Go back to my previous comment and follow along from either Internet Recovery or a separate boot drive from your internal boot drive

Go back to my previous comment and follow along from either Internet Recovery or a separate boot drive from your internal boot drive

I’ll give it a try. Thanks again.

 

[bfrankindy]

Go back to my previous comment and follow along from either Internet Recovery or a separate boot drive from your internal boot drive

I just restarted into Internet Recovery. How do I get from here to Terminal so I can type in those commands?
[doublepost=1517351125][/doublepost]

Go back to my previous comment and follow along from either Internet Recovery or a separate boot drive from your internal boot drive

I figured out how to get to Terminal in Internet Recovery mode. Unable to get anything to happen correctly. I tried numbers 3 and 4 in your post from yesterday at 3:08PM. Not sure if I got the UUID correct, but is says "A percentage value (100%) cannot be specified for this operation.

I cannot use steps 1 and 2 because the recovery partition is completely gone from the diskutil after using the instructions to delete it.

 

[casperes1996]

I figured out how to get to Terminal in Internet Recovery mode. Unable to get anything to happen correctly. I tried numbers 3 and 4 in your post from yesterday at 3:08PM. Not sure if I got the UUID correct, but is says "A percentage value (100%) cannot be specified for this operation.

Try using resizeVolume instead of resizeStack

Alternatively specific the total amount of space on your drive, instead of 100%, i.e. 1000G (1000G=1TB)

 

[bfrankindy]

It says there is not enough space in the Core Storage Logical Volume Group for this operation. I think it has to do with the deleted recovery partition. I don't see it listed anywhere now.

 

[casperes1996]

It says there is not enough space in the Core Storage Logical Volume Group for this operation. I think it has to do with the deleted recovery partition. I don't see it listed anywhere now.

Was that with resizeStack? Resizing the stack should also enlarge the pg (Physical group)

 

[bfrankindy]

I just tried it again with resizeStack and 1000G and I believe it work. I'm so excited. Thank you so much for your time and effort. Is there any way I can reimburse you?