Previous 1 2 3 4 5 6 Next 1,489 Replies Latest reply: Nov 18, 2015 3:46 PM by cmcqueen Go to original post Branched to a new discussion.
  • gmtri Level 1 (0 points)

    Ok, tried a couple more of times with the gidsk commands. Windows boots now! And I see another hard drive in Windows, but don't see Mac HDD in My Computer. If I recall, I used to be able to see it.


    Have not checked the Mac side yet, hopefully it will be okay too. Fingers crossed...

  • lemonsoju Level 1 (0 points)

    gmtri - In my post I added partitions 2 4 5 to the hybrid. That allowed me to see the Mac HDD because #2 partition was the Mac HDD. Based of Chris' reply (thanks Chris) I redid it with just 4 5 - so now I see the shared partition (4) but not the Mac HDD.


    In short, the partitions you see in Windows depends on which partitions you add to the Hybrid. But as per Chris' comment, you probably dont want to add the Mac HDD.

  • gmtri Level 1 (0 points)

    Thanks lemonsoju for your thoughts. That may well be the case. Although I do recall seeing it before with just mac and windows partition (no shared storage), and only windows being added to the MBR in gdisk. Anycase, that's not a worry if everything else works fine. And as Chris and you say, it is for the better that it is not exposed in windows...


    My windows boots now, and I am formatting the new space in windows per Chris' advice. It is taking a while, hopefully will be done... and I need to see if I can get into Mac, and then making sure all works okay. This has been an incredible exercise for someone like me, and a great learning experience, thanks to all of you. Shall keep posted on developments. Cheers...

  • Christopher Murphy Level 3 (555 points)

    Here's a stupid question, do the Boot Camp utilities for Windows bring read/write access to HFS+ volumes in Windows? If so, that's the volume format to choose for sharing files between Windows and Mac OS. There's no advantage to buying Tuxera or Paragon NTFS if Apple already provides the functionality to read/write HFS+ from within Windows.

  • Csound1 Level 8 (46,315 points)

    Christopher Murphy wrote:


    Here's a stupid question, do the Boot Camp utilities for Windows bring read/write access to HFS+ volumes in Windows? If so, that's the volume format to choose for sharing files between Windows and Mac OS. There's no advantage to buying Tuxera or Paragon NTFS if Apple already provides the functionality to read/write HFS+ from within Windows.

    Apples drivers allow read only access to NTFS drives, a 3rd party utility would be needed to allow write access.

  • The hatter Level 9 (60,925 points)

    Apple's read only is also one of the worst and buggy - MacDrive HFS for Windows, Paragon NTFS (v. 10.0 now) is the best supported current NTFS driver for OS X.


    Apple's has trouble mounting, reading files, high overhead, crashes if there is an Apple software RAID present and at various times could BSOD on startup after installing (3.04 and 4.0.0).

  • Christopher Murphy Level 3 (555 points)

    OK so the Windows utils Apple supplies, provides read-only JHFS+/X? Not read-write? And they're buggy?


    Yet another nail...


    I think that VM is the way to do all of this, through its folder sharing.


    And for gamers, do they really need to share files between environments? I'd rather have a NAS for Windows/Mac sharing than either buggy implementations, or 3rd party support. I don't understand how a 3rd party can produce better implementations of party 1's file system on party 2's operating system; while neither operating system company can do this correctly. Embarassing.

  • Scotch_Brawth Level 3 (820 points)

    To be fair to Apple, I've used Boot Camp on a Mac Pro for a good long while, and now on this Mac mini, and never had a problem with accessing my HFS(+)-formatted drives.

    Anyway, I'm turning off notifications for this thread now, seeing as my question's been answered and it's taking on a life of its own   Good luck to everyone who wants to make Boot Camp "Just Work"!



  • gmtri Level 1 (0 points)

    Success! After all these tries, it looks like things are working as they should. Thanks Scotch for raising this thread,  and a big thank you to Christopher for your advice and patience... Hopefully, the computer will continue to perform well going forward... Cheers.

  • jeremy195 Level 1 (0 points)

    Thank you Christopher! The bootcamp thing worked perfectly for me. 


    But then something bad happened...


    I encrypted my new "Data" partition in OSX and the result was a broken bootcamp again!


    So... I ran through your fix again, but this time for some reason bootcamp was listed as partition 6.  So I entered number 6 at the appropriate point in your guide, and it worked again.  Perfect!


    So I now have three partitions - MacHD, Bootcamp, and an encrypted Data partition.  And I still have the recovery partition too!


    So thanks again Christopher, this has really helped me out.  I've only had the Mac two weeks, and it's my first ever Mac.  2012 MacBook Pro 13", i7, 750Gb, 8Gb, Mountain Lion and Windows 7 Ultimate.


    Thank you, Thank you, Thank you


  • Christopher Murphy Level 3 (555 points)

    I know that when you convert an existing JHFS+/X volume to be encrypted, the volume  is resized slightly to make room for the header/gap area for Core Storage. The GUID for the partition is changed from HFS+ to the GUID for Core Storage. So the GPT is being altered. As appears to be the case, if you have more than four partitions (in the GPT), Apple's tools indiscriminately blow away the hybrid MBR, replacing it with a PMBR, and that's why Windows doesn't boot.


    What's interesting is that the slice number for your Windows partition changed. Can you post the result from:

    sudo gpt -r -vv show disk0

    diskutil list

    diskutil cs list


    First one displays the GPT contents. Second lists devices and slices. Third lists core storage devices. All are read-only commands.


    FWIW, the volume contained within the Core Storage partition, when mounted, gets a whole disk (a virtual disk) value. i.e. with a normal HFS+ volume, its partition is designated as something like /dev/disk0s2, meaning disk0 slice 2 (or partition 2). Once that slice becomes Core Storage, the encrypted volume within ends up behaving as a logical device at something like /dev/disk1.

  • jeremy195 Level 1 (0 points)

    Hi Christopher, this is the result, hope it helps.


    thanks again


    Last login: Sun Aug 19 22:41:02 on console

    Jeremys-MacBook-Pro:~ Jeremy$ sudo gpt -r -vv show disk0


    gpt show: disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1465149167

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

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

       390351096   780988168      4  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

      1171339264      262144      5  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      1171601408   293545984      6  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1465147392        1743        

      1465149135          32         Sec GPT table

      1465149167           1         Sec GPT header

    Jeremys-MacBook-Pro:~ Jeremy$ diskutil list


       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *750.2 GB   disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            199.0 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:          Apple_CoreStorage                         399.9 GB   disk0s4

       5:                 Apple_Boot Boot OS X               134.2 MB   disk0s5

       6:       Microsoft Basic Data BOOTCAMP                150.3 GB   disk0s6


       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS Data                   *399.5 GB   disk1

    Jeremys-MacBook-Pro:~ Jeremy$ diskutil cs list

    CoreStorage logical volume groups (1 found)


    +-- Logical Volume Group 35102E9D-7E60-4C09-976B-5EEE57C14FEA


        Name:         Data

        Size:         399865942016 B (399.9 GB)

        Free Space:   16777216 B (16.8 MB)


        +-< Physical Volume DC68ACC4-1CBB-49D4-B71E-B1B19F55154B

        |   ----------------------------------------------------

        |   Index:    0

        |   Disk:     disk0s4

        |   Status:   Online

        |   Size:     399865942016 B (399.9 GB)


        +-> Logical Volume Family F18F9484-61D3-427A-A9D5-55CBC4F79AF6


            Encryption Status:       Unlocked

            Encryption Type:         AES-XTS

            Conversion Status:       Complete

            Conversion Direction:    -none-

            Has Encrypted Extents:   Yes

            Fully Secure:            Yes

            Passphrase Required:     Yes


            +-> Logical Volume FE8E8548-E956-487C-9A8F-9342260D3C61


                Disk:               disk1

                Status:             Online

                Size (Total):       399530393600 B (399.5 GB)

                Size (Converted):   -none-

                Revertible:         Yes (unlock and decryption required)

                LV Name:            Data

                Volume Name:        Data

                Content Hint:       Apple_HFS

    Jeremys-MacBook-Pro:~ Jeremy$

  • Christopher Murphy Level 3 (555 points)




    Partition 2 is normally the Macintosh HD volume, this is a 185GB partion for you and I'm not sure what's on it, other than it's marked as being HFS+.


    Partition 3 is a 620MB Apple Boot partition, which I'm 99% certain is the Lion Recovery HD.


    Partition 4 is 372GB Core Storage partition, inside of which will be your File Vault 2 volume. Normally I expect partition 2 to be converted to Core Storage and encrypted on the fly - at least that's what Lion did.


    Partition 5 is a 128MB Apple Boot partition and I'm not exactly sure what that's for, maybe it's the Mountain Lion Recovery HD? Why is it separate from partition 3? I've heard of other people upgrading to Mountain Lion and they end up with two Recover HD's as options when booting and holding the option/alt key at the start up chime. Do you get that? I don't have a good explanation for this unless somehow your intent was to maintain a Lion and Mountain Lion dual-boot configuration, and in effect triple boot with Windows (which by the way is not something I'm aware of that Apple supports).


    Anyway, unless something significant has changed in Mountain Lion, there isn't a way for Apple's own tools to support Windows booting in such a configuration where there are more than 4 partitions on a disk containing Windows. They simply won't create a hybrid MBR for such a disk.

  • Jeremy7812 Level 1 (0 points)

    Hi Christopher, it's jeremy195.  (I couldn't change my email address so I created a new account here)


    Anyway, I'm not sure if partition 5 is the Mountain Lion recovery, or why it's seperate to partition 3.  But I don't have two recovery HD's when I boot, only the usual one (recovery 10.8), which seems to be working fine.  I have MacHD, Bootcamp, and recovery.  My new MacBookPro is working fine now thanks to the fix you shared.  I'm really happy with it.  Still getting used to it as it's only two weeks old and I've always used PC until now. Thanks again

  • Christopher Murphy Level 3 (555 points)

    Ahh I see what I missed before. The encrypted volume "Data" is a separte partition from "Macintosh HD". So you are only encrypted the Data volume, not Macintosh HD is what it looks like.


    Just make sure you keep prolific backups of your data! The layout of your disk is rather non-standard, which doesn't mean it's bad or unstable, but does mean most people and utilities, including Apple's, may not know what to do with it if modifications are attempted. And keep in mind modifications to the disk layout can be initiated by user or by software upgrade installers. And whatever you do, don't ever use a Windows disk utility to try and change the partition layout of volume sizes!

Previous 1 2 3 4 5 6 Next