Q: repairing bootcamp after partition
hi, my bootcamp won't start.
I can see the bootcamp files on finder and also see the bootcamp system on startup disk in system preference of my OS but when ever I choose to restart my computer using window it just says no bootable device found and goes all black.
I recently updated my os to el capitan and deleted unused partition that was taking up space.
I don't know much about computers so if you could help me I will be so grateful!!!!
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 75.9 GB disk0s2
3: Apple_Boot Recovery HD 5.1 GB disk0s3
4: Microsoft Basic Data BOOTCAMP 40.0 GB disk0s4
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *500.1 GB disk1
1: DOS_FAT_32 HANNA 500.1 GB disk1s1
diskutil cs list
No CoreStorage logical volume groups found
sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
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 236978175
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 148163312 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
148572952 10020072 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
158593024 262144
158855168 78120960 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
236976128 2015
236978143 32 Sec GPT table
236978175 1 Sec GPT header
MacBook Air (13-inch Mid 2012), OS X El Capitan (10.11.4)
Posted on Apr 21, 2016 8:15 PM
You have two separate issues.
1. Your Recovery HD is the incorrect size. It is usually 620 MB, but it is now 5.1Gb.
2. Your MBR entry #4 is incorrect. Let us try to fix this first before we solve the other issue.
A. We need to disable SIP (System Integrity Protection).
1. Boot into Local Recovery (Command+R).
2. Start Utilities -> Terminal.
3. Type csrutil disable in Terminal and press Enter/Return.
4. Type csrutil status.
5. Boot normally, and type csrutil status to confirm that all individual entries are still disabled.
B. Correct the MBR. Please ignore the i386 MBR errors, but not any others.
sudo fdisk -e /dev/disk0
p
setpid 4
07
flag 4
p
w
y
Reboot and Test. If It works repeat step A with csrutil enable to re-enable SIP.
Posted on Apr 21, 2016 10:02 PM