Resolved Boot Camp unmountable after Mavericks update

RyanSSealey

macrumors newbie
Original poster
Mar 16, 2014
5
0
After running the Mavericks OS X update, my Boot Camp (Windows 7 64-bit) partition is inaccessible. I don't normally keep data files on that partition, but I happen to have some there currently that are not backed up.

Opening Disk Utility shows "BOOTCAMP" under my hard drive, but it will not mount. I have been trying to find a solution for this, but it seems the situation can vary so I would really appreciate some assistance.

These outputs were requested in other resolutions, so I went ahead and ran each. Please let me know if the commands need to be changed for my situation.

sudo fdisk /dev/rdisk0
Code:
Disk: /dev/rdisk0	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 - 1466796928] HFS+        
 3: AB 1023 254  63 - 1023 254  63 [1467206568 -    1269536] Darwin Boot 
*4: 07 1023 254  63 - 1023 254  63 [1468477440 -  485046272] HPFS/QNX/AUX
sudo gpt -r -vv show /dev/rdisk0
Code:
gpt show: /dev/rdisk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/rdisk0: Suspicious MBR at sector 0
gpt show: /dev/rdisk0: Pri GPT at sector 1
gpt show: /dev/rdisk0: Sec GPT at sector 1953525167
       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  1466796928      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  1467206568     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  1468476104        1336         
  1468477440   485046272      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  1953523712        1423         
  1953525135          32         Sec GPT table
  1953525167           1         Sec GPT header
 
Last edited:

Quackers

macrumors 6502a
Sep 18, 2013
645
1
Manchester, UK
Everything looks ok to me.
Try booting from the Windows install dvd/usb and running the automatic repair process. Once may be enough but it can need to be run up to 3 times, depending on what's wrong.
That would be my first course of action.
 

RyanSSealey

macrumors newbie
Original poster
Mar 16, 2014
5
0
That fixed it! Thank you so much!

Edit: Darn. Well I'm able to get to my files, and that was the most important thing.
I can now boot into Boot Camp, but I still can't mount it from within OS X.
 
Last edited:

RyanSSealey

macrumors newbie
Original poster
Mar 16, 2014
5
0
Ran the chkdsk with /f and watched it go through the process, but I still can't mount it in OS X.
 

Quackers

macrumors 6502a
Sep 18, 2013
645
1
Manchester, UK
Did the chkdsk find/fix any errors? If so it should be run again until none are found.

Try opening Disk Utility and see if the Bootcamp partition shows up in that.
Don't do anything else in Disk Utility.
If it mounts ok in D.U. open a Finder window and see if Bootcamp shows up there too.
 

RyanSSealey

macrumors newbie
Original poster
Mar 16, 2014
5
0
Running Disk Utility shows "BOOTCAMP" under the disk. When I select it and click "Mount", this displays:
"Mount failed
The disk "BOOTCAMP" could not be mounted.
Try running First Aid on the disk and then retry mounting."

It does not show up in Finder.

I didn't notice that it found any errors, though there were a couple of things I didn't understand listed while it ran. It automatically booted Windows when it finished, so I couldn't get a good look at it then.
 

Quackers

macrumors 6502a
Sep 18, 2013
645
1
Manchester, UK
Thanks. Other than running a second (or third) chkdsk I can't really think of anything else. My supposition is that OSX thinks the NTFS file system is unclean. Maybe there's something I've not thought of :confused:
You don't have NTFS-3G installed do you?
 

RyanSSealey

macrumors newbie
Original poster
Mar 16, 2014
5
0
I have Tuxera NTFS installed. I downloaded the new version of that, which fixed it!

Thanks so much for your help! I feel pretty silly forgetting about that...