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

Previous Page 2 of 3 last Next
  • by Loner T,

    Loner T Loner T Nov 12, 2013 3:29 PM in response to What_iPhone
    Level 7 (24,307 points)
    Safari
    Nov 12, 2013 3:29 PM in response to What_iPhone

    What_iPhone... you can always use a shared directory between OS x and Windows, or a second hard drive which can be connected via SATA/USB/FW and used.

  • by rclutter,

    rclutter rclutter Feb 19, 2014 10:01 AM in response to Christopher Murphy
    Level 1 (5 points)
    Feb 19, 2014 10:01 AM in response to Christopher Murphy

    Similar problem I think. single disk tried minitool to resize the windows partition.

    Now OS x does not see the bootcmp paartiton, and windows will not boot.

     

     

    gpt -r -vv show disk0


    gpt show: disk0: mediasize=250059350016; sectorsize=512; blocks=488397168

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 488397167

          start       size  index  contents

              0          1         MBR

              1          1         Pri GPT header

              2         32         Pri GPT table

             34     409606        

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

      196270352       1776        

      196272128  292124672      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      488396800        335        

      488397135         32         Sec GPT table

      488397167          1         Sec GPT header

     

     

     

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 30401/255/63 [488397168 sectors]

    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE    0   0   2 - 1023 254  63 [         1 -  196272127] <Unknown ID>

    *2: 07 1023 254  63 - 1023 254  63 [ 196272128 -  292124672] HPFS/QNX/AUX

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

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

     


     


  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Feb 19, 2014 11:21 AM in response to rclutter
    Level 3 (555 points)
    Feb 19, 2014 11:21 AM in response to rclutter

    This is a really messed up partition scheme. Partition 1 is missing, which should have been the EFI System partition, yet it starts at sector 34 which is wrong. GPT 2 looks fine yet you can't boot from it, and GPT 3 and MBR 2 contain the same information. So there really isn't anything to go on here. I suggest you just start over: Disk Utility repartition with a single partition configuration (make sure in the Partition tab you change the scheme from Current to 1 Partition). Then restore OS X from backups, repartition with Boot Camp Assistant, reinstall/restore Windows.

     

    Or use a VM.

  • by rclutter,

    rclutter rclutter Feb 19, 2014 11:23 AM in response to Christopher Murphy
    Level 1 (5 points)
    Feb 19, 2014 11:23 AM in response to Christopher Murphy

    gpt 2 is the mac OSX partiton right? I am able to boot to that.

  • by rclutter,

    rclutter rclutter Feb 19, 2014 11:42 AM in response to Christopher Murphy
    Level 1 (5 points)
    Feb 19, 2014 11:42 AM in response to Christopher Murphy

    My question is, can I fix the EFI system partition? and if I know the offsets can we fix the MBR. I have a machine that has a similar setup.

    Thanks!

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Feb 20, 2014 6:17 PM in response to rclutter
    Level 3 (555 points)
    Feb 20, 2014 6:17 PM in response to rclutter

    The EFI System partition can't be fix because t's simply not there. You'd need to use gdisk to add an entry for it starting at LBA 40, and then formatting it as FAT32 understanding you can only do this with command line tools - Disk Utility can only help you by obliterating everything on the disk and starting from scratch. Then you can use gdisk to create a new hybrid MBR and add partitions 2 and 3 making MBR #3 bootable. It's possible to consolidate all of the gdisk tasks first, and then format the EFI System partition.

     

    But ultimately doesn't fix Windows. I can't tell you why it isn't working based on the information provided.

  • by .gab,

    .gab .gab Jun 9, 2014 9:04 AM in response to Christopher Murphy
    Level 1 (0 points)
    Jun 9, 2014 9:04 AM in response to Christopher Murphy

    I have an analog problem.

    OSX sees the Bootcamp partition, but it cannot start. I tried to make the partition "bootable" but it didn't work.

    I thing that when trying to boot the system doesn't know where to start running. Parallels cannot find / mount the bootcamp partition either, though it's perfectly visible from OSX.

     

    The info I have is the following:

     

    GPT

     

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

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

      1563585088        1472        

      1563586560   390623232      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1954209792         295        

      1954210087          32         Sec GPT table

      1954210119           1         Sec GPT header

     

    Diskutil

     

    #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            799.7 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data BOOTCAMP                200.0 GB   disk0s4

     

    Fdisk

     

             Starting       Ending

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

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

    1: EE 1023 254  63 - 1023 254  63 [         1 - 1954210119] <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   

     

    I just backuped everything on windows, and I'm considering nuking that partition and starting from scratch...

    though I tempted to manually edit the fdisk information to make it match to the GDP's... any inputs on this?

     

    Thanks in advance!!

  • by Loner T,

    Loner T Loner T Jun 9, 2014 9:43 AM in response to .gab
    Level 7 (24,307 points)
    Safari
    Jun 9, 2014 9:43 AM in response to .gab

    There are many examples of a "good" fdisk output in this thread.

     

    What "events" took place between Windows booting and not booting?

  • by .gab,

    .gab .gab Jun 9, 2014 1:08 PM in response to Loner T
    Level 1 (0 points)
    Jun 9, 2014 1:08 PM in response to Loner T

    Well, that's a fair question I made myself.

     

    It all started installing a non-apple version of Java.

    On restarting, the Mac didn't shutdown, so after a while I forced it.

     

    After that, it took forever to restart. In fact, it took over 30 minutes me to decide it wasn't starting, so I tried again. After a few runs, I tried with Safe Mode (which couldn't either), run Disk Utility (at this point I disabled the encryption, which I suspect caused the  problem somehow) and Diagnostics after which and -a while-, it loaded everything.

    Uninstalling Java fixed rebooting problem but started a Finder restarting frenzy. Killing Google Drive helped solving that. It alswo worked just disabling "show file sync status".

     

    After that I noticed the Windows problem. The morning before, it worked.

  • by .gab,

    .gab .gab Jun 9, 2014 1:18 PM in response to .gab
    Level 1 (0 points)
    Jun 9, 2014 1:18 PM in response to .gab

    My guess is that my disk should print this on fdisk

     

    #: 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 -  1561905912] HFS+  
    3: AB 1023 254  63 - 1023 254  63 [ 1562315552 -1269536] Darwin Boot

    *4: 07 1023 254  63 - 1023 254  63 [ 1563586560 -  390623232] HPFS/QNX/AUX

     

    Is this right?

  • by Loner T,

    Loner T Loner T Jun 9, 2014 2:03 PM in response to .gab
    Level 7 (24,307 points)
    Safari
    Jun 9, 2014 2:03 PM in response to .gab

    .gab wrote:

     

    run Disk Utility (at this point I disabled the encryption, which I suspect caused the  problem somehow) and Diagnostics after which and -a while-, it loaded everything.

    ...

    After that I noticed the Windows problem. The morning before, it worked.

    DU is notorius for mangling (without recognizing) the Bootcamp MBR, especially if any partitioning activity was done.

     

    The fdisk output you have posted is what your disk should look like under fdisk. You also seem to have picked the correct GPT Start/Size ones. You can also use gdisk (GPT fdisk) or use fdisk to build your MBR. If you do not see an issue with the Missing OS error, Windows (Bootcamp) and Parallels should both work.

     

    If you have a valid Windows backup, winclone is another option for restore, but fixing via fdisk is perhaps the quicker and non-monetary option.

     

    Curious as to what MAC OS X version you are running, since you mention non-apple version of Java.

     

    Apple stopped supporting it's version of Java quite a while ago - http://www.cnet.com/news/apple-not-committing-to-java-support-in-mac-os-x-10-7/

     

    You should be able to use Oracle Java, even though I am not a big fan. It does require some links to be correctly updated. Adobe Flash is in a similar boat.

  • by .gab,

    .gab .gab Jun 9, 2014 8:01 PM in response to Loner T
    Level 1 (0 points)
    Jun 9, 2014 8:01 PM in response to Loner T

    Somehow I cannot edit the values to be the above mentioned... The Partition 1, more precisely,

     

     

    Disk: /dev/disk0    geometry: 121643/255/63 [1954210120 sectors]

    Offset: 0    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE    0   0   2 - 1023 254  63 [         1 -     409639] <Unknown ID>

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

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

    4: 07 1023 254  63 - 1023 254  63 [1563586560 -  390623232] HPFS/QNX/AUX

     

    The Starting Cyl, hd, sec... are automatically set to 0 0 2 when I edit any of the partitions...

    So I'm thinking nuking the windows partition will be the safer path... :/

  • by Loner T,

    Loner T Loner T Jun 10, 2014 6:59 AM in response to .gab
    Level 7 (24,307 points)
    Safari
    Jun 10, 2014 6:59 AM in response to .gab

    Do you want to look at this thread - https://discussions.apple.com/thread/5641066

    before you start all over again?

  • by .gab,

    .gab .gab Jun 10, 2014 7:23 AM in response to .gab
    Level 1 (0 points)
    Jun 10, 2014 7:23 AM in response to .gab

    (Unless someone tells me that the Partition 1 starting on cyl 0 hd 0 sec 2 is perfectly normal). My doubt comes from the previously seen examples...

     

    Googling a bit I saw that this data sometimes appear, but I saw it always in a context where there was some problem with BootCamp and I have no way of knowing if that's a valid possibility...

  • by .gab,

    .gab .gab Jun 10, 2014 7:25 AM in response to Loner T
    Level 1 (0 points)
    Jun 10, 2014 7:25 AM in response to Loner T

    Will do, thanks!

Previous Page 2 of 3 last Next