Wow thanks for that link, I have added that to my list.
I'm running into another issue when trying to run Bootcamp. It seems the computer is having an issue portioning the hard drive as it stalls during the portioning disk progress bar, and then an error appears:
So, I run the First Aid in Disk Utility and everything checks out fine. I look up the error and find another post of yours that mentions to try and "manually" add the partition using Disk Utility, making sure to use FAT32. I couldn't because of this error:
Not sure what to do at this point. I ran the follow per your post (Bootcamp Cannot Partition Disk):
diskutil repairDisk disk0
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
Verifying file system
Volume is already unmounted
Performing fsck_hfs -fn -x /dev/rdisk0s3
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
The volume Boot OS X appears to be OK
File system check exit code is 0
Restoring the original state found as unmounted
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Verifying storage system
Performing fsck_cs -n -x --lv --uuid 0F34B518-B384-480A-8603-F77D4074DFBF
Checking volume
disk1s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk1s2: Scan for Disk Labels
disk0s2: Scan for Disk Labels
Logical Volume Group 0F34B518-B384-480A-8603-F77D4074DFBF spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 66 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 4 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify E23859DD-F40F-485B-878A-4D0C31084FEB
Load and verify FB7B9C03-3203-43DA-A86A-6D8CF4CB7017
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0F34B518-B384-480A-8603-F77D4074DFBF appears to be OK
Storage system check exit code is 0
Repairing storage system
Performing fsck_cs -y -x --lv --uuid 0F34B518-B384-480A-8603-F77D4074DFBF
The volume disk1s2+disk0s2 cannot be repaired when it is in use
Checking volume
disk1s2: Scan for Volume Headers
disk0s2: Scan for Volume Headers
disk1s2: Scan for Disk Labels
disk0s2: Scan for Disk Labels
Logical Volume Group 0F34B518-B384-480A-8603-F77D4074DFBF spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 66 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 4 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify E23859DD-F40F-485B-878A-4D0C31084FEB
Load and verify FB7B9C03-3203-43DA-A86A-6D8CF4CB7017
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0F34B518-B384-480A-8603-F77D4074DFBF appears to be OK
Storage system check exit code is 0
Incorrect size for volume "Macintosh HD"
Adjusting volume "Macintosh HD"
Growing Logical Volume
Resizing Core Storage Logical Volume structures
Resized Core Storage Logical Volume to 2,114,568,323,072 bytes
Growing file system
The partition map appears to be OK
Finished partition map repair on disk0