-
All replies
-
Helpful answers
-
Nov 13, 2015 10:28 AM in response to Loner Tby doug3684,This is a lot more involved than I expected but I will give it a go. And thank you for this, BIG thank you
Before I go ahead with anything I'm a little unsure about a couple of things. You said "If you have OSX El Capitan, then otherwise skip this part" This Mac runs Lion 10.7.5 Shall I follow your instructions or skip them?
Just for the record atm both Bootcamps show in Finder, files are visible and both show in Startup Disk (but only the new one will boot)
-
Nov 13, 2015 10:47 AM in response to doug3684by Loner T,doug3684 wrote:
Before I go ahead with anything I'm a little unsure about a couple of things. You said "If you have OSX El Capitan, then otherwise skip this part" This Mac runs Lion 10.7.5 Shall I follow your instructions or skip them?
Please skip the ELC part.
Just for the record atm both Bootcamps show in Finder, files are visible and both show in Startup Disk (but only the new one will boot)
Only new one boots because the MBR points to the new one. We are recreating the MBR and marking both as bootable. Make Step 9 also as a 'Y'.
-
Nov 13, 2015 11:14 PM in response to Loner Tby doug3684,When I type in "Sudo gdisk /dev/rdisk0" I get "command not found"
-
Nov 14, 2015 7:19 AM in response to doug3684by doug3684,Okay I got that sorted out and followed your instructions so far
-
Nov 14, 2015 7:37 AM in response to doug3684by doug3684,I missed your instruction to type Y in step 9 but I'm not concerned about that
Both BOOTCAMPs show in Finder and in Startup Disk
Tried restart in Startup Disk
I get the options to start in Safe Mode or Normally but I get a Blue screen with message and quickly restarts
Something else I have noticed (Before and after) in Finder window I am able to Re-Name the BOOTCAMP that I want, but not the other
-
-
-
Nov 14, 2015 10:00 PM in response to Loner Tby doug3684,Its not working whichever way I reboot. I get the Safe Mode choices and regardless which one I choose I get a message on a blue screen that quickly disappears and reboots
-
-
Nov 15, 2015 8:46 AM in response to doug3684by Loner T,Can you try the following (this marks the other Windows installation as bootable as well).
sudo fdisk -e /dev/disk0
p
setpid 3
07
flag 3
p
w
y
Reboot and test the other Windows installation. The unmountable boot volume indicates issues with boot loader. We may need Startup Repair on the broken Windows to fix the BCD and MBR.
-
-
Nov 16, 2015 5:45 AM in response to doug3684by Loner T,We do not need fdisk -c . After a Reboot, can you test for boot ability of either Windows installation?
-
Nov 16, 2015 7:41 AM in response to Loner Tby doug3684,It won't boot into either Windows install, I messed up at - I think it was step 9
-
Nov 18, 2015 1:02 AM in response to doug3684by doug3684,Just wondering is there anything else to try?
If it would involve too much time I will let it go, but I thank you for your help
-
Nov 18, 2015 4:24 AM in response to doug3684by Loner T,You can repeat the Fdisk and Gdisk steps, if you mistyped anything.
Can you post the output of the following commands?
sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C
sudo dd if=/dev/rdisk0s5 count=1 2>/dev/null | hexdump -C
Does Startup Repair on either Windows installation boot up?





