jfordtmc

Q: Bootcamp Partition Will Not Mount - Size Bootcamp Partition Will Not Mount - Also Size Discrepancies

I have bootcamp installed on an internal hard drive in my Mac Pro running 10.8.5.  This HD had two partitions, one of which I had 200GB allocated for my Windows install.  I reached a point where I was at nearly 100% capacity on that drive and needed more room.  This is what I did:

 

  1. Used Disk Utility to shrink the Mac OS Extended partition.
  2. Erased free space on that partition.
  3. Booted back into Windows and used MiniTool to extend the bootcamp partition to unallocated space.
  4. MinoTool then performed a restart and finished it's job upon startup.

 

I am still able to boot into Windows and Mac just fine and I did create a backup of each OS before starting.

 

I have two issues now, however.  Parallels no long recognized that Bootcamp partition.  I decided to delete that VM and I had to uninstall Parallels completely anyways due to an upgrage isse to Parallels 9.  After upgrading, Creating a VM from my BC was not an option.  This is because the BC partition will not mount, it is greyed out in Disk Utitlity.

 

I tried installing Tuxera NTFS and the disk still cannot be mounted. 

 

The other issue is that Disk Utility does not show the Bootcamp partition with the correct size.  It still shows it with the original 200GB but does show that the Mac Partition was shrunk.  In Windows, however, either using MiniTool or Windows Disk Managment, it shows the correct sizes for the partitions.

 

I'll attach a screenshot of DU.

 

diskUtil.pngtuxeraError.png

 

I would like to be able to mount the drive successfully so that I can use the partition once again for Parallels.

 

This is the system.log display when attempting to mount the BOOTCAMP partition and when disabling Tuxera from the system preferences:

 

Nov  7 08:35:46 ***-mac-pro.local com.apple.SecurityServer[27]: Succeeded authorizing right 'system.volume.internal.mount' by client '/Applications/Utilities/Disk Utility.app' [973] for authorization created by '/Applications/Utilities/Disk Utility.app' [973] (100013,0)

Nov  7 08:35:46 ***-mac-pro.local com.apple.SecurityServer[27]: Succeeded authorizing right 'system.volume.internal.mount' by client '/usr/sbin/diskarbitrationd' [15] for authorization created by '/Applications/Utilities/Disk Utility.app' [973] (100002,0)

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS driver 3.10 [Flags: R/W].

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS volume name BOOTCAMP, version 3.1.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_lookup_inode_by_name(): Directory index record with VCN 0x3 is corrupt.  Corrupt inode 0x5.  Run chkdsk.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_windows_hibernation_status_check(): Failed to find inode number for hiberfil.sys.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs warning (device /dev/disk3s3, pid 5414): ntfs_system_inodes_get(): Failed to determine if Windows is hibernated.  Will not be able to remount read-write.  Run chkdsk.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_attr_find_in_attribute_list(): Base inode 0x9 contains corrupt attribute list attribute. Unmount and run chkdsk.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_inode_read(): Failed to lookup data attribute.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_inode_read(): Failed (error 5) for inode 0x9. Run chkdsk.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_inode_attach(): Failed to load inode 0x9.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_secure_load(): Failed to load $Secure.

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_mount(): Failed to load system files (error 5).

Nov  7 08:35:47 ***-mac-pro kernel[0]: NTFS-fs error (device /dev/disk3s3, pid 5414): ntfs_mount(): Mount failed (error 5).

Nov  7 08:35:48 ***-mac-pro.local com.apple.SecurityServer[27]: Succeeded authorizing right 'system.privilege.admin' by client '/Applications/System Preferences.app' [5297] for authorization created by '/Applications/System Preferences.app' [5297] (100012,0)

 

Thanks,

Josh

Posted on Nov 7, 2013 8:44 AM

Close

Q: Bootcamp Partition Will Not Mount - Size Bootcamp Partition Will Not Mount - Also Size Discrepancies

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Nov 7, 2013 8:50 AM in response to jfordtmc
    Level 6 (15,624 points)
    Nov 7, 2013 8:50 AM in response to jfordtmc

    Your issue is that you used Disk Utility to resize/modify a disk containing a Boot Camp partition. You will have to erase and reformat the drive then reinstall OSx. Then you will have to go through the Boot Camp Assistant process to create a Boot Camp partition and reinstall Windows.

     

    In the future, if you must resize a Boot Camp partition use CampTune not Disk Utility.

     

    If you want to use Parallels instead of creating another Boot Camp partition just install Parallels after you erase and format the drive and  reinstall OSx.

  • by jfordtmc,

    jfordtmc jfordtmc Nov 7, 2013 9:00 AM in response to BobTheFisherman
    Level 1 (4 points)
    Mac OS X
    Nov 7, 2013 9:00 AM in response to BobTheFisherman

    Mac OSX is not installed on the same partition.  Windows does work fine.  Thank you for the CampTune suggestion.  I thought I was doing the right thing by using MiniTool, I didn't think I needed a third party tool for shrinking the other partition.

     

    Knowing that OSX is not on the same partition and that I can boot to Windows just fine, is there something that can be done to mount the partition?  I have considered just using a different drive and starting over with Windows. It will be a process as I have a ton of work applications installed.  So it goes.

     

    Josh

  • by jfordtmc,

    jfordtmc jfordtmc Nov 7, 2013 9:04 AM in response to BobTheFisherman
    Level 1 (4 points)
    Mac OS X
    Nov 7, 2013 9:04 AM in response to BobTheFisherman

    This is the screenshot from MiniTool on the Windows side.

    miniToolCapture.PNG

  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Nov 7, 2013 9:12 AM in response to jfordtmc
    Level 6 (15,624 points)
    Nov 7, 2013 9:12 AM in response to jfordtmc

    I don't understand what you are saying. No one said OSx is on the same partition. OSx and Boot Camp are on the same drive. By using the wrong tool, Disk Utility, you damaged your drive's configuration. You must do as I suggested.

     

    After doing as I suggested, reinstall your applications and get your data from your backup.

  • by jfordtmc,

    jfordtmc jfordtmc Nov 7, 2013 9:39 AM in response to BobTheFisherman
    Level 1 (4 points)
    Mac OS X
    Nov 7, 2013 9:39 AM in response to BobTheFisherman

    My mistake, I didn't mean the same partition, I meant the same drive.  Mac OSX and Windows are not installed on the same hard drive. 

  • by Loner T,

    Loner T Loner T Nov 8, 2013 4:22 PM in response to jfordtmc
    Level 7 (24,601 points)
    Safari
    Nov 8, 2013 4:22 PM in response to jfordtmc

    Josh,

     

    Can you post the output of following two commands from the MAC OS X side using Terminal?

     

    sudo gpt -r -vv show disk3

     

    sudo fdisk /dev/disk3

     

     

    GPT and FDISK are available in OSX as shown below.

     

    gpt is /usr/sbin/gpt

    fdisk is /usr/sbin/fdisk



  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Nov 9, 2013 12:11 PM in response to jfordtmc
    Level 3 (555 points)
    Nov 9, 2013 12:11 PM in response to jfordtmc

    It sounds to me like the MBR on the disk containing Windows is correct, which is why it successfully boots Windows. But the GPT on that disk is wrong, which is why it isn't mountable by Tuxera NTFS nor usable by Parallels. So the solution is to fix the GPT on that disk. Before doing this, you should post the results from the read only commands mentioned by LonerT with a slight modification, refer to the raw disk using rdisk3 instead of disk3.

     

    sudo fdisk /dev/rdisk3

    sudo gpt -r -v show /dev/rdisk3

     

    I'm assuming disk3 is the disk that contains Windows.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Nov 9, 2013 12:12 PM in response to Christopher Murphy
    Level 3 (555 points)
    Nov 9, 2013 12:12 PM in response to Christopher Murphy

    If the disk is less than 2TB, the alternative is to obliterate the GPT. This is actually in some sense preferable to hybrid MBRs. But before deleting information it's best to make sure we have the information backed up (to the forum) in case it's needed.

  • by jfordtmc,

    jfordtmc jfordtmc Nov 10, 2013 9:33 AM in response to Christopher Murphy
    Level 1 (4 points)
    Mac OS X
    Nov 10, 2013 9:33 AM in response to Christopher Murphy

    Thanks Christopher and Loner,

     

    Here are the results of the termainal commands:

     

    **-**-mac-pro:~ ****$ sudo fdisk /dev/rdisk2

    Disk: /dev/rdisk2            geometry: 77825/255/63 [1250263728 sectors]

    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

    2: AF   25 127  15 - 1023 254 63 [    409640 -  390632848] HFS+       

    *3: 07 1023 254 63 - 1023 254  63 [ 391043072 -  859219968] HPFS/QNX/AUX

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

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

    **-**-mac-pro:~ ****$ sudo gpt -r -v show /dev/rdisk2

    gpt show: /dev/rdisk2: mediasize=640135028736; sectorsize=512; blocks=1250263728

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

    391042488         584

    391043072 467052544 3 

    858095616 392167424      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

    1250263040         655

    1250263695          32 Sec GPT table

    1250263727           1 Sec GPT header

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Nov 10, 2013 9:50 AM in response to jfordtmc
    Level 3 (555 points)
    Nov 10, 2013 9:50 AM in response to jfordtmc

    The MBR and GPT aren't in sync, in particular partition 3 mismatch. Based on the description of events and behavior, there's every reason to conclude the MBR is correct and the GPT is incorrect. You have several options in no particular order

     

    1. Use gdisk's expert menu to zap the GPT only. So you remove the GPT, but you do NOT blank the MBR. Then OS X will use only the MBR since only it exists, and you'll see Boot Camp - Windows and so will Parallels. Strictly speaking you ought to use fdisk to remove the first partition, since its partition type id suggests it's a GPT disk. It probably doesn't hurt anything to not do this, but I haven't tested it.

     

    2. Use gdisk to to delete partition 3, and then create a new partition 3 with the proper start and end sector values from fdisk. Note that fdisk and gdisk will have the same start sector value, however fdisk reports "size" whereas gdisk reports "last sector". So to get the proper value into gdisk, you need to add the start and size values from fdisk, and enter that as the last sector value when creating the new partition with gdisk. The type code for this partition needs to be 0700 when asked. This keeps the disk as primarily GPT, with a hybrid MBR.

     

    Option 1 means any future changes to the partition layout will not require special tools since there's only one partition map. Option 2 means you'll likely have to make sure you use the correct tools, or make repairs, following any partition layout change.

  • by Loner T,

    Loner T Loner T Nov 10, 2013 10:10 AM in response to jfordtmc
    Level 7 (24,601 points)
    Safari
    Nov 10, 2013 10:10 AM in response to jfordtmc

    Josh,

     

    I will defer to Christopher on correcting the GPT, but I agree it is incorrect. On a much simpler, single disk Macmini with Bootcamp...

     

    sudo gpt -r -vv show /dev/rdisk0

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

    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 976773167

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

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

      726773128        632        

      726773760  249999360      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      976773120         15        

      976773135         32         Sec GPT table

      976773167          1         Sec GPT header

     

    sudo fdisk /dev/rdisk0

    Disk: /dev/rdisk0          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 -  725093952] HFS+       

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

    *4: 07 1023 254  63 - 1023 254  63 [ 726773760 -  249999360] HPFS/QNX/AUX

     

    diskutil list /dev/disk0

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *500.1 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            371.2 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data BOOTCAMP                128.0 GB   disk0s4

     

    PS: I see Christopher's response.

  • by jfordtmc,

    jfordtmc jfordtmc Nov 10, 2013 4:00 PM in response to Christopher Murphy
    Level 1 (4 points)
    Mac OS X
    Nov 10, 2013 4:00 PM in response to Christopher Murphy

    Thanks for the help guys, extrememly informative, but a little over my head.  I'm not sure how to use fdisk or gdisk.

     

    I'm clearing off space on an internal 1TB hard drive now and may consider doing a clean install of windows on that drive. It will be a long process to get programs, etc. back on there and another 4 days of syncing my Dropbox but it may be worth it. Aside from the hard drive issues, I have not been able to update bootcamp drivers since version 3.something, If I do, I get the BSOD and I haven't found a solution to that in my research.

     

    Thanks again for your help.

     

    Josh

  • by What_iPhone,

    What_iPhone What_iPhone Nov 11, 2013 12:03 AM in response to jfordtmc
    Level 1 (0 points)
    Nov 11, 2013 12:03 AM in response to jfordtmc

    Hi can anyone tell me if you can create 3 Partitions

     

    1, OSX 10.9 Mac OS extended

    2, Data Mac OS extended

    3, Win 8 NTFS

     

    and be able to see all 3 partitions from both Win8 and OSX

     

    I can only get OSX to see all partitions

    Win8 can see the OSX 10.9 but not the data partiton ecept for with the windows disk manager which shows the Data partition as unallocated ? I did try to format via windows and that broke all partitions needing a full rebulid

     

     

    Thanks Phill

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Nov 11, 2013 12:34 AM in response to What_iPhone
    Level 3 (555 points)
    Nov 11, 2013 12:34 AM in response to What_iPhone

    That configuration is not supported. Visible partitions, you can have OS X and Windows, that's it.

Page 1 of 3 last Next