Bootcamp Issue: MBP Rebooted during partition.

[PhightinPhils26]

As the title says, my Late 2013 13" MBP rebooted itself during the partition and now the space allocated (250 GB) is gone. It's not seen under disk utility and it's not part of my MacOS boot volume.

Any suggestions on how to find it?

Edit: I think I found it using diskutil in the terminal.

New question, how would I go about getting it back. Assuming its the second of two listed (virtual).

 

[Mike Boreham]

As the title says, my Late 2013 13" MBP rebooted itself during the partition and now the space allocated (250 GB) is gone. It's not seen under disk utility and it's not part of my MacOS boot volume.

Any suggestions on how to find it?

Edit: I think I found it using diskutil in the terminal.

New question, how would I go about getting it back. Assuming its the second of two listed (virtual).

Were you in the middle of creating (or removing) the Bootcamp partition with Bootcamp Assistant?

I have occasionally experienced the partition or unpartition process go wrong and the Bootcamp space has become unavailable.

Sometimes it has been possible to simply use Disk Utility to delete the faulty partition, but more often it has been necessary to boot to an external drive and use Disk Utility from that or a third party tool with partitioning capability like Drive Genius.

Booting from the Recovery Partition may work but the RP is a partition on the same drive as the problem. Booting from an independent external drive means the affected drive is completely inactive.

 

[PhightinPhils26]

Were you in the middle of creating (or removing) the Bootcamp partition with Bootcamp Assistant?

I have occasionally experienced the partition or unpartition process go wrong and the Bootcamp space has become unavailable.

Sometimes it has been possible to simply use Disk Utility to delete the faulty partition, but more often it has been necessary to boot to an external drive and use Disk Utility from that or a third party tool with partitioning capability like Drive Genius.

Booting from the Recovery Partition may work but the RP is a partition on the same drive as the problem. Booting from an independent external drive means the affected drive is completely inactive.

First, thank you for your response.

Well, I finally was able to get around to work on this. Booting from a Sierra Recovery USB stick to launch Disk Utility from USB was only the first step. I tried to use First Aid on the disk and it said it checked out fine. However, I noticed that the Macintosh HD wasn't mounted. So, I mounted it, and ran it again. That's where I ran into trouble. Ended up opening terminal (while still running on the USB stick) and ran 'diskutil repairDisk disk0' and that fixed my problem.

Once again, thank you for your help, it proved to be the first breadcrumb I needed.

 

[Mike Boreham]

First, thank you for your response.

Well, I finally was able to get around to work on this. Booting from a Sierra Recovery USB stick to launch Disk Utility from USB was only the first step. I tried to use First Aid on the disk and it said it checked out fine. However, I noticed that the Macintosh HD wasn't mounted. So, I mounted it, and ran it again. That's where I ran into trouble. Ended up opening terminal (while still running on the USB stick) and ran 'diskutil repairDisk disk0' and that fixed my problem.

Once again, thank you for your help, it proved to be the first breadcrumb I needed.

Glad you got sorted and I contributed a breadcrumb!

As a general comment I think Bootcamp can be the source of other partition problems. The three types of problem I have experienced are:
- not being able to get Bootcamp space back simply with BCA. (This thread)
- on the new 2015 onwards Macs BCA creates a temporary partition for the drivers and installer instead of using a thumb drive. It is supposed to delete this on completion but sometimes doesn't.
- Partition Map corruption leading to inability to boot to the Recovery Partition. I can't say definitely that Bootcamp is related to this except that it has happened to me twice in a period when I was creating and destroying Bootcamp partitions.