I've been running the Windows 10 public beta through BootCamp almost since it was announced, and now that we have proper support, I was going to upgrade to the full version. I removed the partition with Boot Camp Assistant, and on attempting to make a new one, was told that there was not enough space. I had just cleared up 72 GB, or so I thought, so this came as a surprise. Come to find out, that drive space no longer exists. "About This Mac" doesn't see it, nor does my Disk Utility. I was on the phone today with Apple Support, but all they could tell me was to come here, so I have. There is no "Repair Drive" button or similar function in Disk Utility that I can find, nor can Boot Camp proceed without solving the issue. Any ideas from those of you that know what you're doing?
El Capitan PB 4 lost my Windows partition
Hi,
Type diskutil list into a Teminal window and post the output.
Max.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 178.1 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
Okay, well you don't have a hidden or unmountable partition. It looks like the 72 GB was released as free space. If you go back to Disk Utility and select your internal drive (first selectable item in left column), then go to the Partitions tab, you should be able to expand your OS X partition back out to ~250GB. Let me know if this is not possible. Assuming for now that it is, you can do that and click "Apply". You should now be back to where you were before you installed the Win 10 beta in the first place.
It isn't. It's got the following information, in case it helps:
Device Information
Device: APPLE SSD SD0256F Media
Scheme: GUID Partition Map
Partition Information
Partition [Macintosh HD]
Format [OS X Extended (Journaled)]
Size [178.89] GB
Trying to increase the size of the partition just resets it to that number when I click off of the box.
Okay, from Terminal copy-paste and try:
sudo diskutil repairDisk disk0
then try the resizing through Disk Utility again.
The above command will present a warning before proceeding - You don't need to worry though, the only partition it may decide it need to wipe and repair will be the EFI partition - the command won't affect your user data.
Here's the output from that command:
Repairing the partition map might erase disk0s1, proceed? (y/N) y
Started partition map repair on disk0
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk0s3
Repairing file system
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Trimming unused blocks
The volume Recovery HD appears to be OK
File system check exit code is 0
Updating boot support partitions for the volume as required
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Updating Windows boot.ini files as required
The partition map appears to be OK
Finished partition map repair on disk0
It didn't affect what I can do in Disk Utility, About This Mac, or Boot Camp Assistant. I'm a little confused about the Windows boot.ini files mentioned towards the end though. Sorry, I'm not that tech savvy, just enough to get myself into messes like this.
Okay, well it looks like you're in the same situation you'd have been in if you just tried to erase the Windows 10 partition without using Bootcamp Assistant - did you get the
Bootcamp has been removed and your disk has been restored to a single volume
message after you removed it?
If you don't have a OS X or an installer on an external drive, you'll have to boot to Internet Recovery (hold Cmd+Opt+R during startup), so that the disk will not be in use. Then go to Utilities > Terminal and enter the following:
gpt show /dev/disk0I don't remember seeing the message you quoted, but that's not a guarantee that it wasn't there. I didn't anticipate problems, so I didn't pay as much attention to the dialog box(es) as I should have. About to boot into Internet Recovery.
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 347930544 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
348340184 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
349609720 140624999
490234719 32 Sec GPT table
490234751 1 Sec GPT header
You see the empty line with size 140624999 - that's where your space is. You can further confirm this by multiplying it by 512 and dividing it by 1,000,000 to convert it to GB - in this case 72GB.
You're going to have to return that space to being a Windows partition (at least temporarily) to get it back. Type the following command into the Terminal window you have open:
- gpt add -b 349609720 -t windows /dev/disk0
- where 349609720 is the start position of the unassigned space (1st column, 3rd from the bottom)
- you should see an output like /dev/disk0s4 added. If so you can reboot normally. If it returns an error then continue:
- mount
you should see an output similar to this:
/dev/disk2 on /Volumes (hfs, local, union, nobrowse)
/dev/disk3 on /private/var/tmp (hfs, local, union, nobrowse)
/dev/disk4 on /private/var/run (hfs, local, union, nobrowse)
/dev/disk5 on /System/Installation (hfs, local, union, nobrowse)
/dev/disk6 on /private/var/db (hfs, local, union, nobrowse)
/dev/disk7 on /private/var/folders (hfs, local, union, nobrowse)
/dev/disk8 on /private/var/root/Library (hfs, local, union, nobrowse)
/dev/disk9 on /Library/ColorSync/Profiles/Displays (hfs, local, union, nobrowse)
/dev/disk10 on /Library/Preferences (hfs, local, union, nobrowse)
/dev/disk11 on /Library/Preferences/SystemConfiguration (hfs, local, union, nobrowse)
/dev/disk12 on /Library/Keychains (hfs, local, union, nobrowse)
/dev/disk0s2 on /Volumes/Macintosh HD (hfs, local, journaled)
- umount /dev/disk0s2
where /dev/disk0s2 is taken from the line of the output above that I put in bold because it is the location of the main Macintosh HD (hfs, local, journaled) drive
- gpt add -b 349609720 -t windows /dev/disk0
this is simply a repeat of the first command in this post, but it should work now. Assuming it does, reboot normally.
Yes, that's certainly your best option.
It may be that the Bootcamp Assistant is buggy in PB4. As I see it you can either try to use the same partition for the new install of Windows 10 or try your luck at simply deleting the partition when you get back to OS X and then see if you can expand your El Capitan partition back out to fill the space - normally the latter wouldn't be advisable, but the worst that could happen is that you'd have to do the internet recovery process again.
I'm going to aggregate some of my replies to you so that anyone else following the procedure can follow it more easily.
If you go back to Disk Utility and select your internal drive (first selectable item in left column), then go to the Partitions tab, you should be able to select the Untitled partion and delete ( - ) it then drag your OS X partition back out to ~250GB. Let me know if this is not possible. Assuming for now that it is, do that and click "Apply".
Using the new Disk Utility GUI:
- Click on the wedge of the partition pie-chart that you're happy to return to free space and click on the - (minus) icon underneath the pie chart.
- Click on the wedge representing the 2nd partition that you want to expand into the newly created free space.
- Click and drag the small white circle (at the corner of this 2nd partition-wedge) to the size.
- Click Apply.
Disk Utility -> APPLE SSD SD0256F Media -> Partition -> Select 2nd partition -> Minus sign -> Apply
- Operation Failed
- Details
- Running operation 1 of 1...
- Merging partitions
- MediaKit reports not enough space on device for requested operation
- Operation failed...
Done. 2nd partition is now grayed out in left sidebar. Attempt again:
The volume "Basic data partition" is not journaled. As a result it can not be resized. To enable journaling, cancel partitioning and use the "Enable Journaling" command under the "File" menu.
Okay. Two options: Attempt to remove anyway, or return and Enable Journaling. The first gives me the same "MediaKit" report as above, the second elicits no results: Nothing changes, and the Enable Journaling button remains in the menu. So I either erase the 2nd partition, producing an identical one; erase the 2nd partition to format it differently (not helpful, apparently); or I mount it, which still changes nothing.
So I can't get rid of it. Nor can I apparently install Windows on the partition I have at the end of all that, because "The selected disk is of the GPT partition style." If you can help me solve either of these problems, I'd be grateful -- more than I already am for the time you've put in.