Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Cannot boot from Bootcamp

Hi all,

I have recently replaced my old hard drive for a SSD. In my old drive I have one partition with OS X Yosemite and another with Bootcamp. Since the new drive has less capacity than the old drive, I decided to clone the partitions instead of cloning the whole drive and since then, I cannot boot from the bootcamp partition.


I understand where the problem is. Since the whole drive was not cloned, the MBR was not copied from the old drive to the new one (please, somebody correct me if I'm wrong). What I am trying to do now, is to fix the issue. Here is all the information I believe it is relevant:

  • I can see the Bootcamp partition in Finder and access the files.
  • Bootcamp appears as an option in System Preferences -> Startup Disk. However, when I select it and Reboot and black screen with a blinking cursor it is all that appears but Windows actually never boots.
  • Bootcamp does not appear as an option when rebooting and pressing option.
  • If I connect my old drive (via a USB case) and reboot pressing the option key, the Bootcamp partition there appears as an option to boot.
  • I have followed the steps depicted here but it didn't work.


Attached, some outputs of fdisk and diskutils

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 SAMSUNG MAC             429.5 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                50.0 GB    disk0s4
MBP-de-Juanjo:~ jjramos$ diskutil cs list
No CoreStorage logical volume groups found
MBP-de-Juanjo:~ jjramos$ 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  838836408      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  839246048    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  840515584   97652736      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  938168320   38604815         
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header
MBP-de-Juanjo:~ jjramos$ 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    0   0   2 - 1023 254  63 [         1 -  840515583] <Unknown ID>
*2: 07 1023 254  63 - 1023 254  63 [ 840515584 -   97652736] 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


I would really appreciate any help regarding this.


Thanks.

MacBook Pro, OS X Yosemite (10.10.1)

Posted on Jan 21, 2015 12:06 AM

Reply
14 replies

Jan 21, 2015 3:52 AM in response to jjramos.developer

1. How was the partition cloned?

2. The MBR has two entries, one which has everything upto the BC part, and second is the Windows part. This should work, even though this is a non-standard MBR.

3. Can you post the output of sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C?

4. Have you tried Startup Repair?

5. Does your old disk Windows installation boot properly? Have you compared the MBR on that disk with the new one?

Jan 21, 2015 1:07 PM in response to Loner T

Thanks Looner for your reply

Loner T wrote:


1. How was the partition cloned?

Using Disk Utility


2. The MBR has two entries, one which has everything upto the BC part, and second is the Windows part. This should work, even though this is a non-standard MBR.

3. Can you post the output of sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C?


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 50 82 51 |........?....P.Q|

00000020 00 00 00 00 80 00 80 00 ff 0f d2 05 00 00 00 00 |................|

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 b8 af 32 46 c9 32 46 90 |..........2F.2F.|

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


4. Have you tried Startup Repair?


What do you exactly mean by that? If it is Recovery Mode, I could not find anything useful there?


5. Does your old disk Windows installation boot properly? Have you compared the MBR on that disk with the new one?


The Windows disk starts properly, yes. These are the outputs of got and fdisk for the old drive. I cannot find anything meaningful here I'm afraid.


sudo gpt -vv -r show /dev/disk1

gpt show: /dev/disk1: mediasize=750156374016; sectorsize=512; blocks=1465149168

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

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

gpt show: /dev/disk1: Sec GPT at sector 1465149167

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

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

782929176 584565480

1367494656 97652736 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1465147392 1743

1465149135 32 Sec GPT table

1465149167 1 Sec GPT header


MBP-de-Juanjo:~ jjramos$ sudo fdisk /dev/disk1

Disk: /dev/disk1 geometry: 91201/255/63 [1465149168 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 - 781250000] HFS+

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

*4: 07 1023 254 63 - 1023 254 63 [1367494656 - 97652736] HPFS/QNX/AUX


Thanks a lot.

Jan 25, 2015 3:59 AM in response to Loner T

Hi Loner,

Thanks so much for helping with this. I installed and run Testdisk and this is the output it generates:

TestDisk 7.0-WIP, Data Recovery Utility, January 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/disk0 - 500 GB / 465 GiB - 976773168 sectors (RO)

Current partition structure:

Partition Start End Size in sectors


1 P EFI System 40 409639 409600 [EFI System Partitio

2 P Mac HFS 409640 839246047 838836408 [SAMSUNG]

3 P Mac Boot 839246048 840515583 1269536 [Recovery HD]

Warning: number of heads/cylinder mismatches 255 (NTFS) != 1 (HD)

Warning: number of sectors per track mismatches 63 (NTFS) != 1 (HD)

4 P MS Data 840515584 938168319 97652736 [WINDOWS]


Obviously that warning indicates something is wrong but I really don't know what it is.


Thanks a lot.

Jan 25, 2015 9:26 AM in response to jjramos.developer

I am having a similar problem - when I press and hold the Option key on my Macbook Pro, nothing happens, screen stays blank. Normally, a screen appears that shows the different drive options, and I would select the windows drive to go to Windows. Similarly, when I select the Bootcamp disk in Start-up disk under System preferences, nothing happens. I can still see the bootcamp disk when I am in Mac mode and see all the files, but something has happened that is preventing Bootcamp from loading up. I would be very appreciative if there are any simple suggestions.

Jan 25, 2015 3:36 PM in response to Loner T

TestDisk 7.0-WIP, Data Recovery Utility, January 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/disk0 - 500 GB / 465 GiB - 976773168 sectors (RO)

Partition Start End Size in sectors

P EFI System 40 409639 409600 [EFI]

D Mac HFS 409640 839246047 838836408

>D MS Data 742862849 840515584 97652736

D Mac HFS 839246048 840515583 1269536

D MS Data 840515584 938168319 97652736


TestDisk 7.0-WIP, Data Recovery Utility, January 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/disk0 - 500 GB / 465 GiB - 976773168 sectors (RO)


Partition Start End Size in sectors


1 P EFI System 40 409639 409600 [EFI]


TestDisk 7.0-WIP, Data Recovery Utility, January 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/disk0 - 500 GB / 465 GiB - 976773168 sectors (RO)


The harddisk (500 GB / 465 GiB) seems too small! (< 1467 GB / 1366 GiB)

Check the harddisk size: HD jumpers settings, BIOS detection...


The following partitions can't be recovered:

Partition Start End Size in sectors

> Mac HFS 518200 1366331903 1365813704

Mac HFS 518576 1366332279 1365813704

Mac HFS 519272 1366332975 1365813704

Mac HFS 519688 1366333391 1365813704

Mac HFS 520888 1366334591 1365813704

Mac HFS 521304 1366335007 1365813704

Mac HFS 521632 1366335335 1365813704

Mac HFS 521848 1366335551 1365813704

Mac HFS 522128 1366335831 1365813704

Mac HFS 522488 1366336191 1365813704

Mac HFS 522776 1366336479 1365813704

Mac HFS 523200 1366336903 1365813704

Mac HFS 523888 1366337591 1365813704

Mac HFS 524224 1366337927 1365813704

Mac HFS 524448 1366338151 1365813704

Mac HFS 525368 1366339071 1365813704

Mac HFS 526000 1366339703 1365813704

Mac HFS 527456 1366341159 1365813704

Mac HFS 528136 1366341839 1365813704

> Mac HFS 529408 1366343111 1365813704

Mac HFS 530632 1366344335 1365813704

Mac HFS 530888 1366344591 1365813704

Mac HFS 533088 1366346791 1365813704

Mac HFS 533440 1366347143 1365813704

Mac HFS 534128 1366347831 1365813704

Mac HFS 535152 1366348855 1365813704

Mac HFS 539064 1366352767 1365813704

Mac HFS 547224 1366360927 1365813704

Mac HFS 558288 1366371991 1365813704

> Mac HFS 2833335 1911929784 1909096450

Mac HFS 74450007 1983546456 1909096450

Mac HFS 304694225 2865579219 2560884995

Mac HFS 704966919 2614063368 1909096450

Mac HFS 744507238 1487325287 742818050

Mac HFS 744507301 1487325350 742818050

Mac HFS 801190884 1601972131 800781248

Mac HFS 839246044 1678082451 838836408

Mac HFS 840253380 1680097123 839843744

> MS Data 921633952 1019286687 97652736

This is what I get when select the MS Data partition.

Thanks again.

Jan 28, 2015 12:26 AM in response to Loner T

Hi Loner,

I was going through all the steps in order to do what you suggested in your previous reply and after the first scan of TEstdisk the output is this one:

Disk /dev/disk0 - 500 GB / 465 GiB - 976773168 sectors (RO)

Partition Start End Size in sectors

P EFI System 40 409639 409600 [EFI]

D Mac HFS 409640 839246047 838836408

D MS Data 742862849 840515584 97652736

D Mac HFS 839246048 840515583 1269536

>D MS Data 840515584 938168319 97652736


Where now there are to MS Data partitions with the exact same size and the first one overlaps with the 2 Mac HFS partitions whereas the last MS Data partitions is consecutive with the last Mac HFS. Is that an indication of something? Should I delete the first MS Data partition?


I will post the results of the Deep Analysis of that one as soon as it finishes.


Thanks.

Jan 28, 2015 12:05 PM in response to Loner T

This is what I got:


TestDisk 7.0-WIP, Data Recovery Utility, January 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

4 P MS Data 840515584 938168319 97652736 [WINDOWS]

Directory /


>dr-xr-xr-x 0 0 0 3-Nov-2014 20:52 .

dr-xr-xr-x 0 0 0 3-Nov-2014 20:52 ..

dr-xr-xr-x 0 0 0 21-Apr-2013 00:09 $Recycle.Bin

dr-xr-xr-x 0 0 0 1-May-2013 17:14 .TemporaryItems

dr-xr-xr-x 0 0 0 30-Apr-2013 23:10 .Trashes

dr-xr-xr-x 0 0 0 8-Dec-2013 10:22 .fseventsd

dr-xr-xr-x 0 0 0 23-Jan-2015 16:07 Boot

dr-xr-xr-x 0 0 0 21-Apr-2013 00:07 Intel

dr-xr-xr-x 0 0 0 21-Apr-2013 18:11 MSOCache

dr-xr-xr-x 0 0 0 14-Jul-2009 04:20 PerfLogs

dr-xr-xr-x 0 0 0 20-Jul-2014 12:50 Program Files

dr-xr-xr-x 0 0 0 3-Nov-2014 20:47 Program Files (x86)

dr-xr-xr-x 0 0 0 20-Jul-2014 12:50 ProgramData

dr-xr-xr-x 0 0 0 21-Apr-2013 00:00 Recovery

dr-xr-xr-x 0 0 0 21-Oct-2014 22:00 System Volume Information

dr-xr-xr-x 0 0 0 7-Jul-2013 10:21 Users

dr-xr-xr-x 0 0 0 21-Oct-2014 22:00 Windows

-r--r--r-- 0 0 6148 15-Oct-2013 22:58 .DS_Store

-r--r--r-- 0 0 4096 22-Apr-2013 21:59 ._.DS_Store

-r--r--r-- 0 0 4096 1-May-2013 17:14 ._.TemporaryItems

-r--r--r-- 0 0 4096 21-Apr-2013 22:57 ._.Trashes

-r--r--r-- 0 0 294 4-Jun-2013 22:29 .apdisk

-r--r--r-- 0 0 8192 21-Apr-2013 08:51 BOOTSECT.BAK

-r--r--r-- 0 0 2062 21-Apr-2013 00:05 RHDSetup.log

-r--r--r-- 0 0 383786 21-Nov-2010 03:24 bootmgr

-r--r--r-- 0 0 6369075200 3-Nov-2014 19:22 hiberfil.sys

-r--r--r-- 0 0 8492101632 3-Nov-2014 19:22 pagefile.sys

Jan 28, 2015 12:31 PM in response to jjramos.developer

This is a bit puzzling. Your Testdisk output is

4 P MS Data 840515584 938168319 97652736 [WINDOWS]

Your GPT4 entry on line 25 of the OP is

840515584 97652736 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7


These are exactly identical. One suggestion would to be to recreate the Hybrid MBR using GPT Fdisk using the following steps and then run Windows Startup Repair using the Windows Installation Media.


Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (Press Return/Enter for questions similar to Enter an MBR hex code (default AF):). The only changes that are being made are to boot ability flags.


  1. Sudo gdisk /dev/disk0
  2. P (Print list of parts)
  3. R (Recover)
  4. H (chooses Hybrid)
  5. Partitions numbers to be hybridized: 2 3 4
  6. Y (Good for GRUB question)
  7. N (part 2 boot flag)
  8. N (part 3 boot flag)
  9. Y (part 4 boot flag make NTFS bootable partition)
  10. W (Write the new MBR)
  11. Y (Yes! write the new MBR)
  12. Reboot

Cannot boot from Bootcamp

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.