Win7-32bit on BootCamp won't boot under 10.9

Reply to Loner T:

You have Bootcamp on a drive which is part of a Fusion Drive. Is this an Apple-supported or DIY Fusion drive?

My BootCamp is _NOT_ part of a Fusion Drive. My MBP has zero optical drives, one SSD, and one HD. BootCamp is on the HD. I usually boot from the SSD. I do not recall if I imposed FileVault2 on the drive where the 28GB BootCamp Win7-32bit installation resides before or after my last successful boot into Windows via BootCamp.

Mavericks has a newer version of Bootcamp (5.1).

Yes, and in order to install the new drivers, I need to be able to boot successfully into Windows. That is the thing that I can't do.

If the 28GB partition can be seen as bootable in System Preferences, do you see a blinking cursor in top left corner and does it just sit there after you select it and the Mac reboots?

When I choose the 28GB partition from Startup Manager, it does nothing after I hit ENTER. If I am booted into Mavericks and use Startup Disk in System Preferences to choose the 28GB partition, it does reboot to a black screen with a white blinking underscore character top left.

http://support.apple.com/kb/HT5446 and http://support.apple.com/kb/HT5828 may be worth looking at.

Those articles would perhaps help me if I had a fusion drive. I do not have a fusion drive. I have two drives that are related only in the sense that they are in the same MacBook Pro.

What version of ML did you upgrade from, to Mavericks?

I upgraded from 10.8.5 build 12F45 (they should have called it 10.8.5-S, or 10.8.5.1 – including the so-called supplemental update.

I removed FileVault2 (decrypted) and rebooted. It still won't boot into Windows, via Startup Manager, or via System Preferences > Startup Disk.

Here is some not-very-different looking Terminal output after the decryption. I post it not because I know what I'm doing, but because such info helped me get help before.

user$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *256.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 255.1 GB disk0s2

3: Apple_Boot RecoverySSD 784.2 MB disk0s3

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS Trefoil_Metdale92 471.1 GB disk1s2

3: Apple_Boot RecoveryHDTM 784.2 MB disk1s3

4: Microsoft Basic Data POCTOBAM 28.0 GB disk1s4

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Contin092 *254.7 GB disk2

user$ sudo fdisk /dev/disk1

Password:

Disk: /dev/disk1 geometry: 60801/255/63 [976773168 sectors]

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: AF 1023 254 63 - 1023 254 63 [ 409640 - 920144304] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 920553944 - 1531680] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 922087424 - 54685696] HPFS/QNX/AUX

Figaro92:~ ruser$ sudo gpt -r -vv show disk1

gpt show: disk1: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk1: Suspicious MBR at sector 0

gpt show: disk1: Pri GPT at sector 1

gpt show: disk1: Sec GPT at sector 976773167

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

920553944 1531680 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

922085624 1800

922087424 54685696 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

user$ diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group 22240EB7-B0B5-4360-B152-B6260DFF7F4D

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

Name: Contin092

Status: Online

Size: 255066537984 B (255.1 GB)

Free Space: 16777216 B (16.8 MB)

|

+-< Physical Volume C29AF948-E979-4E5B-B74B-BBD678C3BC99

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

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 255066537984 B (255.1 GB)

|

+-> Logical Volume Family 7BE6A380-1430-4EF6-BABE-E8F157EF304D

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

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 1D815811-7589-464A-8FBF-B3BF84F66E6B

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

Disk: disk2

Status: Online

Size (Total): 254730989568 B (254.7 GB)

Conversion Progress: -none-

Revertible: Yes (unlock and decryption required)

LV Name: Contin092

Volume Name: Contin092

Content Hint: Apple_HFS

user$

OK but did you create a new partition right before the failure to boot Windows?

No, not as far as I know. Does what the diskutil coreStorage commands do behind the scenes when FileVault2 is invoked constitute "creating a new partition?" If so, then, since I did put FileVault2 in place, perhaps I did.

also be really clear what exactly was done in between Windows working and not working, and also when you say "doesn't succeed" state what does happen, i.e. exactly how does it fail.

As I mentioned in my reply to Loner T, I was not sure of the time relationship between encrypting using FileVault2 and the failure of Windows to boot. It is possible that my Windows partition was unbootable before I upgraded to Mavericks. I use Time Machine for iterative backups of the other drive, but not this one. I usually back it up with Carbon Copy Cloner & Winclone. I know I would not back up an unbootable Windows installation.

I _very much_ do not wish to annoy you, and I am grateful for any help I receive.

Before FileVault2, my 28GB Windows partition was at disk1s5, but after FileVault2 it looks like it's at disk1s4, before and after I removed FileVault2.

If my answer to Loner T is not specific enough about exactly how does it fail, then what sort of details do you seek? I'll just copy my answer here:

When I choose the 28GB partition from Startup Manager, it does nothing after I hit ENTER. If I am booted into Mavericks and use Startup Disk in System Preferences to choose the 28GB partition, it does reboot to a black screen with a white blinking underscore character top left.

Thanks again. I'll try not to be a rat in a coffee can.

Well, I am not sure of your source of information, but on my mac pro, I also upgraded to Mavericks, and I am _certain_ that my Boot Camp installation on that machine is Windows 7 32 bit. I can boot into it easily and I just finished exhaustively upgrading it.

Still, thanks, and I appreciate your contribution.

Thank you. I did copy it. I did paste it.

user$ sudo dd if=/dev/disk1s4 count=2 2>/dev/null | hexdump -C

Password:

00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|

00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 f0 f5 36 |........?......6|

00000020 00 00 00 00 80 00 80 00 f8 6f 42 03 00 00 00 00 |.........oB.....|

00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|

00000040 f6 00 00 00 01 00 00 00 ea 89 06 30 a9 06 30 5c |...........0..0\|

00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|

00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|

00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|

00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|

00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|

000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|

000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|

000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|

000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|

000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|

000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|

00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|

00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|

00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|

00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|

00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|

00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|

00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|

00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|

00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |

00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |

000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|

000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|

000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|

000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|

000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|

000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|

00000200 07 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 52 00 |..B.O.O.T.M.G.R.|

00000210 04 00 24 00 49 00 33 00 30 00 00 d4 00 00 00 24 |..$.I.3.0......$|

00000220 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

*

00000250 00 00 00 00 00 00 eb 22 90 90 05 00 4e 00 54 00 |......."....N.T.|

00000260 4c 00 44 00 52 00 00 00 00 00 00 00 00 00 00 00 |L.D.R...........|

00000270 00 00 00 00 00 00 00 00 00 00 66 0f b7 06 0b 00 |..........f.....|

00000280 66 0f b6 1e 0d 00 66 f7 e3 66 a3 52 02 66 8b 0e |f.....f..f.R.f..|

00000290 40 00 80 f9 00 0f 8f 0e 00 f6 d9 66 b8 01 00 00 |@..........f....|

000002a0 00 66 d3 e0 eb 08 90 66 a1 52 02 66 f7 e1 66 a3 |.f.....f.R.f..f.|

000002b0 66 02 66 0f b7 1e 0b 00 66 33 d2 66 f7 f3 66 a3 |f.f.....f3.f..f.|

000002c0 56 02 e8 95 04 66 8b 0e 4e 02 66 89 0e 26 02 66 |V....f..N.f..&.f|

000002d0 03 0e 66 02 66 89 0e 2a 02 66 03 0e 66 02 66 89 |..f.f..*.f..f.f.|

000002e0 0e 2e 02 66 03 0e 66 02 66 89 0e 3e 02 66 03 0e |...f..f.f..>.f..|

000002f0 66 02 66 89 0e 46 02 66 b8 90 00 00 00 66 8b 0e |f.f..F.f.....f..|

00000300 26 02 e8 83 09 66 0b c0 0f 84 5e fe 66 a3 32 02 |&....f....^.f.2.|

00000310 66 b8 a0 00 00 00 66 8b 0e 2a 02 e8 6a 09 66 a3 |f.....f..*..j.f.|

00000320 36 02 66 b8 b0 00 00 00 66 8b 0e 2e 02 e8 58 09 |6.f.....f.....X.|

00000330 66 a3 3a 02 66 a1 32 02 66 0b c0 0f 84 2b fe 67 |f.:.f.2.f....+.g|

00000340 80 78 08 00 0f 85 22 fe 67 66 8d 50 10 67 03 42 |.x....".gf.P.g.B|

00000350 04 67 66 0f b6 48 0c 66 89 0e 72 02 67 66 8b 48 |.gf..H.f..r.gf.H|

00000360 08 66 89 0e 6e 02 66 a1 6e 02 66 0f b7 0e 0b 00 |.f..n.f.n.f.....|

00000370 66 33 d2 66 f7 f1 66 a3 76 02 66 a1 46 02 66 03 |f3.f..f.v.f.F.f.|

00000380 06 6e 02 66 a3 4a 02 66 83 3e 36 02 00 0f 84 1d |.n.f.J.f.>6.....|

00000390 00 66 83 3e 3a 02 00 0f 84 cf fd 66 8b 1e 3a 02 |.f.>:......f..:.|

000003a0 1e 07 66 8b 3e 4a 02 66 a1 2e 02 e8 e0 01 66 0f |..f.>J.f......f.|

000003b0 b7 0e 00 02 66 b8 02 02 00 00 e8 22 08 66 0b c0 |....f......".f..|

000003c0 0f 85 16 00 66 0f b7 0e 5a 02 66 b8 5c 02 00 00 |....f...Z.f.\...|

000003d0 e8 0c 08 66 0b c0 0f 84 42 0c 67 66 8b 00 1e 07 |...f....B.gf....|

000003e0 66 8b 3e 3e 02 e8 3f 06 66 a1 3e 02 66 bb 20 00 |f.>>..?.f.>.f. .|

000003f0 00 00 66 b9 00 00 00 00 66 ba 00 00 00 00 e8 e4 |..f.....f.......|

00000400

Well, my Mac Pro 3,1 is a 5+ year old machine, and has no hardware that the Boot Camp 5 drivers (for Mavericks) would address. Perhaps that is why it works. I have not installed any Boot Camp upgrades on that machine at all, but it works – it boots to Windows 7 32bit, if I ask it to do so.

However, the MBP was built in early January of 2013. Perhaps therein lies the rub.

I am _not_ sure I have booted this particular hardware into Windows 7 ever, even though in February, 2013, I moved the drive (spinning platters, not fusion) from its old home in my old MBP, now that of another household member.

Maybe my Winclone backup is beside the point.

Is there a log I can address with Console.app that will tell me what my "boot behavior" has been since Feb. 3, 2013?

Wow, do problems ever change their apparent shape when one has to answer questions. You guys are great.

I have an install .iso for Win 7 32 bit, and, perhaps, a "System Recovery CDR or DVDR" or something similar.

Should I try to use asr to make a bootable USB (or in Windovs land is that a fool's errand?) or should I try to burn it to a CDR or DVDR?

The MBP has 3 or 4 attached optical drives, despite its lack of an internal optical drive.

Thanks for your help. My forward progress is arrested pending formation of a sound plan.