I can't delete the section Free

Can you post the output of the following Terminal commands?

diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

For "sudo" commands, enter your password when prompted, and it will not be echoed back to you. "sudo' will also warn about improper use and data loss. As long as you use the commands as they are, it should not cause any problems.

1. What was the issue with Bootcamp?

2. Using Disk Utility and Bootcamp Assistant causes problems.

3. Your Free Space is after the Recovery HD, because BCA moves Recovery HD to be before the Windows partition.

4. Are you planning to use EFI boot or BCA tot install Windows?

5. What year/model is your Mac?

There is an option, but you will lose Recovery HD. Do you have a Time Machine backup of your OSX installation?

In your diskutil list output you have disk0s3, which is the Recovery HD. If it is converted to Free Space, then you have contiguous Free Space after your CS volume.

First you should try and run BC Assistant and if you see a "Remove..." option use it. If that does not work, then diskutil commands will need to be used to reclaim the disk space.

Your diskutil cs list output is not complete. Can you post it again?

You should also back up OSX using Time Machine. You can use an external disk of about 384GB or more.

The following command can merge disk partitions, but Free Space has no assigned disk0sN. The other challenge you have is that you have a CoreStorage

volume, so mergePartitions by itself does not help.

diskutil mergePartitions

Usage: diskutil mergePartitions [force] format name

DiskIdentifier|DeviceNode DiskIdentifier|DeviceNode

Merge two or more pre-existing partitions into one. The first disk parameter

is the starting partition; the second disk parameter is the ending partition;

this given range of two or more partitions will be merged into one.

All partitions in the range, except for the first one, must be unmountable.

All data on merged partitions other than the first will be lost; data on the

first partition will be lost as well if the "force" argument is given.

If "force" is not given, and the first partition has a resizable file system

(e.g. JHFS+), it will be grown in a data-preserving manner, even if a different

file system is specified (in fact, your file system and volume name parameters

are both ignored in this case). If "force" is not given, and the first

partition is not resizable, you will be prompted if you want to erase.

If "force" is given, the first partition is always formatted. You should

do this if you wish to reformat to a new file system type.

Merged partitions are required to be ordered sequentially on disk.

See diskutil list for the actual on-disk ordering; BSD slice identifiers

may in certain circumstances not always be in numerical order but the

top-to-bottom order given by diskutil list is always the on-disk order.

Ownership of the affected disk is required.

Example: diskutil mergePartitions JHFS+ NewName disk3s4 disk3s7

This example will merge all partitions *BETWEEN* disk3s4 and disk3s7,

preserving data on disk3s4 but destroying data on disk3s5, disk3s6,

disk3s7 and any invisible free space partitions between those disks;

disk3s4 will be grown to cover the full space if possible.

You cannot merge Free Space into a Core Storage volume, even if you delete Recovery HD.

1. You need to delete Recovery HD using the following command. The file system should be free. This will merge disk0s3 and the following Free Space into a single Free Space.

diskutil eraseVolume

Usage: diskutil eraseVolume format name MountPoint|DiskIdentifier|DeviceNode

Completely erase a disk (partition or whole), laying down a new file system

volume. Ownership of the affected disk is required. Format is the specific

file system personality name (or alias) you want to erase it as (JHFS+, etc.).

Name is the (new) volume name (subject to file system naming restrictions), or

can be specified as %noformat% to skip initialization (to skip newfs). You

cannot erase the boot volume.

Example: diskutil eraseVolume JHFS+ UntitledHFS /Volumes/SomeDisk

diskutil listfilesystems

Formattable file systems

These file system personalities can be used for erasing and partitioning.

When specifying a personality as a parameter to a verb, case is not considered.

Certain common aliases (also case-insensitive) are listed below as well.

-------------------------------------------------------------------------------

PERSONALITY USER VISIBLE NAME

-------------------------------------------------------------------------------

ExFAT ExFAT

Free Space Free Space

(or) free

MS-DOS MS-DOS (FAT)

MS-DOS FAT12 MS-DOS (FAT12)

MS-DOS FAT16 MS-DOS (FAT16)

MS-DOS FAT32 MS-DOS (FAT32)

(or) fat32

HFS+ Mac OS Extended

Case-sensitive HFS+ Mac OS Extended (Case-sensitive)

(or) hfsx

Case-sensitive Journaled HFS+ Mac OS Extended (Case-sensitive, Journaled)

(or) jhfsx

Journaled HFS+ Mac OS Extended (Journaled)

(or) jhfs+

2. Once you have contiguous free space after the Core Storage volume (disk0s2), you will need to use the following command to extend the CS volume to the entire disk.

diskutil cs resizeStack

Usage: diskutil coreStorage resizeStack

lvUUID|MountPoint|DiskIdentifier|DeviceNode [pvUUID] size

[part1Format part1Name part1Size part2Format part2Name part2Size

part3Format part3Name part3Size ...]

Resize both a logical volume and one of its underlying physical volumes in a

single operation. A single physical volume is always chosen for the underlying

shrink or grow, even if the logical volume's logical volume group is backed by

more than one physical volume. If you do not specify a particular physical

volume, then one is chosen for you. Note that if this is a grow operation,

this verb is limited by the physical volume's partition's room to grow.

Specifying zero as the size asks for an "automatic" grow-to-fill operation.

If this is a shrink operation, you can optionally request that new partitions

be created in the newly-formed free space gap in the partition map.

Again, note that this only resizes one of the underlying physical volumes; if

you need more sophistication in managing your topology, you should use the

separate physical and logical volume resize verbs.

Example: diskutil coreStorage resizeStack

11111111-2222-3333-4444-555555555555 10g JHFS+ New 1g

The command will look like (the UUID used is Logical Volume from you diskutil cs list output).

diskutil cs resizeStack 20DDAD5D-128B-4962-B483-CCB192119A33 250g

3. You can the reinstall OS X (without modifying any of your non-OS files) and get Recovery HD back.