Repairing Boot Camp after creating new partition

Thanks Crhistopher, i will try fixing the MBR

In the meantime:

00000000 33 c0 8e d0 bc 00 7c fb 50 07 50 1f fc be 1b 7c |3.....|.P.P....||

00000010 bf 1b 06 50 57 b9 e5 01 f3 a4 cb bd be 07 b1 04 |...PW...........|

00000020 38 6e 00 7c 09 75 13 83 c5 10 e2 f4 cd 18 8b f5 |8n.|.u..........|

00000030 83 c6 10 49 74 19 38 2c 74 f6 a0 b5 07 b4 07 8b |...It.8,t.......|

00000040 f0 ac 3c 00 74 fc bb 07 00 b4 0e cd 10 eb f2 88 |..<.t...........|

00000050 4e 10 e8 46 00 73 2a fe 46 10 80 7e 04 0b 74 0b |N..F.s*.F..~..t.|

00000060 80 7e 04 0c 74 05 a0 b6 07 75 d2 80 46 02 06 83 |.~..t....u..F...|

00000070 46 08 06 83 56 0a 00 e8 21 00 73 05 a0 b6 07 eb |F...V...!.s.....|

00000080 bc 81 3e fe 7d 55 aa 74 0b 80 7e 10 00 74 c8 a0 |..>.}U.t..~..t..|

00000090 b7 07 eb a9 8b fc 1e 57 8b f5 cb bf 05 00 8a 56 |.......W.......V|

000000a0 00 b4 08 cd 13 72 23 8a c1 24 3f 98 8a de 8a fc |.....r#..$?.....|

000000b0 43 f7 e3 8b d1 86 d6 b1 06 d2 ee 42 f7 e2 39 56 |C..........B..9V|

000000c0 0a 77 23 72 05 39 46 08 73 1c b8 01 02 bb 00 7c |.w#r.9F.s......||

000000d0 8b 4e 02 8b 56 00 cd 13 73 51 4f 74 4e 32 e4 8a |.N..V...sQOtN2..|

000000e0 56 00 cd 13 eb e4 8a 56 00 60 bb aa 55 b4 41 cd |V......V.`..U.A.|

000000f0 13 72 36 81 fb 55 aa 75 30 f6 c1 01 74 2b 61 60 |.r6..U.u0...t+a`|

00000100 6a 00 6a 00 ff 76 0a ff 76 08 6a 00 68 00 7c 6a |j.j..v..v.j.h.|j|

00000110 01 6a 10 b4 42 8b f4 cd 13 61 61 73 0e 4f 74 0b |.j..B....aas.Ot.|

00000120 32 e4 8a 56 00 cd 13 eb d6 61 f9 c3 49 6e 76 61 |2..V.....a..Inva|

00000130 6c 69 64 20 70 61 72 74 69 74 69 6f 6e 20 74 61 |lid partition ta|

00000140 62 6c 65 00 45 72 72 6f 72 20 6c 6f 61 64 69 6e |ble.Error loadin|

00000150 67 20 6f 70 65 72 61 74 69 6e 67 20 73 79 73 74 |g operating syst|

00000160 65 6d 00 4d 69 73 73 69 6e 67 20 6f 70 65 72 61 |em.Missing opera|

00000170 74 69 6e 67 20 73 79 73 74 65 6d 00 00 00 00 00 |ting system.....|

00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

*

000001b0 00 00 00 00 00 2c 44 63 89 3c 89 3c 00 00 00 fe |.....,Dc.<.<....|

000001c0 ff ff ee fe ff ff 01 00 00 00 27 40 06 00 00 fe |..........'@....|

000001d0 ff ff af fe ff ff 28 40 06 00 b0 a8 0c 32 00 fe |......(@.....2..|

000001e0 ff ff ab fe ff ff d8 e8 12 32 28 5f 13 00 80 fe |.........2(_....|

000001f0 ff ff 07 fe ff ff 00 48 26 32 00 18 12 08 55 aa |.......H&2....U.|

00000200

Well the first two bytes look like normal valid bootloader code for Windows XP. I'd google "windows xp" boot repair. If you put windows xp in quotes it will only find results for windows xp.

I think you need to be patient in trying to repair this. Starting over will probably not work well (or at least be a different rabbit hole) because Lion/Mountain Lion expressly don't support Windows XP! So trying to reinstall XP with Lion/MountainLion Boot Camp Assistant will probably fail.

Christopher Murphy, your help is very much appreciated. I'm having a very similar issue that all started when I used the Mac Disk Utility to shrink the Mac partition. I had a previously installed bootcamp partition and hoped to first shrink the mac partition and then use the free space to expand the Windows Bootcamp partition, however I'm sure it's not surprising that it failed and I can no longer boot into windows.

I've managed to follow instructions to the point where I can now select "Windows" from the boot selection screen by holding alt/option on startup, however it still fails to load windows. I'm left with a blinking underscore insertion point on a black screen.

I have also booted a Windows 7 disc to utilize the startup recovery, however I am unable make any repairs because at the point in the process where I would normally select the Windows install that I would like to repair, I'm given no options. It seems to be oblivious to the fact that my windows partition exists, keeping me from accessing the C: drive to attempt the previously mentioned /fixmbr and /fixboot command. Drive X: is all I get! And of course the D: drive that has my windows install disc.

I will post the results of the previously mentioned read-only commands, as well as the contents of rEFIt's partition inspector. I'm hoping that the issue is clear from this information. I can't see anything obvious, but I'm positive that you know heaps more than I do about the subject, so your help would be greatly appreciated.

sudo gpt -r -vv show disk0

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

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

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

876663672 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

877933216 49528160

927461376 49311744 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

diskutil list <---dev/disk1 is my windows 7 install disc

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 448.6 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 25.2 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GRMCULFRER_EN_DVD *4.0 GB disk1

rEFIt Partition Inspector

*** Report for internal hard disk ***

Current GPT partition table:

# Start LBA End LBA Type

1 40 409639 EFI System (FAT)

2 409640 876663671 Mac OS X HFS+

3 876663672 877933215 Mac OS X Boot

4 927461376 976773119 Basic Data

Current MBR partition table:

# A Start LBA End LBA Type

1 1 409639 ee EFI Protective

2 409640 876663671 af Mac OS X HFS+

3 876663672 877933215 ab Mac OS X Boot

4 * 927461376 976773119 07 NTFS/HPFS

MBR contents:

Boot Code: Unknown, but bootable

Partition at LBA 40:

Boot Code: None (Non-system disk message)

File System: FAT32

Listed in GPT as partition 1, type EFI System (FAT)

Partition at LBA 409640:

Boot Code: None

File System: HFS Extended (HFS+)

Listed in GPT as partition 2, type Mac OS X HFS+

Listed in MBR as partition 2, type af Mac OS X HFS+

Partition at LBA 876663672:

Boot Code: None

File System: HFS Extended (HFS+)

Listed in GPT as partition 3, type Mac OS X Boot

Listed in MBR as partition 3, type ab Mac OS X Boot

Partition at LBA 927461376:

Boot Code: Windows BOOTMGR (Vista)

File System: Unknown

Listed in GPT as partition 4, type Basic Data

Listed in MBR as partition 4, type 07 NTFS/HPFS, active

And also,

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 - 409639] <Unknown ID>

2: AF 1023 254 63 - 1023 254 63 [ 409640 - 876254032] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 876663672 - 1269544] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 927461376 - 49311744] HPFS/QNX/AUX

So the MBR seems properly formed, and agrees with the GPT on the start and end LBA for the Windows volume, which also has a boot flag set. I don't have a good suggestio if the Windows install disk, even at the command line, doesn't see this partition. Even if it doesn't see it as a valid NTFS file system, it should see that partition so that seems like the first thing to figure out, and run a chkdisk followed by a chkdsk /f on that volume to make sure the file system is healthy and repair it if it isn't. Next you reboot and get your data off if you don't have a current backup.

Once you have a current backup, back to the Windows install DVD and run through the options in this documentto repair the bootloader. You need to click "Click here to show/hide more information" under "Bootrec.exe options" to see the details. I think a corrupt bootloader is the likely cause for it not booting, but you don't want to make changes that involve the file system until you know it's repaired. In order I would use /FixMbr, /FixBoot, and /RebuildBcd and see where that gets you. /ScanOs may be needed before /RebuildBcd, I haven't actually had to use that feature yet.

Repairing the bootloader is proving to be rather difficult. There are steps at the RE command prompt that require locating files on drive C:, such as "bcdedit /export C:\BCD_Backup". The command is unable to locate the file because as far as the RE command prompt seems to recognize, there is no C: drive.

I feel like that might also be why /FixMbr, /FixBoot, and /RebuildBcd are not solving my problem. Perhaps those are commands that are to be run from the C: directory as opposed to the X: directory that the command prompt defaults to after finding no OS install during the startup repair.

It may be worth noting that even when booting from the windows disc and running the repair command prompt, I am still able to view my windows partition with a diskutil list command.

I'm going to post another result for a command I've seen you request previously, just for kicks, and because I've got no clue as to the implications of said results. Perhaps you will see something I do not. I have a feeling that if this doesn't yield any sort of progress that I might have to dig elsewhere for answers, or just deal with not getting it back.

sudo dd if=/dev/disk0s4 of=~/twosectors.bin bs=512 count=2

2+0 records in

2+0 records out

1024 bytes transferred in 0.027939 secs (36651 bytes/sec)

alex-clarks-imac:~ alexclark$ hexdump -C ~/twosectors.bin

00000000 ca 0e 1d 0f 1c 0f 12 31 35 b2 4c 03 07 1c 0f 1a |.......15.L.....|

00000010 01 00 04 00 00 f8 00 00 11 00 04 00 01 00 00 00 |................|

00000020 00 00 20 00 e0 1f 00 00 00 00 00 00 00 00 00 00 |.. .............|

00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

00000040 80 00 29 00 00 00 00 4e 4f 20 4e 41 4d 45 20 20 |..)....NO NAME |

00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|

00000060 7b 8e c1 8e d9 bd 00 7c 88 4e 02 8a 56 40 b4 41 |{......|.N..V@.A|

00000070 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a f6 c1 01 |..U..r...U.u....|

00000080 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd 13 73 05 |t..F..-.V@....s.|

00000090 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 d1 80 e2 |.....f...@f.....|

000000a0 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 66 f7 e1 |?.......Af...f..|

000000b0 66 89 46 f8 83 7e 16 00 75 38 83 7e 2a 00 77 32 |f.F..~..u8.~*.w2|

000000c0 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 00 e8 2b |f.F.f..........+|

000000d0 00 e9 2c 03 a0 fa 7d b4 7d 8b f0 ac 84 c0 74 17 |..,...}.}.....t.|

000000e0 3c ff 74 09 b4 0e bb 07 00 cd 10 eb ee a0 fb 7d |<.t............}|

000000f0 eb e5 a0 f9 7d eb e0 98 cd 16 cd 19 66 60 80 7e |....}.......f`.~|

00000100 02 00 0f 84 20 00 66 6a 00 66 50 06 53 66 68 10 |.... .fj.fP.Sfh.|

00000110 00 01 00 b4 42 8a 56 40 8b f4 cd 13 66 58 66 58 |....B.V@....fXfX|

00000120 66 58 66 58 eb 33 66 3b 46 f8 72 03 f9 eb 2a 66 |fXfX.3f;F.r...*f|

00000130 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 8a ca 66 8b |3.f..N.f......f.|

00000140 d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 40 8a e8 c0 |.f....v....V@...|

00000150 e4 06 0a cc b8 01 02 cd 13 66 61 0f 82 75 ff 81 |.........fa..u..|

00000160 c3 00 02 66 40 49 75 94 c3 42 4f 4f 54 4d 47 52 |...f@Iu..BOOTMGR|

00000170 20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 | ............|

00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

*

000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 42 4f |..............BO|

000001b0 4f 54 4d 47 52 20 69 73 20 6d 69 73 73 69 6e 67 |OTMGR is missing|

000001c0 ff 0d 0a 44 69 73 6b 20 65 72 72 6f 72 ff 0d 0a |...Disk error...|

000001d0 50 72 65 73 73 20 61 6e 79 20 6b 65 79 20 74 6f |Press any key 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 00 ac c1 ce 00 00 55 aa |..............U.|

00000200 a7 0f 75 0f 4f 0a c6 5e c4 8c 0a 06 a7 0f 7e 0f |..u.O..^......~.|

00000210 c5 5e 4e 0a ca 55 16 76 4c 01 04 7c 0f ca 5e 2d |.^N..U.vL..|..^-|

00000220 0a c8 5c 14 08 7c 0f 7b 0f 76 0f 2b 0a c9 5e c7 |..\..|.{.v.+..^.|

00000230 44 28 06 7b 0f 77 0f 76 0f 2a 0a 26 8d 03 7e 4c |D(.{.w.v.*.&..~L|

00000240 01 04 75 0f c7 5e 25 0a c6 94 08 06 71 0f 70 0f |..u..^%.....q.p.|

00000250 24 0a 20 0a bf 44 28 08 70 0f 6f 0f 09 08 1f 0a |$. ..D(.p.o.....|

00000260 cd 5e 4f 22 34 bd 4c 01 04 6f 0f 4e 61 cc 5e ce |.^O"4.L..o.Na.^.|

00000270 5c 14 06 6f 0f 6b 0f 6a 0f 1e 0a 1a 54 03 0a ff |\..o.k.j....T...|

00000280 ff 10 08 6a 0f 5e 0f 4b 61 19 0a d0 5c 99 08 5e |...j.^.Ka...\..^|

00000290 0f ac 0f 10 08 36 0b d1 5e cf 54 08 0e 10 08 ac |.....6..^.T.....|

000002a0 0f 15 08 d0 5e d2 5e 4a 61 ff ff ad 0f 15 5c 01 |....^.^Ja.....\.|

000002b0 02 91 5f d1 5e d3 44 13 08 ac 0f ae 0f ad 0f 8d |.._.^.D.........|

000002c0 5f 54 0a d2 44 21 00 23 d3 0f d4 0f d2 0f 5f 5f |_T..D!.#......__|

000002d0 73 0a 72 0a ff ff f0 0f ee 0f 69 09 bb 0a 8b 0a |s.r.......i.....|

000002e0 d6 5e ff ff 69 09 f1 0f f0 0f f6 5e d7 5e d5 5e |.^..i......^.^.^|

000002f0 ff ff f1 0f f2 0f f0 0f f5 5e 8c 0a d6 5c 06 08 |.........^...\..|

00000300 f3 0f f2 0f f4 0f 8c 0a f4 5e d9 4c 73 08 f4 0f |.........^.Ls...|

00000310 f5 0f f3 0f 8d 0a ff ff d8 44 0c 08 fc 0f fd 0f |.........D......|

00000320 fe 0f f2 5e 8f 0a db 44 13 08 fe 0f 64 08 fc 0f |...^...D....d...|

00000330 f3 5e dc 5e da 8c 03 06 64 08 ff 0f db 5e 2a 61 |.^.^....d....^*a|

00000340 dd 44 1a 08 ff 0f 00 10 fc 0f ba 0a 91 0a dc 54 |.D.............T|

00000350 55 08 22 08 14 10 13 10 f8 0c a3 0a 44 5c 30 08 |U.".........D\0.|

00000360 5b 08 13 10 11 10 f1 5e a2 0a e0 44 52 08 11 10 |[......^...DR...|

00000370 16 10 5b 08 b6 0a e1 5e df 4c 2d 07 16 10 17 10 |..[....^.L-.....|

00000380 5b 08 ac 3a e2 5e 6c 03 08 5b 08 17 10 18 10 e1 |[..:.^l..[......|

00000390 5e b4 0a e3 6e 50 10 19 44 05 02 a6 0a 2c 61 e2 |^...nP..D....,a.|

000003a0 5c 06 08 61 08 1d 10 1e 10 c7 65 a7 0a e5 4c 11 |\..a......e...L.|

000003b0 08 1e 10 1f 10 61 08 b2 0a e6 5e e4 54 0f 07 1f |.....a....^.T...|

000003c0 10 20 10 61 08 b1 0a e7 5e 6d 03 21 4c 01 04 20 |. .a....^m.!L.. |

000003d0 10 ef 5e e6 5e e8 5d 06 21 4c 03 04 1b 10 e7 5e |..^.^.].!L.....^|

000003e0 b1 0a a8 54 1a 00 08 61 08 26 10 25 10 ea 5e ad |...T...a.&.%..^.|

000003f0 0a c6 65 ff ff 22 10 26 10 61 08 ae 0a e9 5e ef |..e..".&.a....^.|

00000400

Thanks again for having a look.

there is no C: drive

It might be a different letter like D: or E: Try

d:

dir

if that doesn't work try

e:

dir

If that doesn't work, then check out diskpart and see if you can assign a letter to the proper partition.

It may be worth noting that even when booting from the windows disc and running the repair command prompt, I am still able to view my windows partition with a diskutil list command.

I don't know what this means. Windows has a diskpart command. Mac OS X has a 'diskutil list' command which lists all disk devices and their partitions.

alex-clarks-imac:~ alexclark$ hexdump -C ~/twosectors.bin

Line 50 seems to clearly indicate the format of this partition is not NTFS. It's FAT32. Windows 7 makes it difficult to inadvertently install Windows onto a FAT32 volume because it isn't recommended. They recommend, and Apple explicitly shows how to do this with screen shots in the Boot Camp user guide, how to reformat the partition as NTFS after booting from the Windows installer. Mac OS X's Boot Camp Assistant formats the volume as FAT32, not NTFS. So I'm not sure whether you managed to install Windows 7 on a FAT32 volume, or if something has happened causing it to be formatted as FAT32 recently.

This partition 4, Boot Camp/Windows, does not mount in the Mac OS X Finder at all? What's the result from the command:

mount

I don't know what this means. Windows has a diskpart command. Mac OS X has a 'diskutil list' command which lists all disk devices and their partitions.

My mistake. When I wrote "diskutil list", I was thinking of something else (having used the diskpart command to ensure that the windows partition was marked active while in the repair command prompt).

I'm not sure whether you managed to install Windows 7 on a FAT32 volume, or if something has happened causing it to be formatted as FAT32 recently.

This is very likely to be something that has happened recently that caused it to be formatted as FAT32. I wouldn't put it past myself to make the stupid mistake of inadvertently formatting the partition as FAT32 while attempting to resolve the initial issue. Could there be a potential resolution in formatting the disk as NTFS at this point?

It might be a different letter like D: or E:

I will check this now, albeit with little confidence.

More on the file system.

When entering a drive letter into the command prompt such as e: or f:, I receive the message "The system cannot find the drive specified", as expected. However, when I attempt to change to C:, I get "The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and volume is not corrupted."

Could there be a potential resolution in formatting the disk as NTFS at this point?

Absolutely not. Any changes to the disk at this point increase the chances of irreparable data loss. If you did inadvertently format the partition as FAT32, you're in disaster recovery mode, and that's not so much my area. But for sure you need to top altering the volume if you're going to have a chance at recovering data.

Formatting is almost certainly irreversible data loss, but in particular if it's fomatted with the same file system (different file systems put their structures in different parts of the disk, so the old file system may not have been stepped on, I don't know what areas of the disk FAT32 and NTFS share in common). The file system is the card catalog in a library, and your data are the books. So the books are still on the disk, few might have been overwritten with the formatting, but the card catalog has been obliterated. So finding files on the disk isn't directly possible. You'd need a utility to scan the partition for file format patterns to try and recover what you can. If you have a recent backup it's way easier just to use that. This kind of disaster recovery takes many hours to days or even more.

While it's not the best news, that is definitely good to know. Losing the files on the windows partition is fortunately not too severe a consequence for me since I've got the most important bits backed up. I was mostly hoping to fully recover it so I wouldn't have to use up bandwidth redownloading games/programs to install, however at this point it seems that the easiest thing to do would be to get rid of the damaged partition altogether and start fresh. I'll be getting rid of this computer in about two weeks time anyway.

That being said, would you be able to recommend an effective method of completely getting rid of my severely mangled windows partition in order to prepare my HD for one final go at bootcamp before I retire it?

Short version: I use gdisk. gdisk is known as 'GPT fdisk'.

Long version: I use gdisk because it shows what's really going on, on-disk, rather than the trust being obscured by GUI apps. I trust its ability to create exactly correct GPT (and optionally MBR) partition schemes, thoroughly tested on Mac, Windows and Linux.

While it is a command line program, it uses an interactive mode, meaning it prompts you and helps guide you through various command steps. You can type ? <return> to get a menu of commands. And the online documentation is very thorough about describing each command, the vast majority of which you will not use. Importantly, it doesn't live edit the GPT, only modifying a copy in memory. So you can do crazy things in gdisk, and simply use q <return> or control-C to quit and not change anything on-disk.

You basic three tasks in gdisk are: delete a partition, add a new partition, and then make a hybrid partition. Deleting a partition is straight forward, just make sure you use p <return> to list the GPT and make sure you're choosing the correct partition number to delete before issuing the delete command. Adding a new partition will by default use the first free (and 4K aligned) sector, and all contiguously available free space. If you want to specify something different, you can do that.

Before you try to reinstall Windows, you will need a new hybrid MBR. You can do this in gdisk or if you have 4 or fewer partitions, in rEFIt using gptsync.

Long long version: Back to your original problem, there is no easy or obvious way to resize dual-boot Boot Camp disks (disks that have both Mac OS X and Windows), without a commercial 3rd party tool. The included tools can't be used the way you tried to use them, even though it seems emminently rational to do what you did.

Both JHFS+/X and NTFS resize from the *end* of the volume, not the beginning. So when you shrank your Mac OS X volume, it changed where the Mac OS X volume ended, i.e the end of the volume was brought forward, leaving a free space gap between Mac HD and Windows. When trying to resize NTFS, it can't use free space in front of the volume, only free space after the volume. So to use that free space, you first have to move the entire NTFS volume forward so it starts at the beginning of the free space you created, putting all the free space after the NTFS volume; and then resize it.

It is possible to do an NTFS move+resize with Gparted, which is a linux GUI app, but you're almost certainly better off with a commercial app that can simultaneously resize JHFS+/X, do the NTFS move/resize, set the GPT correctly, and set the MBR correctly, all at once.

Sadly I don't have a product recommendations since I'm not really privy to the nuances among Winclone, iPartition, and CampTune.

And last, and least, I actually don't do native booting of non-Mac OS's on my production computer. I only use VM's. On a separate "R&D" Mac, I native boot anywhere from 2 to 8 OS's with fairly crazy partition and bootloader schemes.

Hi Christopher Murphy, Thank you for your kindness.

I had same problem Scotch_Brawth has, and I solved with your solution. 🙂

(One of difference is I'm using Windows 8, but I think that it isn't important to solve this problem.)

Unfortunatly, I have a new problem.

I can't access the middle(?) partition named "Internal Storage" when I'm using Windows.

It's Disk Manager presents to me just two partitions unknown partition and Bootcamp partition.

Can I solve this problem?

There isn't enough information to answer your question. I need to see the GPT and the MBR.

sudo gpt -r -vv show disk0

sudo fdisk /dev/disk0

This is my results. Thx. 🙂

1. result of sudo gpt -r -vv show disk0:

gpt show: disk0: mediasize=320072933376; sectorsize=512; blocks=625142448

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 625142447

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

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

99335424 329816832 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

429152256 262144

429414400 195727360 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

625141760 655

625142415 32 Sec GPT table

625142447 1 Sec GPT header

2. result of sudo fdisk /dev/disk0:

Disk: /dev/disk0 geometry: 38913/255/63 [625142448 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 1023 254 63 [ 1 - 429414399] <Unknown ID>

*2: 07 1023 254 63 - 1023 254 63 [ 429414400 - 195727360] 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