Looks like no one’s replied in a while. To start the conversation again, simply ask a new 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

29 replies

ramon_au Author

Level 1

0 points

Jul 29, 2015 6:15 AM in response to Loner T

That did not work either. diskutil complains about not being able to unmount volume.

I then tried snow leopard dvd and diskutil got the same error as before (Could not read partitionmap (-9988). As you can see the error code is different, but the message is pretty much the same. I am starting to get the feeling that something is wrong with my partition map.

Loner T

Level 9

59,471 points

Jul 29, 2015 6:24 AM in response to ramon_au

Can you run diskutil repairDisk before you merge the partitions?

ramon_au Author

Level 1

0 points

Jul 29, 2015 6:32 AM in response to Loner T

diskutil complained that repairDisk is deprecated and to use repairVolume instead. I did repairVolume on disk0s3, which worked because that is the recovery volume. I then moved on to disk0s4 and that one errored. It says:

invalid sector size: 0

Volume repair complete

Updating boot support partitions for the volume as required

Error: -9957: Filesystem verify or repair failed

Underlying error: 8: POSIX reports: Exec format error

Have we found the corrupt partition?

Loner T

Level 9

59,471 points

Jul 29, 2015 9:28 AM in response to ramon_au

1. Run the following two erase commands.

diskutil eraseVolume JHFS+ Part4 disk0s4

diskutil eraseVolume JHFS+ Part5 disk0s5

2. Now retry the mergePartitions. MSD and Linux Swap need to be erased first.

ramon_au Author

Level 1

0 points

Jul 29, 2015 1:55 PM in response to Loner T

Finally we are getting a little further. The eraseVolume was successful and after that the mergePartitions worked like a charm. This was the output:

Started erase on disk0s4

Unmounting disk

Erasing

Initialized /dev/rdisk0s4 as a 158 GB case-insensitive HFS Plus volume with a 16384k journal

Mounting disk

Finished erase on disk0s4 Part4

[cool:~]diskutil eraseVolume JHFS+ Part4 disk0s5

Started erase on disk0s5

Unmounting disk

Erasing

Initialized /dev/rdisk0s5 as a 5 GB case-insensitive HFS Plus volume with a 8192k journal

Mounting disk

Finished erase on disk0s5 Part4

[cool:~]diskutil mergepartitions JHFS+ "Macintosh HD" disk0s2 disk0s5

Merging partitions into a new partition

Start partition: disk0s2 Macintosh HD

Finish partition: disk0s5 Part4

Started partitioning on disk0

Merging partitions

Waiting for the disks to reappear

Growing disk

Finished partitioning on disk0

/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 399.0 GB disk0s2

3: Microsoft Basic Data BOOTCAMP 100.8 GB disk0s6

Next up is the recovery disk. I'll post progress soon.

Loner T

Level 9

59,471 points

Jul 29, 2015 2:09 PM in response to ramon_au

Can you test booting in OSX and Windows? Please post the output of sudo fdisk /dev/disk0.

ramon_au Author

Level 1

0 points

Jul 29, 2015 7:03 PM in response to Loner T

Ok, manage to restore the recovery partition through a reinstall of Yosemite. Then reinstated refind and then executed fdisk as per your initial instructions. Output:

fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory

Enter 'help' for information

fdisk: 1> p

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 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: AF 1023 254 63 - 1023 254 63 [ 409640 - 778291384] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 778701024 - 1269536] Darwin Boot

4: 0C 1023 254 63 - 1023 254 63 [ 779970560 - 196802560] Win95 FAT32L

fdisk: 1> setpid 4

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

4: 0C 1023 254 63 - 1023 254 63 [ 779970560 - 196802560] Win95 FAT32L

Partition id ('0' to disable) [0 - FF]: [C] (? for help) 07

fdisk:*1> flag 4

Partition 4 marked active.

fdisk:*1> p

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 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: AF 1023 254 63 - 1023 254 63 [ 409640 - 778291384] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 778701024 - 1269536] Darwin Boot

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

fdisk:*1> w

Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? [n] y

Writing MBR at offset 0.

Loner T

Level 9

59,471 points

Jul 29, 2015 7:21 PM in response to ramon_au

Are both OSX and Windows functional?

ramon_au Author

Level 1

0 points

Jul 29, 2015 8:05 PM in response to Loner T

Well, the repair install that I started previously is finalising, so that is progress at least. I'll report back in once that has finished. But signs are good 🙂

ramon_au Author

Level 1

0 points

Aug 1, 2015 4:38 AM in response to Loner T

It was a bit of a struggle (read: a major struggle of epic proportions) since the reinstall of Windows XP cause so many driver issues in the end. I would recommend people to not resort to that as XP is out of support and a lot of the recommended fixes require downloads from Microsoft.

However, the good news is that I managed to get it up and running with you help Loner T! Thank you so much. I will mark the partition advice as the answer, as I think that definitely moved the dial.

Thanks again!

Loner T

Level 9

59,471 points

Aug 1, 2015 4:52 AM in response to ramon_au

XP and newer more modern hardware are at odds. One option to consider is to run Virtual machines instead of Bootcamp equivalents of older OSes unless native hardware is an absolute requirement. I keep Macs from 2006-2007 just for such purposes, as well as old HP desktops to run Windows NT/95/98. It is much cleaner from a driver perspective.

ramon_au Author

Level 1

0 points

Aug 1, 2015 5:27 AM in response to Loner T

I agree in principle. My macbook is from mid-2008, so well within the XP era. The bootcamp drivers provided with Snow Leopard have been doing their job for the last 3 or 4 years. However, that reinstall did something weird and for whatever reason the existing drivers failed to re-apply themselves to their respective devices. I am still experiencing some weirdness, but overall it seems everything is back to working. Fun times, I definitely learned something about partitions, Windows XP and Yosemite 🙂

Loner T

Level 9

59,471 points

Aug 1, 2015 6:24 AM in response to ramon_au

What kind of weirdness do you observe?

ramon_au Author

Level 1

0 points

Aug 1, 2015 6:51 AM in response to ramon_au

One example is the trackpad driver not wanting to install. It kept giving me a 'driver failed to install' message. In the end I searched on google and found the suggestion to use the generic trackpad driver. This removed the error and made the trackpad available. However, I can't simulate right-clicks with those driver, which makes using Windows a lot harder. I am now fiddling around with removing all the installed drivers, uninstalling and installing bootcamp. That did not work, the trackpad refuses to let go of the windows generic one now and trying to manually override found there is no driver from Apple installed. Bootcamp is now upgrading from 3.0 to 3.1. Let's just hope that has the desired effect.

Bootcamp not working after upgrade to Yosemite