Bootcamp not working after upgrade to Yosemite

Question

Level 1

0 points

Bootcamp not working after upgrade to Yosemite

Another victim of the less than reliable upgrade to Yosemite. First a bit of context:

I had a Snow Leopard machine that I bootcamped with XP and eventually I moved to rEFIt bootmanager to allow me to install Linux side by side as well as a bit of a hobby project. After resisting the temptation for a while to take the free upgrade I finally caved in and went to Yosemite and ended up screwing my setup.

Of course the first thing that disappeared was rEFIt and with it the ability to boot any of my alternative OSes. That was easily fixed by installing rEFInder, which brought the original boot options back. However, both Linux and Windows do not boot anymore. I do not care so much about the Linux stuff as it was a bit of a sandbox anyway, but the Windows one I would like to salvage if possible.

So on Windows, I managed to get the boot.ini to point at the correct partition for startup purposes, only to end up at a blue screen of the 07B variety. This one (not mine, was easier this way) http://4.bp.blogspot.com/-a3LXaNbqGv8/UHGR-5rJboI/AAAAAAAAByc/OeKqMi2J2lo/s1600/ Windows+Stop+0x0000007B.jpg shows precisely what I get.

So, I did a bit of digging on this forum and found quite a few cases and it seems the initial information finally leading to a solution need the following bits of information as a starting point:

+ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 223.5 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 170.0 GB disk0s4

5: Linux Swap 5.0 GB disk0s5

6: Microsoft Basic Data BOOTCAMP 100.8 GB disk0s6

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: CD_partition_scheme *840.2 MB disk1

1: CD_ROM_Mode_1 F4UBCD v4.61 731.6 MB disk1s0

+ diskutil cs list

No CoreStorage logical volume groups found

+ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: /dev/disk0: Suspicious MBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: 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 436492632 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

438171808 332031250 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

770203058 1876

770204934 9765626 5 GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F

779970560 196802560 6 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

+ sudo fdisk /dev/disk0

Disk: /dev/disk0 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 - 438171807] <Unknown ID>

*2: 83 1023 254 63 - 1023 254 63 [ 438171808 - 332031250] Linux files*

3: 82 1023 254 63 - 1023 254 63 [ 770204934 - 9765626] Linux swap

4: 07 1023 254 63 - 1023 254 63 [ 779970560 - 196802560] HPFS/QNX/AUX

From memory I recall having the linux partitions first and then the windows one, as I was following a rEFIt guide at the time.

Another piece of information, the old partition number that boot.ini pointed at was 4 and I got windows to start booting by changing it to 6. As stated before the booting ended in a BSOD.

Info from disk 6 seems to suggest an NTFS partition is present there:

sudo dd if=/dev/rdisk0s6 count=1 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 68 7d 2e |........?....h}.|

00000020 00 00 00 00 80 00 80 00 ff f7 ba 0b 00 00 00 00 |................|

00000030 00 00 0c 00 00 00 00 00 7f af bb 00 00 00 00 00 |................|

00000040 f6 00 00 00 01 00 00 00 3d 44 07 60 85 07 60 fe |........=D.`..`.|

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

00000060 8e d8 e8 16 00 b8 00 0d 8e c0 33 db c6 06 0e 00 |..........3.....|

00000070 10 e8 53 00 68 00 0d 68 6a 02 cb 8a 16 24 00 b4 |..S.h..hj....$..|

00000080 08 cd 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 |...s......f...@f|

00000090 0f b6 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f |.....?.......Af.|

000000a0 b7 c9 66 f7 e1 66 a3 20 00 c3 b4 41 bb aa 55 8a |..f..f. ...A..U.|

000000b0 16 24 00 cd 13 72 0f 81 fb 55 aa 75 09 f6 c1 01 |.$...r...U.u....|

000000c0 74 04 fe 06 14 00 c3 66 60 1e 06 66 a1 10 00 66 |t......f`..f...f|

000000d0 03 06 1c 00 66 3b 06 20 00 0f 82 3a 00 1e 66 6a |....f;. ...:..fj|

000000e0 00 66 50 06 53 66 68 10 00 01 00 80 3e 14 00 00 |.fP.Sfh.....>...|

000000f0 0f 85 0c 00 e8 b3 ff 80 3e 14 00 00 0f 84 61 00 |........>.....a.|

00000100 b4 42 8a 16 24 00 16 1f 8b f4 cd 13 66 58 5b 07 |.B..$.......fX[.|

00000110 66 58 66 58 1f eb 2d 66 33 d2 66 0f b7 0e 18 00 |fXfX..-f3.f.....|

00000120 66 f7 f1 fe c2 8a ca 66 8b d0 66 c1 ea 10 f7 36 |f......f..f....6|

00000130 1a 00 86 d6 8a 16 24 00 8a e8 c0 e4 06 0a cc b8 |......$.........|

00000140 01 02 cd 13 0f 82 19 00 8c c0 05 20 00 8e c0 66 |........... ...f|

00000150 ff 06 10 00 ff 0e 0e 00 0f 85 6f ff 07 1f 66 61 |..........o...fa|

00000160 c3 a0 f8 01 e8 09 00 a0 fb 01 e8 03 00 fb eb fe |................|

00000170 b4 01 8b f0 ac 3c 00 74 09 b4 0e bb 07 00 cd 10 |.....<.t........|

00000180 eb f2 c3 0d 0a 41 20 64 69 73 6b 20 72 65 61 64 |.....A disk read|

00000190 20 65 72 72 6f 72 20 6f 63 63 75 72 72 65 64 00 | error occurred.|

000001a0 0d 0a 4e 54 4c 44 52 20 69 73 20 6d 69 73 73 69 |..NTLDR is missi|

000001b0 6e 67 00 0d 0a 4e 54 4c 44 52 20 69 73 20 63 6f |ng...NTLDR is co|

000001c0 6d 70 72 65 73 73 65 64 00 0d 0a 50 72 65 73 73 |mpressed...Press|

000001d0 20 43 74 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f | Ctrl+Alt+Del to|

000001e0 20 72 65 73 74 61 72 74 0d 0a 00 00 00 00 00 00 | restart........|

000001f0 00 00 00 00 00 00 00 00 83 a0 b3 c9 00 00 55 aa |..............U.|

00000200

The partition is accessible from Mac side and it seems to contain the files I expected to be there.

I would appreciate any help on how to proceed from here.

Posted on Jul 25, 2015 6:41 AM

Reply

Answer 1

Loner T

Level 9

59,471 points

Jul 25, 2015 6:50 AM in response to ramon_au

Let us try the simple fix first. Please ignore the i386 MBR error message, but not any others.

sudo fdisk -e /dev/disk0

p

setpid 4

07

flag 4

p

w

y

Reboot and Test.

Reply

Answer 2

ramon_au Author

Level 1

0 points

Jul 25, 2015 7:04 AM in response to Loner T

Thanks for the rapid response!

That made no difference, XP starts to boot as per before and ends in a BSOD.

Reply

Answer 3

Loner T

Level 9

59,471 points

Jul 25, 2015 7:30 AM in response to ramon_au

Please run XP Startup Repair.

Reply

Answer 4

ramon_au Author

Level 1

0 points

Jul 25, 2015 7:46 AM in response to Loner T

You mean by bootcfg /rebuild? I have run this one in the past, happy to try again. I will report back in once I have executed this.

Reply

Answer 5

Loner T

Level 9

59,471 points

Jul 25, 2015 8:13 AM in response to ramon_au

There should also be options to rebuild MBR, etc. If boot.ini was modified with the correct partition address, you may want to enable boot logging and check the log.

Reply

Answer 6

ramon_au Author

Level 1

0 points

Jul 25, 2015 8:16 AM in response to ramon_au

Interesting. This added a boot option in boot.ini that tries to boot from partition 4. Selecting that option at boot time then led to an error saying that hal.dll is corrupt or missing, which is similar to my initial findings when I managed to get refind working. At that time I manually edited the boot.ini file to create an entry pointing at partition #6, which led to windows starting to boot and then BSOD.

Reply

Answer 7

Loner T

Level 9

59,471 points

Jul 25, 2015 8:19 AM in response to ramon_au

What does the BSOD say? Can you post a screen shot if possible? If it is related to hardware, Safe Boot may help to diagnose. Boot logging may tell you which driver may be causing problems.

Reply

Answer 8

ramon_au Author

Level 1

0 points

Jul 25, 2015 6:56 PM in response to Loner T

Here is the screen shot

I've tried safe booting and that led to exactly the same error, unfortunately. I've also enabled boot logging, I'll post the results once I've grabbed the logfile off the machine. I am currently on a different machine.

Is there any value in running diagnostic tests for partition issues? That seemed to be a cause and way to fixing for many others suffering similar problems.

Reply

Answer 9

Loner T

Level 9

59,471 points

Jul 25, 2015 8:20 PM in response to ramon_au

The reason you are getting a 7B error is because between SL and Yosemite, there are significant device differences, including new devices. XP and many of Windows versions (Vista is one example) do not take kindly to devices being introduced without the corresponding drivers being installed.

If you have tried bootcfg /rebuild, you may have to repeat it several times to get it corrected, till you no longer see the BSOD.

Please also see https://support.microsoft.com/en-us/kb/324103 .

Reply

Answer 10

ramon_au Author

Level 1

0 points

Jul 27, 2015 4:32 AM in response to Loner T

I've tried what you suggested, but it hasn't worked. I've also tried a repair installation (by going into setup, not recovery mode and choosing to repair an existing installation). That had the effect that it loaded the setup files onto the hard drive, pointed boot.ini to partition #4 and couldn't boot at all. After pointing boot.ini to partition #6 the booting started and the BSOD was shown a few seconds in. My (untested) theory that the fact that windows cannot enumerate all partitions is leading to this problem.

Reply

Answer 11

Loner T

Level 9

59,471 points

Jul 27, 2015 4:47 AM in response to ramon_au

Your theory is close. A MBR can hold only 4 entries. XP does not know how to handle the two Linux entries and results BSOD's because it cannot build a partition map.

Is it possible to remove Linux, get Windows back into the first four entries and install Linux once Windows is working?

Reply

Answer 12

ramon_au Author

Level 1

0 points

Jul 27, 2015 8:26 AM in response to Loner T

I am happy to ditch Linux for now, since it isn't booting anyway. Still interesting how I ended up with 6 partitions instead of 5 (as the original number was 4, plus the introduced recovery partition), but that is a mystery for later.

So, what is the best way to merge all the partitions and move windows to the start?

Reply

Answer 13

Loner T

Level 9

59,471 points

Jul 27, 2015 9:22 AM in response to ramon_au

1. From Terminal use

diskutil mergepartitions JHFS+ "Macintosh HD" disk0s2 disk0s5

You will lose Recovery HD and the two Linux partitions.

Please read the following carefully before you do that.

diskutil mergepartitions

Usage: diskutil mergePartitions [force] format name

DiskIdentifier|DeviceNode DiskIdentifier|DeviceNode

Merge two or more pre-existing partitions into one. The first disk parameter

is the starting partition; the second disk parameter is the ending partition;

this given range of two or more partitions will be merged into one.

All partitions in the range, except for the first one, must be unmountable.

All data on merged partitions other than the first will be lost; data on the

first partition will be lost as well if the "force" argument is given.

If "force" is not given, and the first partition has a resizable file system

(e.g. JHFS+), it will be grown in a data-preserving manner, even if a different

file system is specified (in fact, your file system and volume name parameters

are both ignored in this case). If "force" is not given, and the first

partition is not resizable, you will be prompted if you want to erase.

If "force" is given, the first partition is always formatted. You should

do this if you wish to reformat to a new file system type.

Merged partitions are required to be ordered sequentially on disk.

See diskutil list for the actual on-disk ordering; BSD slice identifiers

may in certain circumstances not always be in numerical order but the

top-to-bottom order given by diskutil list is always the on-disk order.

Ownership of the affected disk is required.

Example: diskutil mergePartitions JHFS+ NewName disk3s4 disk3s7

This example will merge all partitions *BETWEEN* disk3s4 and disk3s7,

preserving data on disk3s4 but destroying data on disk3s5, disk3s6,

disk3s7 and any invisible free space partitions between those disks;

disk3s4 will be grown to cover the full space if possible.

2. Reinstall OSX using Internet Recovery - OS X: About OS X Recovery - Apple Support to get Recovery HD.

3. Post the output of the same commands.

4. Rebuild MBR and test.

Reply

Answer 14

ramon_au Author

Level 1

0 points

Jul 28, 2015 4:07 AM in response to Loner T

Thanks for your help so far. Unfortunately an error occurred.

Output:

diskutil mergepartitions JHFS+ "Macintosh HD" disk0s2 disk0s5

Merging partitions into a new partition

Start partition: disk0s2 Macintosh HD

Finish partition: disk0s5

Merging partitions encountered error "Couldn't read partition map (-69876)".

The erase will not occur.

Reply

Answer 15

Loner T

Level 9

59,471 points

Jul 28, 2015 4:27 AM in response to ramon_au

Can you boot into Internet Recovery and then run these steps? This means you run Step 2 first and then Step 1.

Reply