Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Bootcamp/Yosemite Boot Issues

I have a setup where I have Windows 8.1 installed through bootcamp on a separate partition. I haven't booted into bootcamp natively for a while and have updated to Yosemite in the meantime. Now quite often when I try and boot into bootcamp it loads windows and I see the windows desktop for a few seconds and then it reboots automatically back into OS X. I have also had this behaviour when booting into OS X Utilities too.


I've tried everything from scanning partitions for errors in disk utility to deleting the bootcamp partition, recreating it and restoring a winclone image and also reinstalling windows afresh, yet the issue is still there. I can get into windows eventually after two or three attempts however.


I'm inclined to think it may be a Yosemite issue as I've tried most other things that I can think of with the exception of going back to Mavericks. Just wondered if anyone might have any ideas. Thanks in advance.

MacBook Pro with Retina display, OS X Yosemite (10.10.1)

Posted on Dec 25, 2014 9:32 AM

Reply
45 replies

Dec 25, 2014 12:46 PM in response to Loner T

Thanks for your reply Loner T.


I have tried resetting NVRAM to no effect.


The bootcamp partition is on the same physical drive as the Macintosh HD. Interestingly, I have had Paragon for NTFS installed for a long while but have just uninstalled it and tried Tuxera NTFS instead. The issue still remains. Do I actually need third party NTFS software?


I haven't tried resetting the SMC. On an October 2013 macbook pro does that involve taking the battery out?

Dec 25, 2014 8:17 PM in response to adyf88

1. I suggest removing third-party NTFS drivers temporarily. You need them if you need read-write access, but Apple native NTFS by default provides read-only access.

2. Please post the output of following Terminal commands. You will need to enter you password for the sudo commands to return meaningful output.

diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

3. Your issue looks like a timer issue between two separate NTFS drivers.

Dec 25, 2014 8:20 PM in response to GoldSpell

GoldSpell wrote:


I have a problem. I need GPT for Windows 8. I have formatted my USB Flash Drive in GUID-Partition..., but when I install the .iso on Boot Camp-Assistent the partition table switch to Master Boot Record. Do you have solution for that?

The GPT on the USB is not related to the disk partitioning of teh Windows destination partition/disk. BCA always created a MBR USB which is used by Windows installer. The eventual file system for Windows is NTFS, but BCA leaves it as FAT, which the Windows installer re-formats to NTFS.


Please see - https://help.apple.com/bootcamp/mac/5.0/help/.

Dec 26, 2014 4:41 AM in response to Loner T

Hi Loner T, thanks for persevering. I uninstalled Tuxera NTFS and ran the requested commands in terminal.


The following information doesn't mean too much to me but I did notice that the command 'diskutil cs list' returned 'No CoreStorage logical volume groups found'. I don't know if this is significant or not.

Last login: Fri Dec 26 12:34:04 on ttys000

MacBook-Pro:~ AdrianLAPTOP$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 397.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 102.4 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS G-DRIVE mobile with ... 499.9 GB disk1s2

3: Apple_HFS SuperDuper - G-DRIVE... 499.8 GB disk1s3

MacBook-Pro:~ AdrianLAPTOP$ diskutil cs list

No CoreStorage logical volume groups found

MacBook-Pro:~ AdrianLAPTOP$ sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

gpt show: /dev/disk0: PMBR 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 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 775390656 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

775800296 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

777069832 760

777070592 200034304 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

977104896 131

977105027 32 Sec GPT table

977105059 1 Sec GPT header

MacBook-Pro:~ AdrianLAPTOP$ 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 - 977105059] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

MacBook-Pro:~ AdrianLAPTOP$

Dec 26, 2014 10:01 AM in response to adyf88

If your Windows installation was done using Bootcamp Assistant and the partitioning was also done by BCA, then you should have a Hybrid MBR, but your fdisk output does not show one.


You will need GPT Fdisk (aka gdisk - http://sourceforge.net/projects/gptfdisk/) to recreate the Hybrid MBR using the following steps.


Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes).

Sudo gdisk /dev/disk0

P (Print list of parts)

R (Recover)

H (chooses Hybrid)

Partitions numbers to be hybridized: 2 3 4

Y (Good for GRUB question)

N (part 2 boot flag)

N (part 3 boot flag)

Y (part 4 boot flag make NTFS bootable partition)

W (Write the new MBR)

Y (Yes! write the new MBR)

Reboot


Test 1 - Does Bootcamp Volume show up in Finder?

Test 2 - Can you see files in Bootcamp Volume?

Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?

Test 4 - If Test 3 is successful, select Bootcamp and Click Restart


If you see a hanging underline cursor at the top left on a black screen, and it does not proceed further, you may need Windows Startup Repair or a tool called EasyBCD.

Dec 27, 2014 5:20 AM in response to Loner T

Hi Loner T,


I followed your instructions and all four tests were successful. I also get the hanging cursor at the top left on a black screen, it doesn't hang for long though as it soon boots back into OS X which was my original problem.


I cannot get into windows at all now directly, the windows installation CD won't perform the startup repair and throws an error. I can however boot into windows through Parallels and I did install EasyBCD. I'm not 100% sure what to do with this software but I did use the re-create/repair boot files which it said completed successfully but this made no difference.


I do however have a second windows disk (hard disk icon) option on boot up. Selecting one of them takes you to the hanging cursor, selecting the other one takes you to a light blue screen that says your PC needs to be repaired and offers F1 to F9 options, I tried safe mode which didn't work. How do I get rid of this and do you have any ideas on what I should do next please?


PS I haven't reinstalled any third party NTFS software at this point.

Dec 27, 2014 6:41 AM in response to adyf88

Today I find out, that I have also a problem with Yosemite & Bootcamp.


If I try too boot Windows, it will hang.

If I try to delete Windows 7 partition it don't work

Repairing Bootcamp partition I get some entries:

Volume „BootCamp“ überprüfen und reparierenDateisystem reparieren.ntfsck 3011.12.9-mac

Checking NTFS Superblock ...

Device name : /dev/disk0s4

NTFS volume version: 3.1

Cluster size : 4096 bytes

Current volume size: 31998341632 bytes (31999 MB)

Current device size: 31998345216 bytes (31999 MB)

Checking for bad sectors ...

Scanning $MFT ...

Actual VCN (0x0) of index buffer is different from expected VCN (0xe) in inode 0xa02.

Checking directory structure ...

Corrupt directory found, inode=2562 (0xa02)

Repairing corrupt directories started.

0.00 percent completed

...

100.00 percent completed

File name from INDEX_ALLOCATION "HPZSSwn7.DLL", and MFT "HPZSSWN7.DLL" are not same.

Repairing corrupt directories completed.

Corrupt directory found, inode=9344 (0x2480)

Repairing corrupt directories started.

0.00 percent completed

...

100.00 percent completed

Repairing corrupt directories completed.

Checking for orphaned files ...

0.00 percent completed

...

100.00 percent completed

Scanning orphaned files completed.

Checking cluster allocation ...

0.00 percent completed

...

100.00 percent completed

Checking cluster allocation bitmap ...

Checking $MFT bitmap ...

0.00 percent completed

...

100.00 percent completed

Fixing $MFT bitmap

Fixed $MFT bitmap

Space in use : 14794 MB (46.2%)

Done NTFS checking and repair on device '/dev/disk0s4'.

Syncing device ...

Exit-Code für Dateisystemprüfung lautet 0.Boot-Support-Partitionen nach Bedarf für das Volume aktualisieren.


So what can I do?

Dec 27, 2014 7:57 AM in response to adyf88

Just an update. I deleted my Bootcamp partition, recreated it and restored my winclone image. I then thought I would follow the gdisk instructions again. What does the following mean from below 'GPT partition #4 does not exist or is too big; skipping.'? This didn't happen the first time.


Last login: Sat Dec 27 15:48:33 on ttys000

MacBook-Pro:~ AdrianLAPTOP$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 1953525167] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

MacBook-Pro:~ AdrianLAPTOP$ Sudo gdisk /dev/disk0

GPT fdisk (gdisk) version 0.8.10


Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present


Found valid GPT with protective MBR; using GPT.


Command (? for help): P

Disk /dev/disk0: 1953525168 sectors, 931.5 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 00FAF90D-333B-4C35-9EB7-D090E862249A

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1953525134

Partitions will be aligned on 8-sector boundaries

Total free space is 524301 sectors (256.0 MiB)


Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 976836311 465.6 GiB AF00 G-DRIVE mobile with...

3 977098456 1953262983 465.5 GiB AF00 SuperDuper - G-DRIV...


Command (? for help): R


Recovery/transformation command (? for help): H


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 2 3 4

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y


Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF): AF

Set the bootable flag? (Y/N): N


Creating entry for GPT partition #3 (MBR partition #3)

Enter an MBR hex code (default AF): AF

Set the bootable flag? (Y/N): N


GPT partition #4 does not exist or is too big; skipping.


Unused partition space(s) found. Use one to protect more partitions? (Y/N):

Dec 27, 2014 9:41 PM in response to adyf88

adyf88 wrote:


Just an update. I deleted my Bootcamp partition, recreated it and restored my winclone image. I then thought I would follow the gdisk instructions again. What does the following mean from below 'GPT partition #4 does not exist or is too big; skipping.'? This didn't happen the first time.

Your command output shows disk0 as

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 397.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 102.4 GB disk0s4

but when you run gdisk /dev/disk0, disk0 seems to be

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS G-DRIVE mobile with ... 499.9 GB disk1s2

3: Apple_HFS SuperDuper - G-DRIVE... 499.8 GB disk1s3

This can happen if OSX, after a reboot, renumbers drives. You should not create a Hybrid MBR on disk1. You need to pick diskN, where N contains the Bootcamp volume, and verify that you are picking the correct drive.


If you are using Winclone to restore, unless you tell it to use Legacy EFI, it should recreate the MBR as well. Your G-drive does not need it, so check on teh diskN which corresponds to the Bootcamp partition as diskNs4.

Dec 28, 2014 2:54 AM in response to Loner T

I'm not too sure what you are asking me to do. Are you saying that I should use gdisk again to create a Hybrid MBR on the corresponding bootcamp GPT partition which may no longer be #4? How do I find out what the correct drive is?


When I used gdisk yesterday as you predicted I got the flashing cursor on a black screen but then couldn't get windows to repair itself with the installation disk under any circumstances. That's why I restored my winclone image.


Another thing I have noticed which may add value. I can reliably boot directly into windows using System Preferences -> Startup Disk -> Select Bootcamp -> Restart. The problem seems to be when I hold down the option key on boot up and then select the windows drive, that's when sometimes it boots and sometimes it doesn't. Therefore what is the difference in booting from Startup Disk when in OS X and booting the other way from the options presented after booting and holding down the options key?

Bootcamp/Yosemite Boot Issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.