Created partition after bootcamp windows install - 'No Disk'

You expect people to follow your links around to find out rather than just posting the information yourself.?

Goodbye.

The main problem is the MBR 4th partition type code is 0C, it should be 07, and it's not marked active (boot flag is not set). A secondary problem is that you have a 154GB pile of free space between partitions 3 and 4, and it may be tricky getting that absorbed by one or the other file system.

First, you should make a backup of important things on the OS X volume for starters, so that you at least have that should one of make a mistake with my subsequent recommendations.

Next, download and install gdisk.This is a command line only utility so you'll be using it in Terminal once installed. It's interactive, and doesn't write anything to disk until you explicitly tell it to, so it's quite safe.

Each line is a command, followed by return, you can use ? to see a menu and find that the first command "r" is to get to the recovery menu. Once you're there, you can use ? again to see that menu of options and find h is to make a new hybrid MBR. And the program is quite well documented so you can see this is quite transparent and straight forward. If the line is <enter> that means enter no information just hit the return key to accept the program's default value.

sudo gdisk /dev/disk0

r

h

2 3 4

y

<enter>

n

<enter>

n

<enter>

y

o

p

Now copy-paste the output from the o and p commands into the forum for proof reading if you want. If you don't care for it to be proofed you can issue the w command to write out the changes to disk. And reboot. Now see if Windows is bootable again.

Basically all of that is to create a new hybrid MBR, adding the GPT and EFI System partition into MBR partition 1; and then 1:1 correlation GPT to MBR for partitions 2 3 4, with only 4 marked as bootable, accepting the default partition type codes (gdisk gets the defaults from the GPT partition type code which are all correct). So this should fix the first problem.

Once that's fixed we'll discuss what to do with this 154GB of free space as there are some tricky options there.

That looks right so just write that out with the w command (followed by y) and then reboot and test it out. This needs to be fixed regardless so you can backup anything important on the Windows volume before moving on to dealing with the free space.

The most commonly recommended product in these forums for doing this is Paragon Camptune. It understands the unique, non-standard partition scheme that Apple is using. It will correctly resize JHFS+ and NTFS volumes, and then updates the GPT and MBR partition maps. That's the easiest and fastest way to do it.

If you want to use free tools, the basic recipe is:

1. Use gdisk to create a new protective MBR. This removes the hybrid MBR you previously made, and makes the disk strictly GPT. I suggest this to avoid any confusion which partition table is to be updated in subsequent steps, and the hybrid MBR will be recreated later based on the updated GPT.

2. Gparted is a linux program that can do the move/resize of an NTFS volume. It needs to be moved forward first, since resizing happens at the end of NTFS (and JHFS+) volumes. This will take a while and it's important that the process isn't interrupted. There are two ways to get access to Gparted, the easiest is download Gparted Live and burn it to a CD/DVD and boot the Mac with the c key, then go find Gparted and run it. There are lots of guides on the internet how to do the move/resize.

If you need to boot off a USB flash drive, then you also (ideally) need a wired internet connection as well. Download Fedora 19 (Desktop, 64-bit) and use the OS X dd command to write it to a USB stick, boot from the USB stick, then in the Terminal program type:

su

yum install gparted

It isn't installed to the hard drive, it's only in memory, so if you were to reboot from this USB stick, Gparted will be gone.

3. Reboot to OS X, rerun gdisk, and execute the earlier commands I gave to recreate the hybrid MBR.

4. Reboot to Windows. The NTFS volume will be flagged by Gparted (actually ntfs-3g tools) as needing to be repaired by chkdsk the next time Windows boots, so seeing that repair will be normal.

I haven't used it so I'd give them a call and see what they have to say. I'd like to think that it would consider either JHFS+ or free space as a possible source to add to an existing NTFS volume, but I could be wrong. Maybe it only expects to shrink JHFS+ and then expand NTFS or vice versa, rather than growing NTFS from free space.

What do you get for:

diskutil resizevolume /dev/disk0 limit

oh yeah right. specify the right partition also, something like disk0s2 usually. you can use diskutil list to find it.

try it with limits, with an s.