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.

jfordtmc Author

Level 1

8 points

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:

Used Disk Utility to shrink the Mac OS Extended partition.
Erased free space on that partition.
Booted back into Windows and used MiniTool to extend the bootcamp partition to unallocated space.
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.

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

33 replies

Loner T

Level 9

59,513 points

Jun 10, 2014 8:49 AM in response to .gab

.gab wrote:

Regarding the MacOSX and Java... I installed the Oracle's Java on Mavericks (I was trying to solve other problem, but that also didn't work) and I promise never to do such a thing again.

OT, but for Java to work, you should have this in place

sudo find /library -name java -print -exec ls -l {} \;

/library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java

-rwxrwxr-x 1 root wheel 99216 May 7 16:17 /library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java

Jun 10, 2014 9:26 AM in response to .gab

OK instead of hijacking and resurrecting 4 month old threads, it's better to start a new thread and post the URL in the single much more recent massive thread on this subject.

The way to get the MBR (which is what fdisk shows) to be properly in sync with the GPT (which is what gpt and gdisk show), you are best off using gdisk's option to create a new hybrid MBR, rather than doing this manually in fdisk. fdisk on OS X is beyond ancient, no drives use CHS anymore, they only use LBA so all that matters are the start and end LBA values (note that fdisk and gpt use start LBA and size; gdisk and testdisk report start LBA and end LBA not size).

.gab

Level 1

0 points

Jun 10, 2014 10:24 AM in response to Christopher Murphy

Sorry! Here was the place I found what seemed the answer to my problems and that's why I continued it. I'll try not to resurrect old threads again.

BTW: Thanks for the additional information. I didn't have gdisk installed and fdisk seemed to be able to do what I needed.

Anyway. Sorry again, and, also, thanks again, your earlier information was also very helpful!

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