Loner T,
My bootcamp does not load after Yosemite install.
Thanks
iMac, OS X Yosemite (10.10), Also Windows 7
did Safe Mode and got the same result.
then did SMC reset based on the se instructions
Resetting the System Management Controller (SMC) on your Mac - Apple Support
it still will not let BCAssistant remove windows and Disk Utility still has Verify and Repair greyed out.
Next steps?
Is this usual?
This is very unusual. Can you look at Resolve startup issues and perform disk maintenance with Disk Utility and fsck - Apple Support and try the fsck method?
The fsck method said everything was ok
i've realised now that i cannot be sure that anything happened with the SMC Reset but have done it again to try and be sure.
i get a slightly different error message from BCAssistant now (below) but am still unable to remove the greyed out Bootcamp.
Will wiping the entire hard drive help?
Can you check Applications -> Utilities -> Console logs for any error messages? In the top right corner, type boot in the search box. You will get additional messages. Please remove any personal information before posting screen shots/logs.
Can you run the following highlighted command from a Terminal and post the output? Here is an example.
diskutil verifyDisk disk0
Started partition map verification on disk0
Checking prerequisites
Checking the partition list
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
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 Recovery HD appears to be OK
File system check exit code is 0
Checking Core Storage Physical Volume partitions
Verifying storage system
Checking volume
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 57578357-3715-48A5-AB8A-4107AF12F7FB on 1 device
disk0s2: Scan for Metadata Volume
Logical Volume Group has a 24 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
Incorporate 0 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 11EBF920-AA4B-4EC6-AC7F-7CC70E69883C
Load and verify 8A0116D5-7E1E-44D8-B2A0-8D4E4D48298D
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 57578357-3715-48A5-AB8A-4107AF12F7FB appears to be OK
Storage system check exit code is 0
The partition map appears to be OK
Finished partition map verification on disk0
Console, 'boot' results looked like this:
Terminal:
Started partition map verification on disk0
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk0s3
Verifying 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
The volume Recovery HD appears to be OK
File system check exit code is 0
Checking Core Storage Physical Volume partitions
The partition map appears to be OK
Finished partition map verification on disk0
That's all. It was a shorter result than the one posted. Problem?
Can you run repairDisk instead of verifyDisk and post the output? I have seen the RepairDisk and SMC reset done twice work much better.
Can you post the output of
sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 977105059
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 878906248 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
879315888 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
880585424 1328
880586752 96518137 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
977104889 138
977105027 32 Sec GPT table
977105059 1 Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 878906248] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 879315888 - 1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 880586752 - 96518137] HPFS/QNX/AUX
Is this your old BC partition? The numbers look like they are. Based on your past comments, I assume you want to remove this partition and start over.
as trying to recover/reinstate the BC installation appears to have failed, yes, i think starting again is the next option. However, as you have seen using BCAssistant to remove the Windows partition does not seem to work either.
What should be my next step?
In a standard Bootcamp configuration, Recovery HD is sandwiched between OS X and Windows partition. BC Assistant relocates the Recovery HD and adds the disk space back to OS X. If any other utility is used to manipulate the BC disk space, it cannot be merged back into OS X, without losing Recovery HD in this non-BCA process.
If you want to pursue the manual method, Recovery HD can be recreated, by re-installing OS X.
so reinstalling OSX seems to the only way past this impass as BCA is not able to fix it.
If i use Time Capsule to bring back all my files and mac software, will it also bring the problem partition back too?
TM/TC do not back up Windows/NTFS. Take a backup of current OS X installation. My recommendation would be to back up the current OS X installation to a different directly attached external disk via USB/Firewire/Thunderbolt, which will keep your original TM/TC intact and you will have two distinct backups. It also avoids partition pollution. TM supports multiple destinations.
Once you have the complete backup, use Internet Recovery, erase your internal disk, and restore from this new backup. Verify that OS X works properly. At this point you ready to try a new BCA partition/Windows installation.
Bootcamp Wont Load After Yosemite Install
