Skip navigation

iMac 13,2 Late 2012 3TB Boot Camp Windows 7 Install - SOLVED! (unsupported)

9634 Views 34 Replies Latest reply: Apr 4, 2013 2:27 PM by bkervaski RSS
1 2 3 Previous Next
Bill Kervaski Level 1 Level 1 (15 points)
Currently Being Moderated
Dec 14, 2012 2:40 PM

Ok, apparently a lot of folks (like me) bought a 3TB iMac expecting to install Windows 7 only to be greeting with a message from Boot Camp saying it isn't supported on 3TB hard drives .. hey I thought we were beyond these file system limitations, what do I know ;p

 

It's really easy to get Windows 7 installed, here's the steps (This is *NOT* supported by Apple -- assess your risk before proceeding):

 

* Just in case create a recovery USB stick - http://support.apple.com/kb/DL1433

* Boot into recovery mode

* Launch Terminal

* Remove the coreStorage Logical Volume Group (this is what's preventing you from freely partitioning with Disk Utility)

** diskutil coreStorage list

** diskutil coreStorage delete UUID

* Exit Terminal

* Launch Disk Utility

* Create 3 Partitions, 1TB Each, make sure your Windows partition is 2nd as both the OSX and WINDOWS partition *must* exists below 2.2TB

** Partition 1 - OSX (HFS)

** Partition 2 - WINDOWS (FAT)

** Partition 3 - DATA (HFS) .. store all your iTunes stuff here?

* Exit Disk Utility

* Install OS X

* Create a Windows 7 USB install drive with Boot Camp on another computer

* Boot with your Windows 7 USB install drive, install Windows 7, be careful to choose the correct partition when you format

* Download the Windows 7 Boot Camp drivers - http://swcdn.apple.com/content/downloads/25/23/041-6932/ezgnx0guny5bw6vm7to92ile w38ptli0z5/BootCampESD.pkg

* Install Boot Camp drivers

* Enjoy!

 

Didn't have time to write a book (sorry) but I'll try to check back to answer any questions (no promises).

 

Cheers!

  • Christopher Murphy Level 2 Level 2 (470 points)

    Can you post the results of

     

    sudo gpt -v -rr show diskX

    sudo fdisk /dev/diskX

     

    Where X = the number of the actual physical 3TB drive? This number can be found using 'diskutil list'.

  • Christopher Murphy Level 2 Level 2 (470 points)

    Short version is that I agree with your assessment that this is not supported by Apple. Anyone doing this is advised to have a most aggressive and consistent backup strategy. That should be the case anyway with any Boot Camped disk, but all the more the case with this 2.2+TB disk work around for Boot Camp.

     

    Long version is that I think the work around is interesting. I'll bet Apple would consider the work around a bug and may try to close it if they ever figure out it's possible. I say that because Apple's tools, both Disk Utility and diskutil, refuse to produce a hybrid MBR if the GPT contains 5 or more partitions. MBR can only contain four partitions. In a Lion or Mountain Lion installation, three partitions are needed: EFI System, OS X, and Recovery HD. This leaves one partition for one additional BIOS booting OS.

     

    For a good primer, and then some, on hybrid MBRs (vs protective MBRs) see this article by Rod Smith, the developer of GPT fdisk (gdisk) and rEFInd, the EFI boot manager:

     

    Hybrid MBRs: The Good, the Bad, and the So Ugly You'll Tear Your Eyes Out

     

     

    Bill's around gets around the Disk Utility limitation by creating three partitions, but are actually four due to the EFI System partition. One partition is formatted as a FAT32 volume, therefore a hybrid MBR is created. The installer then splits the first HFSJ partition into two to make the Recovery HD. But instead of nuking the hybrid MBR entirely as a result of a fifth partition being created like Disk Utility would, the installer seems to just drop the MBR entry for the last partition, which is Bill's 2nd HFS+ data partition. Since there can be no MBR entry for it (no more entries, and MBR can't define a location beyond 2.2TB anyway), the main negative consequence is this volume can't be accessed from within Windows, no matter what file system is used.

     

    Normally, if only Disk Utility is used to add another partition to a disk already containing four, like what happens when people with OS X and Windows already installed want another partition for data, the result is the hybrid MBR is blown away in favor of a protective MBR, and access to Windows is lost. It simply vanishes. (Access can be restored with a tool like gdisk, but it's a CLI only application, and exactly what to do in each instance isn't exactly obvious.)

     

    There is anecodatal evidence from these and other forums that upon major upgrades (SL to Lion, Lion to ML) if the disk contains 5+ partitions, and/or the GPT and MBR are not in sync, something during installation causes the hybrid MBR to be replaced with a protective MBR. So again, good reason to make judicious backups especially before using Disk Utility to make repairs or OS updates/upgrades. I don't know exactly what causes this to occur so I can't say exactly what situation to avoid.

     

    Anyway, Boot Camp is a rabbit hole. It gets vastly deeper and more risky with each "unsupported" behavior added on, and this one adds both a fifth partition as well as a disk larger than 2.2TB. Risky in that if anything modified either the MBR or GPT, it'll get messy fast! But at Bill now has in effect backed up both his MBR and GPT partition schemes on Apple's forums so his chances of recovery should something get messed up, are much better. So it's not a bad idea to take a snapshot of your current partition mappings if you go down the rabbit hole.

     

    As for why there's a limitation on disk size: Apple hardware supports Windows through an EFI compatibility support module, called the CSM. It's BIOS baked into an EFI module. In effect when booting Windows, Apple hardware has BIOS. When booting OS X it uses only EFI. EFI specifies GPT partition scheme. Windows booted in BIOS mode only honors MBR boot disks, hence the need for hybrid MBRs on Apple hardware. And MBR encoding only supports disk sizes of 2.2TB or less. So the problem is a combination of limitations. The long term solution is for Apple to support EFI mode boot of Windows, and it's unclear if that will happen as none of Apple's hardware meets the minimum Windows requirement for UEFI 2.x spec firmware or greater. Apple EFI is based on the Intel EFI 1.10 spec. Nevertheless some people are having varying degrees of success getting Windows 8 to boot on Apple hardware in EFI mode. There's a huge thread on Mac Rumors of people working on this.

  • jmoney0461 Calculating status...

    Bill -

     

    Can you write out the scripts to do this? I don't know enough code/mac language to perform this. I did however just get in my 3tb new iMac and was shocked to see that Boot Camp doesn't work. Clearly I didn't do enough research.

     

    Thanks

     

    JRM

  • Christopher Murphy Level 2 Level 2 (470 points)

    He already posted a clear step by step, I'm not sure what else you need.

  • V Bassan Level 1 Level 1 (0 points)

    Anyone know if this solution also works with the 3TB Fusion Drive? If so, the Fusion Drive will also contunue to work as a single drive (SSD and HDD) for the first partition?

  • jmoney0461 Level 1 Level 1 (0 points)

    I'm in the middle of trying it with fusion 3tb hd. I made a mistake in the instructions so I'm currently going through internet recovery. we'll see how things look in the next hour.

     

    JRM

  • V Bassan Level 1 Level 1 (0 points)

    Good Luck! It will be great news if you can make it work since I already bought my 3TB iMac and one of the main uses is Windows gaming (Wich would be terrible with any kind of virtualization).

  • jmoney0461 Level 1 Level 1 (0 points)

    thanks mine is my big boy machine for engineering work. useless if I can't get windows on here.

  • Christopher Murphy Level 2 Level 2 (470 points)

    No because Fusion Drive is leveraging Core Storage which is an Apple logical volume manager. It requires XNU to be running first to implement Core Storage. Meaning you can take advantage of this through a VM, but not natively booting Windows which will have no way of understanding the proprietary on-disk-format to make Fusion work.

  • V Bassan Level 1 Level 1 (0 points)

    OK, no Fusion Drive to the Windows partition (2nd partition), but what about the 1st Partition (Partition 1 - OSX (HFS)? When I remove the coreStorage Logical Volume Group to divide the HDD in 3 partitions it is definitive or it can be restored to allow the OSX to use the Fusion Drive functionality? (Im sorry if theres any flaw in my question - Im not an expert in the system core functions)

  • Christopher Murphy Level 2 Level 2 (470 points)

    I don't know how smart the new Disk Utility and Boot Camp Assistant are in dealing with this situation. The message boards are littered with people experiencing data loss because Disk Utility can do the wrong thing when the user goes even slightly off script: the script is to use Boot Camp Assistant for everything related to setting up drives for use with Windows.

     

    But based on what I've read you should be able to use Boot Camp Assistant to make a Windows volume on either the SSD or HDD; and then the remaining space on both SSD and HDD can be used by Core Storage as a Fusion drive for OS X. But you have to have Windows entirely on SSD or entirely on HDD.

  • dil_king Calculating status...

    I am trying to do the method above but its keeps saying "Ownership of the affected disk is required" how do i get that and what are the commands and my new imac wont let me boot off a mac osx lion disk that i burnt through the dmg through the appstore why is it doing that ?  I wanna do this so i can run terminal through the setup disc.

     

    xxxx-iMac:~ xxxx$ diskutil coreStorage list

    CoreStorage logical volume groups (1 found)

    |

    +-- Logical Volume Group xxxxx

        =========================================================

        Name:         Macintosh HD

        Size:         1483372879872 B (1.5 TB)

        Free Space:   0 B (0 B)

        |

        +-< Physical Volume xxxxxxxx

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

        |   Index:    0

        |   Disk:     disk0s2

        |   Status:   Online

        |   Size:     1483372879872 B (1.5 TB)

        |

        +-> Logical Volume Family xxxx

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

            Encryption Status:       Unlocked

            Encryption Type:         None

            Conversion Status:       NoConversion

            Conversion Direction:    -none-

            Has Encrypted Extents:   No

            Fully Secure:            No

            Passphrase Required:     No

            |

            +-> Logical Volume xxxx

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

                Disk:               disk1

                Status:             Online

                Size (Total):       1483054104576 B (1.5 TB)

                Size (Converted):   -none-

                Revertible:         No

                LV Name:            Macintosh HD

                Volume Name:        Macintosh HD

                Content Hint:       Apple_HFS

    xxxx-iMac:~ xxxx$ diskutil coreStorage delete UUID

    Error deleting CoreStorage Logical Volume Group: Not a valid CoreStorage Logical Volume Group UUID (-69778)

    xxxx-iMac:~ Jerry$ diskutil coreStorage delete UUID disk0

    Usage:  diskutil coreStorage delete lvgUUID

    Delete a CoreStorage logical volume group. All logical volumes will be removed.

    Ownership of the affected disk is required.

    xxxx-iMac:~ Jerry$

  • Christopher Murphy Level 2 Level 2 (470 points)

    You need sudo in front of these commands. And UUID is a place holder for the actual UUID for the thing you're deleting.

1 2 3 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.