Repairing Boot Camp after creating new partition

Christopher Murphy wrote:

See post from 3 days ago with the bullet list including "bcdedit".

It was obvious to me so I already did it but completely forgot to mention...As I said I again restored the bcd with the full procedure (bcdedit etc.) you mentioned above but still without sucess 😕

Well I'm out of ideas. I don't know that Clonezilla understands hybrid MBRs, which is a uniquely Apple thing that's totally non-standard. The only tools I know that are designed to resize file systems on disks containing hybrid MBRs are Wincone, iPartition, and Camptune. There's a bit more favorable reviews of Camptune, although I just read on Macrumors a user having a Camptune problem. Since I haven't used any of them, I can't provide guidance. Doing the resize from command line with open source tools is possible, but requires some rather esoteric knowledge of MBRs, GPTs, and NTFS. I think this particular case, copying an instance of Windows to another disk (partition) while resizing in the process, is maybe more the realm of Winclone. I get the impression that Camptune is more for resizing partitions on one drive; not migration.

Hi Christopher / Scotch,

I am experiencing the same problem as many other seems to be having. I have one SSD (disk 1) with OSX on which is the default boot partition. I also have another HDD (disk 0) with OSX and WINDOWS 7. However, after creating a new partition (disk0s4), the boot meny is no longer showing the Windows partition. Naturally, it still shows in OSX.

Below is the respective overview:

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 469.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Apple_HFS Data 449.9 GB disk0s4

5: Microsoft Basic Data BOOTCAMP 80.3 GB disk0s5

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *128.0 GB disk1

1: EFI 209.7 MB disk1s1

2: Apple_HFS SSD 127.2 GB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s3

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

After installing gdisk and running the sudo gdisk /dev/disk0 I get the following:

GPT fdisk (gdisk) version 0.8.6

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help):

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

Would highly appreciate your inputs on how to proceed further as I have tried most of the solutions in this thread without any luck.

Many thanks in advance!

Like I ask everyone, seemingly over and over again, the basic information you need to provide is:

sudo gpt -r -v show disk0

sudo fdisk /dev/disk0

If you already have gdisk installed, and you're still at its command prompt/

Command (? for help):

You can type the following letters, each followed by return/enter, and post those results intead: r, p, o, q.

As follows:

sudo gpt -r -v show disk0

gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 916015600 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

917694776 878644936 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

1796339712 262144

1796601856 156921856 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 1953525167] <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

Disk /dev/disk0: p

1953525168 sectors, 931.5 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 96171B85-E1D6-4CAD-805D-5EA01AA69A1D

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1953525134

Partitions will be aligned on 8-sector boundaries

Total free space is 263573 sectors (128.7 MiB)

Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 916425239 436.8 GiB AF00 Untitled

3 916425240 917694775 619.9 MiB AB00 Recovery HD

4 917694776 1796339711 419.0 GiB AF00 Data

5 1796601856 1953523711 74.8 GiB 0700 BOOTCAMP

Disk /dev/disk0: o

Disk size is 1953525168 sectors (931.5 GiB)

MBR disk identifier: 0xF80847A9

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 1953525167 primary 0xEE

Letters Q and R does not give any information.

Thanks!

Hi Chris

If you have a wish to could you advise on this thread?

I have asked this before of you, Thanks.

Your disk, disk0, has five partitions. This isn't supported for Boot Camp disks. You can only have four: EFI System partition, OS X, Recovery HD, BOOTCAMP. You have an extra partition, apparently labeled Data.

There is a distinctly non-standard, not highly advised, work around that will let you at least boot Windows, and also share one of the other partitions. You'll need to use gdisk to create a new hybrid MBR from the recovery menu, and add partitions 4 and 5. So you'll type 4<space>5<enter> into the proper field when prompted what partitions you want to add. This will allow you to see the partitions Data and BOOTCAMP from within Windows (and OS X also, of course). But you will not be able to see the primary Macintosh HD from within Windows. Make sure when asked that you do not set GPT partition #4 (MBR partition #2) as bootable. But do make GPT partition #5 (MBR partition #3) bootable. Then use the w command to write out the new partition tables and reboot.

Hi Chris,

Perhaps a bit off-topic, but I found out that:

1. Paragon NTFS for MAC 10.0 is killing the WIN8 startup option in system preferences in OSX 10.8.2! 😠

2. Paragon HFS+ for Windows 10.0 gives a BSOD for HFSSYS in WIN8! 😠

I assumed that the cause of the startup option in OSX was a MBR mix-up but it was not. Contacting Paragon to look into the matter! 😕

Keep you posted! Cheers

Berend de Meyer wrote:

Hi Chris,

Perhaps a bit off-topic, but I found out that:

1. Paragon NTFS for MAC 10.0 is killing the WIN8 startup option in system preferences in OSX 10.8.2! 😠

That is common, common with any 3rd party NTFS converter on a Mac.

Thanks alot Christopher! Good help!

Well I'm out of ideas. [...|

The only tools I know that are designed to resize file systems on disks containing hybrid MBRs are Wincone, iPartition, and Camptune. [...]

I think this particular case, copying an instance of Windows to another disk (partition) while resizing in the process, is maybe more the realm of Winclone. [...]

A pity it didn't work out with the conventional command line tools, I'd like to thank you in any case for your help and your patience!

And finally your last hint was perfect. This is not at all meant as an advertisement more sharing the knowledge of fixing a problem: finally Winclone did its job very well!

Thanks and best regards,

Fab

PS: Actually the partition table finally changed to this...not sure what I can conclude out of this:

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>

2: AF 25 127 15 - 1023 112 53 [ 409640 - 1826171904] HFS+

3: AB 1023 112 54 - 1023 119 13 [1826581544 - 1269536] Darwin Boot

*4: 07 1023 138 25 - 1023 57 56 [1827852288 - 125671424] HPFS/QNX/AUX

This sounds like a Windows 8 Fast Boot induced corruption when used with other OS's. I think you need to disable Fast Boot, but I really don't know anything more about it. You've got to realize Windows 8 isn't supported by Apple, and it wouldn't surprise me if Paragon were to say they aren't supporting NTFS file systems written on by Windows 8 either. So you should confirm that before risking your data, unless of course you don't really care about it.

Hi Chris,

Thansk for your prompt reply! I purchased both Paragon NTFS / HFS+ because they were adverticed as Windows 8 / OSX 10.8.2 COMPATIBLE! As far as I can determin now this is not the case!

Windows gives me a BSOD on the HFSSYS and OSX ML won't boot properly anymore! Very disappointed in both products and even more so, because a post on the Wilders Forum, monitored by Paragon was not ever answered!

If this was twitter I'd shout out loud #FAIL!!!!!!!!!!!!

But never the less I'm enjoying my evening! ;-)

Greetings!

Thnx, preparing to UNINSTALL both Paragon 'drivers'!

The only they do is DRIVE ME NUTS! ;-)

Cheers

Paragon's web site says HFS for Windows supports Windows 8.

But their notes for NTFS for Mac OS X doesn't list Windows 8 modified NTFS file systems, and so far I haven't seen anywhere on their web site an advertisement that it does. So I don't understand why you'd give them the fail whale when you're using an OS that as yet is unsupported by Apple. Quite honestly I think it's dangerous to use Windows 8, dual boot, on a computer contain data you care about at all. If it's a test machine, and the data doesn't matter, then great, go ahead and play with matches.