Recommended Posts

Goal: On my MacBook Pro 13 (mid-2010), I want to run both OS X Lion with FileVault protection, and Windows 7 64-bit (Boot Camp) with BitLocker protection.

Dilemma: Limit of four primary partitions.

Story: I have this 13-inch MacBook Pro (mid-2010) which I rarely used. Several months ago I upgraded its hard drive to a Seagate Momentus XT 500GB, and just recently I loaded Windows 7 through Boot Camp. I was impressed with how well Windows 7 ran on the system, and I was even playing fairly recent games at high graphics quality. I decided that I wanted to secure the hard drive data in case I bring the laptop with me when I go on trips. "No problem", I thought. Both Windows 7 and OS X Lion have drive encryption features. I first attempted to enable BitLocker in Windows, and realized that the MacBook didn't have a TPM chip. No big deal though - I'll just enable BitLocker and use a USB drive for authentication. The next issue I ran into was that BitLocker required a separate boot partition, and with a Boot Camp install, Windows loads everything in one partition.

OS X Lion uses three partitions - an EFI partition, the OS X partition, and a recovery partition. "Hmm, I don't really need that recovery partition", I thought. So I removed the recovery partition, enabled BitLocker, and all was well on the Windows side. I was impressed that I didn't really notice any speed difference with BitLocker enabled.

Next step: Enable FileVault. Only problem: Apparently FileVault requires that OS X recovery partition. So now I have a dilemma. I can only encrypt one OS or the other since OS X uses three partitions if you use FileVault, and Windows 7 uses two partitions if you use BitLocker.

Theoretical workarounds: I wonder if I could somehow get Windows 7's two partitions inside of an extended partition. Windows 7 doesn't allow you to install it like this since a logical partition can't be marked as active. But perhaps I could image them into logical partitions, and maybe it could still boot since it's being selected from the OS X boot menu.

Another idea is to have the Windows 7 boot partition on a USB drive (since I need the USB drive for BitLocker anyways). But this does not look promising since I have a USB drive with WinPE on it, and it does not show up in the Apple boot menu.

Any suggestions on this would be appreciated. I know some might suggest using virtualization for Windows, but that's not a good solution if you intend to do some gaming in Windows. Some might suggest using TrueCrypt for the Windows partition. I tried that, but it apparently doesn't work with Boot Camp.

Doesn't Mac's come with the gpt partition table? You can just set the two windoze partitions as "mbr" primary partitions and the OSX ones (including the EFI partition) as gpt primary ones.

The problem here is that when you boot up through Boot Camp, the OS sees the drive as having an MBR partition table. So to Windows, the OS X partitions count as the first three, and you are left with one available.

It's starting to look like this project may be a failure. I tried gathering an image of the Windows boot partition, then recreating it as a logical partition. But that would not show up on the Apple boot menu.

  • 1 year later...

Doesn't Mac's come with the gpt partition table? You can just set the two windoze partitions as "mbr" primary partitions and the OSX ones (including the EFI partition) as gpt primary ones.

 

http://tumblr.tguum.kr/post/9709394290/enabling-bitlocker-with-osx-lions-filevault-activated

^^ the English is rough, and it is presented in a difficult way to understand besides.

 

It appears possibly this guy is manually editing the Hybrid MBR to effect the suggested fix (using GPT for Mac OS Filevault/boot and MBR for Windows Bitlocker/boot).

 

Can anyone read that post?

 

-Matt

This topic is now closed to further replies.
  • Posts

    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • OK, now ask yourself how are they going to enforce that law? By requiring every single adult to prove their age and provide their legal identity documents to an UNREGULATED 3rd party company that already has a long track record of multiple data breaches. Not to mention, parliament have voted AGAINST this ban, twice, and Starmer is going ahead anyway. So, where's the democracy here, because that looks like dictatorship to me. The solution here is parental responsibility, not government control. Run some public service announcements on TV and UK social media teaching parents how to setup parental controls. That's already been proven to actually work. But the, this is not and has NEVER been about keeping kids safe. It's about control and monitoring. Watching what you're doing online and controlling what you can see and what you can say.
    • Interesting read. I knew the adware was quite controversial at the time, however never realised to the point The Guardian wrote an article about Patchou. I just said no and enjoyed his creation, I’d probably be a lot more wary of something like that today though.
  • Recent Achievements

    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
    • Collaborator
      vjlex earned a badge
      Collaborator
    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      525
    2. 2
      +Edouard
      180
    3. 3
      PsYcHoKiLLa
      105
    4. 4
      Steven P.
      89
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!