Dual-boot dual-encryption notes [ RAW NOTES ]
This document created: 2015-07-13
Last updated: 2015-07-14
Mason is attempting to get both FileVault2 and Bitlocker working on a 2015 MacBook Air.
The main resource claiming this is possible is:
Steps:
PARTITION THE DISK MANUALLY
Nope failed at this step. After creating another partition, Disk Utility then says "You may only merge this partition with the one before it." (I do that just for completeness, and then it says "You may only split this partition into two.")
This is apparently because it is a Core Storage volume? This post:
http://blog.twocanoes.com/post/42453643591/bootcamp-on-a-3-tb-fusion-drive
...is from Twocanoes, so pretty legit.
So, first I partition the MacBook's SSD into two, using Disk Utility (the max that app will allow):
Then I follow steps of blog post above:
Solution, for posterity:
1. Split disk into 2 partitions using Disk Utility, and rename the first one MAC and the second WINDOWS, with the
2. Then do this:
mason@IT-PC-MACPRO /Volumes>
mason@IT-PC-MACPRO /Volumes> sudo diskutil splitPartition /Volumes/WINDOWS 2 MS-DOS WINDOWS 196G MS-DOS BLBOOT 0b
Password:
Started partitioning on disk3s4 WINDOWS
Splitting
Unmounting disk
Waiting for the disks to reappear
Formatting disk3s6 as MS-DOS (FAT) with name WINDOWS
512 bytes per physical sector
/dev/rdisk3s6: 382716608 sectors in 5979947 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=104472576 drv=0x80 bsec=382810112 bspf=46719 rdcl=2 infs=1 bkbs=6
Mounting disk
Formatting disk3s7 as MS-DOS (FAT) with name BLBOOT
512 bytes per physical sector
/dev/rdisk3s7: 2943336 sectors in 367917 FAT32 clusters (4096 bytes/cluster)
bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=487284736 drv=0x80 bsec=2949120 bspf=2875 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished partitioning on disk3s4 WINDOWS
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage 52.6 GB disk3s2
3: Apple_Boot Recovery HD 650.0 MB disk3s5
4: Microsoft Basic Data WINDOWS 196.0 GB disk3s6
5: Microsoft Basic Data BLBOOT 1.5 GB disk3s7
mason@IT-PC-MACPRO /Volumes>
OK. That worked for partitioning, at least.
BOOT INTO OS X AND TURN ON FILEVAULT
OK. Enable FileVault and restart. Re-open the Security and Privacy prefs pane to monitor progress, and wait until complete.
INSPECT GPT PARTITION TABLE
And boom! We are already looking very different from that helpful blog post. Maybe we need to nuke Core Storage off the drive first? (Can we do that?)
its-MacBook-Air:~ it$ sudo gpt -rv show -l disk0
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
gpt show: disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - "EFI System Partition"
409640 102791776 2 GPT part - "Customer"
103201416 1269536 3 GPT part - "Recovery HD"
104470952 1624
104472576 382810112 4 GPT part - "Macintosh HD 2"
487282688 2048
487284736 2949120 5 GPT part - "BLBOOT"
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
its-MacBook-Air:~ it$
Note the GPT data does not match the Disk Utility names. Also note the "Suspicious MBR" warning. Here is a screenshot:
But anyway, onwards!
REWRITE MBR
OK FUCK I THINK WE ARE FUCKED:
its-MacBook-Air:~ it$ sudo fdisk -e /dev/disk0
Password:
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1>
BLEAH!
<Mason goes home for day; bathes lice-ridden offspring; drinks herbal tea while trying to fix garbage disposer until 1am>
OK, I have no idea what fdisk and MBR are (fuckdisk? Major Butt Reamer?) -- these are relics I haven't thought about for decades.
But, plod on a little more, at least until I kill this Mac.
Interesting link about mostly-unrelated boot issues: http://jonsview.com/fixing-mbr-tables-on-imac-or-mbp-triple-boot-setups
fdisk: 1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AC 1023 254 63 - 1023 254 63 [ 409640 - 102791776] <Unknown ID>
3: AB 1023 254 63 - 1023 254 63 [ 103201416 - 1269536] Darwin Boot
4: 0B 1023 254 63 - 1023 254 63 [ 104472576 - 382810112] Win95 FAT-32
fdisk: 1>
Hmm, the diskutil tool seems to have a better grasp of reality than gpt:
Last login: Mon Jul 13 16:50:19 on ttys000
dual:~ it$ sudo diskutil list
Password:
Sorry, try again.
Password:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 52.6 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data WINDOWS 196.0 GB disk0s4
5: Microsoft Basic Data BLBOOT 1.5 GB disk0s5
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS MAC *52.3 GB disk1
Logical Volume on disk0s2
3D877145-7F3D-40DA-8716-0198A7FF0DE4
Unlocked Encrypted
dual:~ it$
OK fuck it... we go!!
Here is my terminal session, including me pulling an ID-10-T and accidentally fucking up with fdisk repeatedly:
its-MacBook-Air:~ it$ sudo gpt -rv show -l disk0
Password:
gpt show: disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - "EFI System Partition"
409640 102791776 2 GPT part - "Customer"
103201416 1269536 3 GPT part - "Recovery HD"
104470952 1624
104472576 382810112 4 GPT part - "Macintosh HD 2"
487282688 2048
487284736 2949120 5 GPT part - "BLBOOT"
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$ sudo fdisk -e /dev/disk0
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> help
help Command help list
manual Show entire man page for fdisk
reinit Re-initialize loaded MBR (to defaults)
auto Auto-partition the disk with a partition style
setpid Set the identifier of a given table entry
disk Edit current drive stats
edit Edit given table entry
erase Erase current MBR
flag Flag given table entry as bootable
update Update machine code in loaded MBR
select Select extended partition table entry MBR
print Print loaded MBR partition table
write Write loaded MBR to disk
exit Exit edit of current MBR, without saving changes
quit Quit edit of current MBR, saving current changes
abort Abort program without saving current changes
fdisk: 1> abort
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$
its-MacBook-Air:~ it$ sudo fdisk -e /dev/disk0
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1>
fdisk: 1>
fdisk: 1>
fdisk: 1>
fdisk: 1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AC 1023 254 63 - 1023 254 63 [ 409640 - 102791776] <Unknown ID>
3: AB 1023 254 63 - 1023 254 63 [ 103201416 - 1269536] Darwin Boot
4: 0B 1023 254 63 - 1023 254 63 [ 104472576 - 382810112] Win95 FAT-32
fdisk: 1> add 1
Invalid command 'add'. Try 'help'.
fdisk: 1>
fdisk: 1> edit 1
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
Partition id ('0' to disable) [0 - FF]: [EE] (? for help)
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [63] 1
Partition size [1 - 490234751]: [490234751] 409600
fdisk:*1> ERASE
Invalid command 'ERASE'. Try 'help'.
fdisk:*1> erase
fdisk:*1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
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
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> add 1
Invalid command 'add'. Try 'help'.
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> help
help Command help list
manual Show entire man page for fdisk
reinit Re-initialize loaded MBR (to defaults)
auto Auto-partition the disk with a partition style
setpid Set the identifier of a given table entry
disk Edit current drive stats
edit Edit given table entry
erase Erase current MBR
flag Flag given table entry as bootable
update Update machine code in loaded MBR
select Select extended partition table entry MBR
print Print loaded MBR partition table
write Write loaded MBR to disk
exit Exit edit of current MBR, without saving changes
quit Quit edit of current MBR, saving current changes
abort Abort program without saving current changes
fdisk:*1> select 1
Partition 1 is not an extended partition.
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> edit 1
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Partition id ('0' to disable) [0 - FF]: [0] (? for help) EE
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [63] 1
Partition size [1 - 490234751]: [490234751] 409600
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> edit 2
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Partition id ('0' to disable) [0 - FF]: [0] (? for help) 07
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [409601] 104472576
Partition size [1 - 385762176]: [385762176] 382810112
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> edit 2
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
2: 07 1023 254 63 - 1023 254 63 [ 104472576 - 382810112] HPFS/QNX/AUX
Partition id ('0' to disable) [0 - FF]: [7] (? for help) 07
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [409601] 487284736
Partition size [1 - 2950016]: [2950016] 2949120
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> write
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] y
Writing MBR at offset 0.
fdisk: 1>
fdisk: 1>
fdisk: 1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 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 - 409600] <Unknown ID>
2: 07 1023 254 63 - 1023 254 63 [ 487284736 - 2949120] 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
fdisk: 1>
fdisk: 1>
fdisk: 1>
fdisk: 1>
fdisk: 1> ohfuckifuckinoverwrotepart2withdatafor3damnit
Invalid command 'ohfuckifuc'. Try 'help'.
fdisk: 1>
fdisk: 1>
fdisk: 1>
fdisk: 1> edit 2
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
2: 07 1023 254 63 - 1023 254 63 [ 487284736 - 2949120] HPFS/QNX/AUX
Partition id ('0' to disable) [0 - FF]: [7] (? for help) 07
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [409601] 104472576
Partition size [1 - 385762176]: [385762176] 382810112
fdisk:*1>
fdisk:*1>
fdisk:*1> edit 3
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Partition id ('0' to disable) [0 - FF]: [0] (? for help) 07
Do you wish to edit in CHS mode? [n]
Partition offset [0 - 490234752]: [487282688] 487284736
Partition size [1 - 2950016]: [2950016] 2949120
fdisk:*1>
fdisk:*1>
fdisk:*1>
fdisk:*1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 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 - 409600] <Unknown ID>
2: 07 1023 254 63 - 1023 254 63 [ 104472576 - 382810112] HPFS/QNX/AUX
3: 07 1023 254 63 - 1023 254 63 [ 487284736 - 2949120] HPFS/QNX/AUX
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
fdisk:*1> write
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] y
Writing MBR at offset 0.
fdisk: 1>
Reboot here (with sudo /sbin/reboot now ). Worked. Doing fdisk print shows the MBR as we left it.
INSERT WINDOWS BOOT MEDIA AND BOOT USING OPTION KEY TO BOOT FROM IT
This works. The booting, I mean.
However, installing does NOT work, because:
This MS help post is related: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/windows-7-the-selected-disk-has-an-mbr-partition/5aee7be1-3038-4290-a283-75806dc1be1f?page=~pagenum~&auth=1
On this superuser.com post, there's a guy recommending using Shift-F10 to get windows command prompt and using diskpart to deal with this:
http://superuser.com/questions/481650/cant-use-bootcamp-partition-for-windows-8-installation
So I tried that. I doubt that will work, although it shouldn't hurt.
UPDATE: yep that of course did nothing, formatting the disk partition that was already formatted...
But, this superuser comment looks promising! It seems that the entire fuckin MBR thing was a red herring, if Windows 8 won't install on an EFI booting machine with a fucking MBR.
So I think I need to fix the GPT partition table.
Install GPT fdisk from this site:
http://www.rodsbooks.com/gdisk/
Then:
Last login: Tue Jul 14 10:25:14 on console
dual:~ it$ sudo gdisk /dev/disk0
Password:
GPT fdisk (gdisk) version 1.0.0
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 64931A2B-5051-469A-ADE9-F8CCCEF886C4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 4541 sectors (2.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 103201415 49.0 GiB AF05 Customer
3 103201416 104470951 619.9 MiB AB00 Recovery HD
4 104472576 487282687 182.5 GiB 0700 Macintosh HD 2
5 487284736 490233855 1.4 GiB 0700 BLBOOT
Command (? for help): x
Expert command (? for help): n
Expert command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/disk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
dual:~ it$ /sbin/reboot now
Rebooted. Check what fdisk thinks about things:
dual:~ it$ sudo fdisk -e /dev/disk0
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> print
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 0 0 2 - 1023 255 63 [ 1 - 490234751] <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
fdisk: 1>
OK. That's either awesome, or lame. Who knows?
What I am concerned about is that the GPT shit still looks wacky. Well really it is that "Macintosh HD 2" label. Hmm but the sectors look the same as what was in the MBR I made, why not use gdisk to change them?
dual:~ it$ sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.0
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 64931A2B-5051-469A-ADE9-F8CCCEF886C4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 4541 sectors (2.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 103201415 49.0 GiB AF05 Customer
3 103201416 104470951 619.9 MiB AB00 Recovery HD
4 104472576 487282687 182.5 GiB 0700 Macintosh HD 2
5 487284736 490233855 1.4 GiB 0700 BLBOOT
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): c
Partition number (1-5): 4
Enter name: WINDOWS
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 64931A2B-5051-469A-ADE9-F8CCCEF886C4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 4541 sectors (2.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 103201415 49.0 GiB AF05 Customer
3 103201416 104470951 619.9 MiB AB00 Recovery HD
4 104472576 487282687 182.5 GiB 0700 WINDOWS
5 487284736 490233855 1.4 GiB 0700 BLBOOT
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/disk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
dual:~ it$
Reboot. Fuck it let's use Option and go straight into the windows installer again.
Bada-boom! At least the install is proceeding.
... 30 min later... BABOOM! Booted into Windows 8.
Now, shut down and see if OS X still boots?
Hmm, No, but Windows boots FAST! Must be the EFI vs MBR thing... I have read that EFI booting on a MacBook Air is wayyyy faster than the Bootcamp way. Seems true. Booted in like 3 seconds.
Now the moment of truth: Can I boot OS X if I hold the Option key down??
YUP!
INSTALL BOOT CAMP DRIVERS
This step must be done now because otherwise I can't even use the trackpad and I want to know (before trying to hack BitLocker) if the normal boot disk control software works in this scenario.
OK. And Boot Camp control panel on Windows lets me select OS X boot disk, and in OS X the Startup Disk control panel lets me select Windows.
All working fine.
RUN ALL WINDOWS UPDATES
Just in case there are fixes to Bitlocker I want to run all Windows updates before... in the weird ass Windows 8 UI figuring out how to do this is about as hard as figuring all this shit up to here.
OK, there are 130 updates, sigh... how many will fail and how long will it take to resolve all the Windows Update failures? NOBODY CAN KNOW THAT
11:29 START
Ten minutes in, still at 0%, doesn't look like it is doing anything... but I guess it is:
13:11 Windows offers to reboot and proceed with updating (no error messages displayed so far... amazing)
13:29 Windows reboots and a second attempt at Windows Update results in a 80240016 error.
(This is normal Windows behavior and is likely unrelated to anything we are trying to do.) Pressing the "Retry" button makes it proceed with some of the updates. OH WOW IT COMPLETED THEM ALL. One more run claims there are no more updates available so... ONWARD!
ENABLE BITLOCKER HACK FOR NO TPM
I am using this superuser.com post as my lode star...
I also referred to this: http://www.howtogeek.com/192894/how-to-set-up-bitlocker-encryption-on-windows/
I edited the registry setting:
Then I right-clicked the drive in Windows Explorer and chose "Enable Bitlocker for this drive":
Go thru the wizard, sticking with the defaults...
Save the Bitlocker recovery key to my USB stick, for now.
Then, I rebooted. w00t! Bitlocker up in this booch!
OK it boots and then I have to let it actually do the encryption before answering the most important question...
DID ENABLING BITLOCKER NUKE THE OS X PARTITION OR NOT??!?!
Well, the Boot Camp control panel doesn't think so:
HO LEE FUK, IT WORKED!!!
However the Startup Disk prefs pane in OS X cannot see the Bitlocker-encrypted Windows partition. That's ok, as booting with Option key down still works.
I notice, though that I still have this BLBOOT partition I created when I was still following the obsolete MBR instructions.
Now then, I want to compare what gdisk says now vs what it said earlier. Where did Bitlocker create it's funknard partition?
Last login: Tue Jul 14 14:04:39 on console
dual:~ it$ sudo gdisk
Password:
GPT fdisk (gdisk) version 1.0.0
Type device filename, or press <Enter> to exit: /dev/disk0
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 64931A2B-5051-469A-ADE9-F8CCCEF886C4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 6046 sectors (3.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 103201415 49.0 GiB AF05 Customer
3 103201416 104470951 619.9 MiB AB00 Recovery HD
4 104472576 486664734 182.2 GiB 0700 WINDOWS
5 486666240 487282687 301.0 MiB 2700 挐᪩È
6 487284736 490233855 1.4 GiB 0700 BLBOOT
Command (? for help):
Vs before:
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 103201415 49.0 GiB AF05 Customer
3 103201416 104470951 619.9 MiB AB00 Recovery HD
4 104472576 487282687 182.5 GiB 0700 WINDOWS
5 487284736 490233855 1.4 GiB 0700 BLBOOT
So... it SHRUNK the WINDOWS partition, and created the fabulously named 挐᪩È partition for its mysterious bitlocking purposes. OK. This makes me believe that I didn't need to create the BLBOOT partition at all.
NEXT STEPS: Do this again and see if we can condense this 20-hour process into a 1-hour process.
END OF DOCUMENT (2015-07-14 16:08 TOKYO)