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.

No access to Bootcamp after Mavericks upgrade

Hi Loner T,


Thank you for your help. Here are the answers to your questions:


What was the sequence of upgrade? 10.9.3. followed by Parallels or the other way?


I upgraded to 10.9.3 first.


Where in this sequence did the Bootcamp disappear?


After I upgraded, I tried to connect to the Bootcamp partition via Parallels 5. Wasn't able to connect at all. I then upgraded to Parallels 9, was able to connect, but went right to the blue screen.


What OSX version did you upgrade from to 10.9.3?


I believe it was 10.6.


It is good to see that Bootcamp NTFS is intact and mountable?


Yes, seems to be mountable as I can switch between mount and unmount for Bootcamp.


Can you see files in Bootcamp in Finder? If you have XP installed then it is supported, but new installation of XP is not supported.


Yes, I can see files in the Bootcamp Finder.


Can you post the output of the following two commands?


sudo gpt -r -v show /dev/disk0

gpt show: /dev/disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: /dev/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 814524592 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

814934232 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

816203776 160569344 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

Users-iMac:~ user$ sudo gpt -r -v show /dev/disk0

gpt show: /dev/disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: /dev/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 814524592 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

814934232 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

816203776 160569344 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header


sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 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 - 814524592] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 814934232 - 1269544] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 816203776 - 160569344] HPFS/QNX/AUX

Posted on Jul 1, 2014 12:41 PM

Reply
18 replies

Jul 4, 2014 6:12 AM in response to Matt2400

You are doing a disservice to the advice available on the forums. Regrading qualifications, this is a self-help forum, not vendor provided tech support.


If you have the luxury of taking your machine where the repair can be done with ears and eyes of person diagnosing the problem vs diagnosing over a forum and can afford the financial aspects, you are welcome to it.


It was your choice to seek help here, rather than going to this "professional" place at first. I think your misunderstanding of how it is supposed to work vs how you want it to work is where the problem started. There were changes made without knowing what the consequences would be. It is not something this community can prevent.


The community tries to assist, and you are the ears and eyes that the community has to rely on.


You could have also said, it could not be resolved here, so I got it fixed at a professional place. You could have been complimentary to the community which tried to help you. You have chosen a different line of discussion, which is very callous.


Others may not have access to such a professional place because of their location.


Do not burn bridges, if you have not built any.


Do you know what was done to your machine to fix the issue? If you want to, you can document it here which may help others.

No access to Bootcamp after Mavericks upgrade

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