You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

Inaccessible bootcamp partition for startup disk

Here are the results of the commands that Christopher asked for in thread: https://discussions.apple.com/thread/4144252


Matts-iMac:~ mattp$ 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 - 409639] <Unknown ID>

2: AF 1023 254 63 - 1023 254 63 [ 409640 - 1660156288] HFS+

3: AB 1023 254 63 - 1023 254 63 [1660565928 - 1269536] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [1661837312 - 291686400] HPFS/QNX/AUX



Matts-iMac:~ mattp$ sudo gpt -r -v show disk0

gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

gpt show: disk0: Suspicious MBR at sector 0

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 1660156288 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

1661835464 1848

1661837312 291686400 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.4)

Posted on Jul 16, 2013 6:37 PM

Reply
16 replies

Jul 16, 2013 8:39 PM in response to MattP94

Sadly, I have the same on my MacBookPro. Here are the results for that one.


Matts-MacBook-Pro:~ mattp$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 91201/255/63 [1465149168 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 - 1169921920] HFS+

3: AB 1023 254 63 - 1023 254 63 [1170331560 - 1269536] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [1171601408 - 293545984] HPFS/QNX/AUX



Matts-MacBook-Pro:~ mattp$ sudo gpt -r -v show disk0

gpt show: disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168

gpt show: disk0: Suspicious MBR at sector 0

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 1169921920 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

1171601096 312

1171601408 293545984 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1465147392 1743

1465149135 32 Sec GPT table

1465149167 1 Sec GPT header

Jul 16, 2013 9:07 PM in response to Christopher Murphy

Thanks for the speedy reply. In both cases, I can't select the boot camp partition as a startup disk to boot directly to it. I hadn't tried in a while, but I think what must have caused it was the upgrade to Mountain Lion from Lion. In both cases I haven't touched the partitions themselves since setting up boot camp when I first got them.


The only other thing I can think of that's of note is that in both cases there is VM software that can run the bootcamp within OSX. I have the bootcamp OS shut down in the VM, though, and still can't select it in the Startup Disk control panel. One uses VMWare Fusion. The other uses Parallels.


Let me know if there's any other info I might provide. Sorry if that's too vague. I'll understand if there's nothing to be done.


Thanks again.

Matt

Jul 16, 2013 9:20 PM in response to Christopher Murphy

Ok, now I feel silly. Tried that on the iMac, and windows was there. It seems like it's coming up normally. I'd assumed there was a problem since the way I'd always gotten it to boot before seemed to be missing. This works fine, so I guess I don't have to worry about that.


Thanks so much, and sorry for wasting your time!


Just as an aside question, could it be that I need to/can download new drivers related to bootcamp, after having done OS upgrades and such?

Jul 17, 2013 5:44 AM in response to MattP94

I found this which seems related once you get to post 6.

http://forums.macrumors.com/archive/index.php/t-770812.html


I think the Startup Disk panel expects to use Apple's NTFS (readonly) implementation, in order to locate Windows, and then display it as a boot option. If you're using something other than Apple's implementation, it doesn't get listed (?) for whatever reason. Do you have NTFS-3G installed, or something else that eneables read-write to NTFS?

Jul 17, 2013 5:50 AM in response to Christopher Murphy

Hi Chris:


FYI, in my experience any 3rd party NTFS utility (Paragon, Tuxera and especially NTFS-3G) will cause this behavior. NTFS-3G is especially buggy with Mountain Lion, just because it is free is not a good reason to use it. In practice the most stable option is Paragon, but the sensible option (as always) is to put Windows on a PC, not a Mac.

Jul 17, 2013 6:12 AM in response to MattP94

Curious that the implementation matters. If you're going to pay for read-write support, I'd probably go with Paragon. If you want a free solution, I'd make certain you're not using the positively ancient NTFS-3G build from 2009 (or older) that's floating around on the internet. NTFS-3G is regularly updated, but they don't keep OS X binaries handy. You have to build it yourself using XCode and Macports, which is a bit tedious to learn. But using an old build is asking for trouble.


If you've already paid for Tuxera's version, I'd make sure it's up to date, and I'd file a bug with them (as if they don't already know this) that when using their NTFS-3G software, Windows doesn't show up as an option in the Startup Disk panel.

Jul 17, 2013 11:12 AM in response to MattP94

MattP94 wrote:


I looked in their support forum, and found this:

http://goo.gl/gWe8T


It looks like they were saying it's an Apple problem, so there's not much they can do. I'll probably open a ticket with them, just to see, since this was a while ago, but at least I can use the option key, and that's great.


Thanks again for all the help!

You do realize that the date of that post was 2007, 6 years ago. If they have been blaming Apple for the last 6 years I doubt that anything will change in the next 6 years.

Jul 17, 2013 11:54 AM in response to Christopher Murphy

Yeah, realized it was that old, just figure if it's really hard-coded with apple, they're probably not too concerned about changing it. That said, I'll see what Tuxera has to say about it now.


Here's the mount results.


Matts-iMac:~ mattp$ mount

/dev/disk0s2 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

/dev/disk0s4 on /Volumes/BOOTCAMP (fusefs_txantfs, local, synchronous)

Inaccessible bootcamp partition for startup disk

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