Created partition after bootcamp windows install - 'No Disk'

Oh jeez, another long standing annoying bug. So basically it's saying it's not recognizing the free space after the Recovery HD as valid space to re-expand the OS X volume back to the size it was. I thought maybe if it would do that, then you could retry Camptune.

In the past, I've looked at the number of sectors for the recovery hd partition (you can use gdisk or gpt commands to get that info), and then subtract that from the start value for the windows partition, to get the new start value for recovery HD. And then copy Recovery HD using dd, sector copy. Blow away the original. And now the freespace is right next to the OS X volume, and for some reason that satisfies diskutil resizevolume and it'll reabsorb the free space.

But honestly, you've paid for the product, I'd call or email Paragon and explain the present partition layout (you could give then gdisk's current o and p outputs, MBR and GPT respectively), tell them how Camptune is behaving, and the result you get and see if this is supported or not. If not, try to get a refund if you want. I mean, if it doesn't do what you need it to do... be a consumer.

And if that's how it turns out, then you're either back to Gparted, or backing up OS X and Windows, blowing away the disk and starting from scratch with the desired layout.

OR another option, is to go all OS X and use a VM instead of dual-booting. Saves a LOT of brain cells.

I haven't had any issue with bootcamp up until now.

Basically Apple has given users a razor blade, and told them to go play on the freeway. When there's an accident, which in my opinion is inevitable because inevitably a reasonable user will want to reallocate space from one or the other environment, Apple provides no obvious way to do this except through Disk Utility. And Disk Utility, without warning, simultaneously makes Windows unbootable and also creates free space that can't then be reabsorbed back to OS X.

Anyway, you should still talk to Paragon so at least you can report back if they have a work around, because if they don't I'm not going to recommend it for this problem again.

I can't answer your question, all I can tell you is I've filed two bugs: one for documentation to be more clear about what proscriptions there are related to Boot Camping a drive, and for Disk Utility to warn or disallow changes (short of blowing away the whole disk which it should still allow).

As for the 2-5GB that you can't use, it really isn't that difficult to move the Recovery HD partition to the end of that 2-5GB of free space, thereby making 2-5GB right after the OS X JHFS+ partition. Then diskutil resizevolume should allow the volume to be expanded into this free space. It also doesn't hurt to just leave it be. If you get to a situation where you need those 2-5GB, you're probably ready for a bigger drive anyway.

NTFS is a perfectly valid partition? so there is no reason to, and it does not look to see what is inside the partition.

I think at one time if you tried to use DU to repair NTFS you might get an alert, but people do use NTFS and have data partitions along with Paragon NTFS (which really seems to be the only or most reliable for 10.7.x and above).

Do we really want to lock down, dumb-down and make the OS into a restricted and somewhat crippled?

I think HFSX is constantly changing and evolving which does continue into 10.9.

NTFS is a perfectly valid partition? so there is no reason to, and it does not look to see what is inside the partition.

I don't understand the question or the comment. Any tool that creates a hybrid MBR needs to look at the partition type GUID and the file system header in order to set the MBR type code correctly because there isn't a 1:1 correlation. The same GPT GUID partition type code is used for FAT32 and NTFS, whereas for MBR they are different type codes. Apple is simply doing this incorrectly, among many other things in Disk Utility.

Do we really want to lock down, dumb-down and make the OS into a restricted and somewhat crippled?

Versus data loss? Yes. Apple's own technote about disks with hybrid MBRssays that utilities shouldn't modify them. Yet Disk Utility does modifiy such a disk, and data loss ensues, and can't be reversed with Disk Utility.

I think HFSX is constantly changing and evolving which does continue into 10.9.

Well, Apple isn't using HFSX by default, you have to ask for it. Currently it's only used for case-sensitive file system, although there is a flag that can be set to make it case-insensitive and still be HFSX. But for now Apple uses JHFS+ for case-insensitive and HFSX for case-sensitive. And due to various reasons HFSX breaks certain applications, top on my list is Photoshop.

When I say "isn't difficult" I mean doing this via CLI. There isn't a GUI way to do this. So I'd have to publish the steps if turns out you want to do this. But I'm not going to the trouble until then.