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

Bootcamp Partition not bootable after adding new partition disk utility

Dear support team, I only add a new partition in Mac OS, and didn't touch the bootcamp partition at all. but now I can't start the bootcamp.

this is what I have tried so far:

  • update the OS to macOS Sierra 10.12.6
  • Bootcamp assistant is already version 6, but has no other option but to remove the bootcamp drive.
  • I try to update the MBR with below step:
    • disk -e /dev/disk0
    • setpid 4
    • 07
    • flag 4
    • write

But this doesn't work. but the bootcamp partition is working find in MacOS and can see all the files well.

when I restart and press alt, I can see 2 boot option (macOS and windows), but the windows is just showing black screen. not even the initial windows logo)


I check all the other similar Q&A (https://discussions.apple.com/thread/8293181 and https://discussions.apple.com/thread/251214564 and few others. but this 2 suggest different steps: gdisk or parted. I am not sure with my specific cases what is the right step.


MacBook Pro with Touch Bar

Posted on Jun 26, 2020 7:12 AM

Reply
Question marked as Best reply

Posted on Jul 6, 2020 2:51 PM

Run (do not type text like this)


sudo gdisk /dev/disk0

p (print the GPT)

x (Expert mode)

n (new Protective MBR)

o (print the Protective MBR)

p (print the GPT)

w (write)

y (confirm write)


Reboot and test.


Similar questions

15 replies

Jul 2, 2020 5:44 AM in response to Loner T

Hi Loner,

yes, i've tried to execute the 2 command with N (from 1 till 6), it still didn't provide output. but kind of suggest there is no disk N=2 or 3 onward.


but i still can't find way to be able to run these 2 command from the normal MacOS mode.

sudo gpt -vv -r show /dev/diskN

sudo disk /dev/diskN


this is what message it gave:

Last login: Thu Jul 2 19:17:25 on console

The default interactive shell is now zsh.

To update your account to use zsh, please run `chsh -s /bin/zsh`.

For more details, please visit https://support.apple.com/kb/HT208050.

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r /dev/disk0

Password:

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk0

gpt show: unable to open device '/dev/disk0': Operation not permitted

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk1

gpt show: unable to open device '/dev/disk1': Operation not permitted

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk2

gpt show: unable to open device '/dev/disk2': No such file or directory

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk3

gpt show: unable to open device '/dev/disk3': No such file or directory

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk4

gpt show: unable to open device '/dev/disk4': No such file or directory

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk5

gpt show: unable to open device '/dev/disk5': No such file or directory

asido-MacBook-Pro:~ asido$ sudo gpt -vv -r show /dev/disk6

gpt show: unable to open device '/dev/disk6': No such file or directory

asido-MacBook-Pro:~ asido$ sudo disk /dev/disk0

sudo: disk: command not found

asido-MacBook-Pro:~ asido$ sudo disk /dev/disk1

sudo: disk: command not found

asido-MacBook-Pro:~ asido$ sudo disk /dev/disk2

sudo: disk: command not found

asido-MacBook-Pro:~ asido$ sudo disk /dev/disk3

sudo: disk: command not found

asido-MacBook-Pro:~ asido$ sudo fdisk /dev/disk0

fdisk: /dev/disk0: Operation not permitted

asido-MacBook-Pro:~ asido$ sudo fdisk /dev/disk1

fdisk: /dev/disk1: Operation not permitted

asido-MacBook-Pro:~ asido$ sudo fdisk /dev/disk2

fdisk: /dev/disk2: No such file or directory

asido-MacBook-Pro:~ asido$ 

Jun 28, 2020 4:11 AM in response to Loner T

Hi Loner T, thanks for responding.


My mac is MacBook Pro 13-inch 2016 (with digital touch panel).


I've added those detail in my earlier msg (but as attached additional text, so maybe not readily visible.) BUT, i've actually did one more step since the last msg, i upgrade the OS from MacOS Sierra to MacOS Catalina 10.15.5. So, i put again below the latest output of those command. i can only run the first command in MacOS terminal. the remaining 2 i can only run it from recovery mode (and since i have another issue my main screen is dead, i am using external screen, i can only manage to run and take picture).


$ diskutil list

/dev/disk0 (internal, physical):

  #:             TYPE NAME           SIZE    IDENTIFIER

  0:   GUID_partition_scheme             *500.3 GB  disk0

  1:             EFI EFI            314.6 MB  disk0s1

  2:     Apple_APFS Container disk1      300.0 GB  disk0s2

  3:     Microsoft Basic Data BOOTCAMP  199.4 GB  disk0s3

  4:       Windows Recovery              545.3 MB  disk0s4


/dev/disk1 (synthesized):

  #:             TYPE NAME           SIZE     IDENTIFIER

  0:    APFS Container Scheme -             +300.0 GB  disk1

                  Physical Store disk0s2

  1:         APFS Volume Macintosh HD - Data   68.6 GB  disk1s1

  2:         APFS Volume Preboot          82.2 MB  disk1s2

  3:         APFS Volume Recovery         528.5 MB  disk1s3

  4:         APFS Volume VM            1.1 GB   disk1s4

  5:         APFS Volume Macintosh HD       11.0 GB  disk1s5


the other 2 command result i could only show in attached picture



Jul 1, 2020 7:00 PM in response to Loner T

Hi Loner,

no, for the first command "diskutil list", i run it on macOS (not in recovery mode). below is the results. (only the other 2 command because i can't run it on macOS normal mode, i run at recovery mode).


are the other 2 command supposed to work also in the normal macOS mode?



below is run on normal macOS mode:

$ diskutil list

/dev/disk0 (internal, physical):

  #:             TYPE NAME           SIZE    IDENTIFIER

  0:   GUID_partition_scheme             *500.3 GB  disk0

  1:             EFI EFI            314.6 MB  disk0s1

  2:     Apple_APFS Container disk1      300.0 GB  disk0s2

  3:     Microsoft Basic Data BOOTCAMP  199.4 GB  disk0s3

  4:       Windows Recovery              545.3 MB  disk0s4


/dev/disk1 (synthesized):

  #:             TYPE NAME           SIZE     IDENTIFIER

  0:    APFS Container Scheme -             +300.0 GB  disk1

                  Physical Store disk0s2

  1:         APFS Volume Macintosh HD - Data   68.6 GB  disk1s1

  2:         APFS Volume Preboot          82.2 MB  disk1s2

  3:         APFS Volume Recovery         528.5 MB  disk1s3

  4:         APFS Volume VM            1.1 GB   disk1s4

  5:         APFS Volume Macintosh HD       11.0 GB  disk1s5



Jul 2, 2020 6:10 AM in response to Loner T

Hi Loner, sorry, now i manage to get the output for these 2 command:


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

Password:

gpt show: /dev/disk0: mediasize=500277792768; sectorsize=4096; blocks=122138133

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 122138132

   start     size  index  contents

      0      1      MBR

      1      1      Pri GPT header

      2      4      Pri GPT table

      6    76800    1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

    76806  73244410    2.  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC

   73321216  48683368    3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

 122004584     152     

 122004736    133120    4  GPT part - DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

 122137856     272     

  122138128      4      Sec GPT table

  122138132      1      Sec GPT header


$ sudo gpt -vv -r show /dev/disk1

Password:

gpt show: unable to open device '/dev/disk1': Resource busy

$ sudo gpt -vv -r show /dev/disk2

gpt show: unable to open device '/dev/disk2': No such file or directory


$ sudo disk /dev/disk1

sudo: disk: command not found

$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 7602/255/63 [122138133 sectors]

Sector size: 4096 bytes

Signature: 0xAA55

     Starting    Ending

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

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

 1: EE 1023 254 63 - 1023 254 63 [     1 -   76805] <Unknown ID>

 2: FF 1023 254 63 - 1023 254 63 [   76806 -  73244410] Xenix BBT  

*3: 0C 1023 254 63 - 1023 254 63 [ 73321216 -  48683368] Win95 FAT32L

 4: FF 1023 254 63 - 1023 254 63 [ 122004736 -   133120] Xenix BBT  

$ sudo fdisk /dev/disk1

fdisk: /dev/disk1: Resource busy

Jul 3, 2020 8:24 AM in response to asidos

On a 2015 or later Mac, you cannot use a MBR, since legacy BIOS mode of Windows is no longer supported. You have a


My mac is MacBook Pro 13-inch 2016 (with digital touch panel).


You will need to remove the MBR using GPT Fdisk. You also have a WinRE partition. Are you able to see Windows files in macOS Finder?

Jul 6, 2020 3:29 AM in response to Loner T

Hi Loner, i see.

Do you have the steps in some previous thread i could follow to do this MBR remove with GPT Fdisk? anything I need to do in regards to the WinRE partition?


yes, i can perfectly see all the windows files in BOOTCAMP partition in MacOS with Finder. had tried copy some of them to macOS folder and open.

Bootcamp Partition not bootable after adding new partition disk utility

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