Bootcamp startup "missing operating system"

Question

@ Loner TI am using an Apricorn Velocity x2 for the RAID.drives 2 &amp; 3 of disk 0 were used to create the RAID.MacPro:~ jeff$ diskutil list/dev/disk0 (external, physical):   #:                       TYPE NAME                    SIZE       IDENTIFIER   0:      GUID_partition_scheme                        *500.0 GB   disk0   1:                        EFI EFI                     209.7 MB   disk0s1   2:       Microsoft Basic Data WIN                     250.0 GB   disk0s2   3:                  Apple_HFS macOS                   249.1 GB   disk0s3   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4/dev/disk1 (internal, physical):   #:                       TYPE NAME                    SIZE       IDENTIFIER   0:      GUID_partition_scheme                        *128.0 GB   disk1   1:                        EFI EFI                     209.7 MB   disk1s1   2:                  Apple_HFS Mavericks               127.2 GB   disk1s2   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3/dev/disk2 (internal, physical):   #:                       TYPE NAME                    SIZE       IDENTIFIER   0:      GUID_partition_scheme                        *64.0 GB    disk2   1:                        EFI EFI                     209.7 MB   disk2s1   2:                  Apple_HFS ElCap Backup            63.2 GB    disk2s2   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3/dev/disk3 (internal, physical):   #:                       TYPE NAME                    SIZE       IDENTIFIER   0:     Apple_partition_scheme                        *2.0 TB     disk3   1:        Apple_partition_map                         32.3 KB    disk3s1   2:                  Apple_HFS Stash                   2.0 TB     disk3s3/dev/disk4 (internal, physical):   #:                       TYPE NAME                    SIZE       IDENTIFIER   0:     FDisk_partition_scheme                        *500.1 GB   disk4   1:               Windows_NTFS Storage                 500.1 GB   disk4s1MacPro:~ jeff$ diskutil cs listNo CoreStorage logical volume groups foundMacPro:~ jeff$ sudo gpt -vv -r show /dev/disk0Password:gpt show: /dev/disk0: mediasize&#x3D;499950813184; sectorsize&#x3D;512; blocks&#x3D;976466432gpt show: /dev/disk0: Suspicious MBR at sector 0gpt show: /dev/disk0: Pri GPT at sector 1gpt show: /dev/disk0: Sec GPT at sector 976466431      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       2008             411648  488232960      2  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7  488644608  486552248      3  GPT part - 48465300-0000-11AA-AA11-00306543ECAC  975196856    1269536      4  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC  976466392          7          976466399         32         Sec GPT table  976466431          1         Sec GPT headerMacPro:~ jeff$ sudo fdisk /dev/disk0Disk: /dev/disk0    geometry: 60782/255/63 [976466432 sectors]Signature: 0xAA55         Starting       Ending#: id  cyl  hd sec -  cyl  hd sec [     start -       size]------------------------------------------------------------------------1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] &lt;Unknown ID&gt;*2: 0C 1023 254  63 - 1023 254  63 [    411648 -  488232960] Win95 FAT32L3: AF 1023 254  63 - 1023 254  63 [ 488644608 -  486552248] HFS+       4: AB 1023 254  63 - 1023 254  63 [ 975196856 -    1269536] Darwin BootMacPro:~ jeff$Sorry for the lack of column alignment

Loner T · Answer

If you were using disk0s2 and disk0s3 for RAID, it seems to have been broken. Sierra will not handle such a configuration. On a MP, RAID sets are usually physically removed, before any OS X upgrade, and reconnected later. With the Apricorn in the mix, if you try to rebuild the RAID set again on disk0s2/disk0s3, you will lose one or both OSes. Also, a RAID set on the same physical disk may not provide the protection you expect. Can you physically remove the disks which are not needed? To address your issue, we only need disk0.Please post the output of sudo dd if&#x3D;/dev/rdisk0s2 count&#x3D;1 2&gt;/dev/null | hexdump -Csudo dd if&#x3D;/dev/rdisk0s3 count&#x3D;5 2&gt;/dev/null | hexdump -C

Jeff Robertson · Answer

Funny thing, I was contemplating doing a straight "update" to the macOS on my Mac Pro for a while because I have always been a proponent of fresh installs. Since the update went so well on my Mac minis, I wanted to save some time and installed on top of El Capitan. And, it DID go well on the macOS side.So are you saying Sierra does not support this setup I have going forward or it was simply damaged in the update process? I have not heard of a requirement to remove a RAID and reconnect, but then I do not have a common RAID setup. With the Apricorn, the RAID is set in hardware using a real PC and is recognized as a virtual disk by the Mac Pro. That is how I was able to then partition it. I did this strictly for the performance benefit. The drives used are two identical Samsung 250GB SSDs.I believe my RAID volume is fine (confirmed in Disk Utility) and it is just a problem with the Windows partition itself. I was thinking I could apply an MBR fix but wanted to check here first.On the plus side, I have an old WinClone backup of the Windows partition as well as an El Capitan backup if I need to revert but the Winclone dates back to May of this year and I would hate to go back that far. No, I did not backup the Windows side before the update to Sierra.   😟Last login: Sat Nov 19 08:08:24 on consoleMacPro:~ jeff$ sudo dd if&#x3D;/dev/rdisk0s2 count&#x3D;1 2&gt;/dev/null | hexdump -CPassword: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 48 06 00  |........?....H..|00000020  00 00 00 00 80 00 80 00  f8 d7 19 1d 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  f7 dc 84 18 8a a0 e7 6b  |...............k|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.&gt;..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&#x60;.|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  |..............&lt;.|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.|00000200MacPro:~ jeff$ sudo dd if&#x3D;/dev/rdisk0s3 count&#x3D;5 2&gt;/dev/null | hexdump –C00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|*00000400  48 2b 00 04 80 00 20 00  48 46 53 4a 00 00 07 45  |H+.... .HFSJ...E|00000410  d3 63 d4 c4 d4 56 30 d0  00 00 00 00 d3 64 37 34  |.c...V0......d74|00000420  00 07 07 0e 00 01 cc 29  00 00 10 00 03 a0 06 57  |.......).......W|00000430  03 18 20 a9 00 7a 42 3b  00 01 00 00 00 01 00 00  |.. ..zB;........|00000440  00 20 47 08 02 1a f4 46  00 00 00 00 02 20 00 fb  |. G....F..... ..|00000450  00 18 79 04 00 1f 26 24  00 00 00 00 00 00 00 00  |..y...&amp;$........|00000460  00 00 00 00 00 18 79 04  a3 3b 53 c5 c4 22 c3 f2  |......y..;S.."..|00000470  00 00 00 00 00 74 40 00  00 74 40 00 00 00 07 44  |.....t@..t@....D|00000480  00 00 00 01 00 00 07 44  00 00 00 00 00 00 00 00  |.......D........|00000490  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|*000004c0  00 00 00 00 00 80 00 00  00 80 00 00 00 00 08 00  |................|000004d0  00 00 1f 46 00 00 08 00  00 00 00 00 00 00 00 00  |...F............|000004e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|*00000510  00 00 00 00 14 d0 00 00  06 f0 00 00 00 01 4d 00  |..............M.|00000520  00 06 78 46 00 01 4d 00  00 00 00 00 00 00 00 00  |..xF..M.........|00000530  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|*00000560  00 00 00 00 12 60 00 00  09 30 00 00 00 01 26 00  |.....&#x60;...0....&amp;.|00000570  00 00 27 46 00 01 26 00  00 00 00 00 00 00 00 00  |..&#x27;F..&amp;.........|00000580  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|*00000a00MacPro:~ jeff$

Loner T · Answer

If /dev/disk0 is the logical disk shown to the firmware on the MP as a hardware RAID, then OS X will also see it that way. diskutil list does not show the two separate 250G SSDs. Update your MBR and set the WIN disk0s2 to be 0700 rather than 0C00 and test.

Jeff Robertson · Answer

Correct on the RAID.Now how does one do the MBR update?  🙂

Loner T · Answer

Please see Re: bootcamp fails to start after upgrade to macOS Sierra .

Jeff Robertson · Answer

Ahh. I did see that post from you but was not sure if I could apply it to my situation given the order in which my partitions appear. SIP is already disabled. So I can just add apply these SAME commands in fdisk?sudo fdisk -e /dev/disk0psetpid 407flag 4pwy

Jeff Robertson · Answer

Okay, after a little trial and error, I figured out the logic. In my case, I needed to make two changes because my first disk for my RAID volume changed from 0 to 2 (it does this for some strange reason). I then needed to use "setpid 2" instead of 4 because my Windows partition comes before the macOS one. I applied the value change and then printed.It went from being called Win95 FAT32 to HPFS/QNX/AUX. Unfortunately, I received an "Operation not permitted" when I tried to write the change.  😟Maybe I can try the steps again while in the Recovery system.

Loner T · Answer

The &#x27;not permitted&#x27; is usually due to SIP. Can you check SIP? If you have multiple OS X versions which support SIP, you should check using the version you boot from.

Jeff Robertson · Answer

Strange. SIP *was* disabled! I was certain I performed it under the correct system.Anyway, I was able to write the change while in Recovery.But now I get "BOOTMGR is missing" when I try to boot into Windows. Hmm....a message not unfamiliar to me as I support Windows PCs for the most part. You will see this if attempting to boot from a plain formatted drive! Of course, my Windows system is all there. Not sure about the EFI partition though since I do not normally see it.

Loner T · Answer

You will need to use bootrec.exe and most likely will need a chkdsk and fix boot - https://support.microsoft.com/en-us/kb/927392 .

Jeff Robertson · Answer

When I booted into my Windows 7 Pro install CD and clicked on Repair my computer, it automatically scanned my Windows system and reported that it found problems and asked if I wanted to repair them. I clicked yes and it processed for a little while and completed the task successfully!It still boots up with the same BOOTMGR is missing error, though.So, I booted back into the CD, opened the command line and did the manual repair steps:/FixMbr/FixBoot/RebuildBcdEven did the export option. All commands succeeded without error but I *still* get the error on boot!Stubborn problem, eh?

Loner T · Answer

A silly question, but did you run Bootrec.exe on C: or were you in your boot media directory (usually X:)?

Jeff Robertson · Answer

Correct!I just noticed something now, however. The problem may be worse if what it is telling me is true.After RebuildBcd is run, it reports there are 0 Windows installations! And yet, the GUI repair still identifies one.

Loner T · Answer

Before you run /rebuildBCD, run dir/s/p and look for BCD files on C:. Check after you run it to ensure it changed the one on C:. Is your Windows 7 an EFI installation?

Jeff Robertson · Answer

Yes I have an EFI installation and yes, it changed the one in oot to bcd.old.I do not see a new one in that directory though! I think I see what happened. The rebuild command was choosing the c:oot path by default but my Windows system is assigned to D: under this command prompt (again, probably due to how the Mac automatically creates this drive order). C: is my data storage under the repair command prompt.I just copied the BCD file from c:oot to d:oot. NOW it exists in the correct path!It still does not boot! Darn, I thought for sure that would have worked.I can redo the whole process again, making sure my paths are correct. I also noticed that the bcd.old and new BCD file are of two different sizes if that matters.