oharag Author

Level 1

48 points

Bootcamp/Win 10 corruption - Macbook Pro 2015 is crashing

Here is my scenario:

I've had a Macbook Pro Retina 2015 for a while.
I recently upgraded to Catalina
I decided to give bootcamp a try after wanting to do this for a long time!
So i go through the procedure with a few hickups. I partitioned my exisiting 1 TB SSD to 500/500.
I installed Win 10 on one 500 GB partition.
Everything seemed fine. I could switch between MacOSX and Win 10 without issues (by holding Option Key).
A few days ago I decided to try to install a Printer connected via USB Cable to my Mac. I was having issues so I decided to boot into Win 10 to see if it worked. Win 10 could not see the Printer so I decided to boot back into MacOSX. I think i may have performed a hard shutdown to force a reboot. So by holding Option key I decided to go to MacOSX.
So somehow I believe the win side of things got corrupted. I noticed while on the MacOSX side, after a bit, my mouse would show the spinning beach ball. Then y MacOSX would freeze, and then eventually MacOSX would reboot, and I would get a blue screen of death:
So I have to hold down the power button to reboot. If I do nothing I get booted right into the blue screen of death.
So I have to always hold down the Option key to boot into MacOSX. When in MacOSX I have less than 5 mintues before the spinning ball shows up - then system locks - then crash - then blue screen.
If I hit F1 in Recovery Enviro - nothing happens - if I hit F8 the screen just blinks on/off.
So I figured I would at least try to fix this using Bootcamp Assistant - maybe try to remove my installation of Win 10.
When I launched Bootcamp it only gave me the option to create a new Win Bootdisk. There was nothing in options to remove an existing Win installation.
So I figured I would use Disk Utility and just remove the Win10 Partition. I thought that would fix my woes. Ha - no go. My Mac still thinks there is a Win Partition, I still get booted into Blue Screen of Death on reboot.
QUESTION: How does this happen - if there is no WIn 10 why does it still think there is one?????
So here is my dilemma: I called Apple support. They said no problem we will go through the process of using web install of Catalina while erasing your HD (so a fresh install). So I hold down Option/CMD/R. I get to the Password screen - input my password - spinning ball - nothing - try again and the password input shakes to say wrong password. So Apple support says to select Forgot PW. It then asks for my apple ID and PW - that works - asks for two form identification from my iPhone - then gives me a message that my apple ID does not allow for erase of my Macbook! So Apple support says okay then hold cmd/R and try that. I'm like what the heck is the difference. Well same thing thing happened - I can not erase my Mac and reinstall Catalina.
So I figure I'll create an external MACOSX boot disk (USB) by downloading full install from internet. Well i can never get passed the spinning ball/freeze/crash/bluescreen of death.
So Apple says - go to an authorized Apple dealer since Apple stores are closed. i'm like is this going to cost me money - they say of course. It turns out I got quoted for $125 to force a erase and reinstall of Catalina.
Questions: How did this happen? Why is it so hard to recover from this blue screen of death? Is it too late to fix this issue - or at least allow for my Mac to not shutdown?
I'm disappointed with MacOSX/Bootcamp. Something like this should NEVER happen, and if it did there should be a recovery mode.
I look towards your expert knowledge - PLEASE HELP!
Thanks

MacBook Pro Retina

Posted on Jun 3, 2020 6:44 AM

Similar questions

53 replies

oharag Author

Level 1

48 points

Jun 7, 2020 6:33 PM in response to Loner T

I did manage to format the external MBP SSD using Disk Utility on Mini as follows:

/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.0 TB disk3

Physical Store disk2s2

1: APFS Volume OpusII 737.3 KB disk3s1

Is this what you were looking for or do I still need to run:

diskutil apfs createContainer disk2s2

BTW I can see and mount the SSD on my Mini. I can format using APFS and GUID. Once I try to run CMD+R or use an external Repair Catalina USB drive the volume disapppears.

oharag Author

Level 1

48 points

Jun 7, 2020 6:38 PM in response to oharag

Iran your command and got this:

Geralds-Mini:~ geraldohara$ diskutil apfs createContainer disk2s2

Creating container with disk2s2

Started APFS operation on disk2s2

Creating a new empty APFS Container

Error: -69614: The disk is already in use by APFS

Loner T

Level 9

59,536 points

Jun 8, 2020 5:18 AM in response to oharag

oharag wrote:

Error: -69614: The disk is already in use by APFS

There is no need to reformat it again, since it is already APFS. Are you able to install Catalina on the 2015 MBP disk? If not, we may need to create additional APFS volumes.

oharag Author

Level 1

48 points

Jun 8, 2020 6:38 AM in response to Loner T

Yeah kind of figured this to be the issue. Again - why doesn't Disk Utility - during format - set up the drive to accept Catalina. Conversely - why doesn't Catalina just install and do the work for me?

It sates from your link that during Catalina update - Catalina goes ahead and created both volumes. How would this be any different from an empty SDD HD formatted using DU and APFS?

I was reading up on how to change the Mount Point since I assume / is where OS is installed. There was a bunch of Terminal Commands thrown around. This seems to be WAYYYY too complicated for the average person - and highly unusual for Apple ease of use methodology.

oharag Author

Level 1

48 points

Jun 8, 2020 7:04 AM in response to Loner T

Man I'm trying anything and everything. I figured if I renamed my SSD HD to Macintosh HD my USB Catalina repair disk would work. Not happening. CMD+R - Mavericks - Not Happening. In fact Mavericks requires HD to be formatted in APFS so I can understand why Mavericks doesn't see my SSD HD.

Loner T

Level 9

59,536 points

Jun 8, 2020 8:10 AM in response to oharag

oharag wrote:

Yeah kind of figured this to be the issue. Again - why doesn't Disk Utility - during format - set up the drive to accept Catalina. Conversely - why doesn't Catalina just install and do the work for me?

DU can create individual elements, but the installer knows all the volumes needed.

It sates from your link that during Catalina update - Catalina goes ahead and created both volumes. How would this be any different from an empty SDD HD formatted using DU and APFS?

macOS Catalina upgrades the volumes correctly, but doesn't create them.

I was reading up on how to change the Mount Point since I assume / is where OS is installed. There was a bunch of Terminal Commands thrown around. This seems to be WAYYYY too complicated for the average person - and highly unusual for Apple ease of use methodology.

Indeed, it is. See Can't upgrade to Mojave on iMac with … - Apple Community as an example.

The steps are....

Create the APFS Fusion Container
- diskutil apfs createContainer -main disk0s2 -secondary disk1s2 (please ensure the SSD is first).
Run (assuming disk2 is the Container)
- diskutil apfs addVolume disk2 apfs "Macintosh HD" -reserve 500g
Add additional volumes (assuming disk2 is the container, change as appropriate)
- Preboot - diskutil apfs addVolume disk2 apfs Preboot -role B -reserve 1g
- Recovery - diskutil apfs addVolume disk2 apfs Recovery -role R -reserve 1g
- VM - diskutil apfs addVolume disk2 apfs VM -role V -reserve 1g
Post the output of diskutil apfs list before we go further. The role value must be uppercase.
This is the Mojave layout. Catalina will upgrade it to match the layout on your Mini.

oharag Author

Level 1

48 points

Jun 8, 2020 9:44 AM in response to Loner T

I will try this, but I want to clarify a few things.

My MBP is a 2015 version. First MacOS version for this MBP was Mavericks. Mavericks requires HD to be formatted as:

Mac OS Extended (Journaled)

So I just got of the phone with Apple Support. The had me hold cmd+r for local recovery. Mavericks pops up (now that I know how Apple performs recovery I think it's bizarre to go all the way back to Mavericks). So I see my SSD in Disk Utility. The Apple Rep said to rename the SSD as "untitled" and format using Mac OS Extended (Journaled), and then attempt to install Mavericks. When I get to select HD the SSD does not show up. When I go back to DU the SSD has disappeared. So the Apple Rep asked if I deleted the the NetBoot OS Install, and I said, "No".

I still think this is BSCrazy, and I still don't understand how Apple manages OS's, installs, formatting, etc.. So The Apple Rep told me that something is jacked and that I had to pay $200 to a local service center, to $300 to Apple to have it shipped out and fixed. I still don't know how I managed to screw up my MBP.Apple Reps says they has SPECIAL ways to install MacOS. I'm frustrated that this isn't a ton simpler than it has been.

Loner T I think we've come a long way, and I TRULY appreciate your tireless help, but knowing the above info - do you think I can use the commands you posted to fix a Mavericks MBP. Especially since Mavericks requires MAC OS Extended? Your link states Mojave. Do the same commands work for a Mavericks system?

Loner T

Level 9

59,536 points

Jun 8, 2020 11:10 AM in response to oharag

I do not think you are getting the right information. See How to reinstall macOS from macOS Recovery - Apple Support for reference. Notice the three different key-sequences and what each one allows.

If your 2015 MBP can boot into Recovery using the correct key combination, you will get the correct macOS version. In Target Disk Mode, the 2012 Mini is providing the Recovery behavior, because it has no way of telling the Apple Recovery servers about the 2015 MBP. The 2015 MBP should have come with El Capitan (10.11.x or Yosemite 10.10.x) at the earliest, rather than Mavericks (10.9.x).

oharag Author

Level 1

48 points

Jun 8, 2020 12:12 PM in response to Loner T

If I hold cmd+r i get Mavericks boot up. I decided to format using Mac OS Extended (Journaled) and GUID Partition.

I rebooted holding shift+option+cmd+r.

Mavericks came up. What was strange I almost got to select the "Untitled" SSD, but it quickly turned into a generic icon, and gave me this error:

I'm just fed up by now. I'm trueing everything at this - especially with your help. Should I just pay the $200? I'm mean this is getting ridiculous.

Loner T

Level 9

59,536 points

Jun 8, 2020 2:02 PM in response to oharag

You have a single-disk in 2015 MBP, so there is no Main or Secondary. You only have a Main disk, which is already APFS.

Using what you already have, you can make the volumes as

Run
- diskutil apfs addVolume disk3 apfs "Macintosh HD" -reserve 500g
Add additional volumes (assuming disk3 is the container, change as appropriate)
- Preboot - diskutil apfs addVolume disk3 apfs Preboot -role B -reserve 1g
- Recovery - diskutil apfs addVolume disk3 apfs Recovery -role R -reserve 1g
- VM - diskutil apfs addVolume disk3 apfs VM -role V -reserve 1g
Post the output of diskutil apfs list before we go further. The role value must be uppercase.

Also, since the Mini is already running Catalina, if you boot into Command+R on the Mini, and then use it to click on Re-install macOS, you can install Catalina on the MBP 2015 Target Disk, as long as you have the volumes created.

oharag Author

Level 1

48 points

Jun 8, 2020 2:17 PM in response to Loner T

Ok things seems to work with our failure - though when I performed the format APFS I named the HD "Untitled". I thought this would go away during your commands. Instead I have both Macintosh HD and Untitled:

It seems like your Preboot, VM and Recovery partitions (?) were created as you expected.

How do I get rid of Untitled?

Here is diskutil list readout:

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 1000.0 GB disk0s2

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1000.0 GB disk1

Physical Store disk0s2

1: APFS Volume OpusIII - Data 102.1 GB disk1s1

2: APFS Volume Preboot 81.0 MB disk1s2

3: APFS Volume Recovery 528.5 MB disk1s3

4: APFS Volume VM 4.3 GB disk1s4

5: APFS Volume OpusIII 11.0 GB disk1s5

/dev/disk2 (external):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 1.0 TB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_APFS Container disk3 1.0 TB disk2s2

/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.0 TB disk3

Physical Store disk2s2

1: APFS Volume Untitled 745.5 KB disk3s1

2: APFS Volume Macintosh HD 500.0 GB disk3s2

3: APFS Volume Preboot 1.0 GB disk3s3

4: APFS Volume Recovery 1.0 GB disk3s4

5: APFS Volume VM 1.0 GB disk3s5

oharag Author

Level 1

48 points

Jun 8, 2020 2:27 PM in response to oharag

Of course I got impatient and deleted APFS Volume "Untitled". In doing so I think i messed up some of your partitions. So I deleted all APFS Volumes and started over with your commands. The Macintosh HD Volume was created without an error. here is output for error:

Geralds-Mini:~ geraldohara$ diskutil apfs addVolume disk3 apfs Preboot -role B -reserve 1g

Will export new APFS Volume "Preboot" from APFS Container Reference disk3 with a 1000000000-byte reserve

Started APFS operation on disk3

Preparing to add APFS Volume to APFS Container disk3

Creating APFS Volume

Error: -69624: Unable to add a new APFS Volume to an APFS Container

It worked initially.

oharag Author

Level 1

48 points

Jun 8, 2020 2:31 PM in response to oharag

Or maybe it worked:

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 1000.0 GB disk0s2

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1000.0 GB disk1

Physical Store disk0s2

1: APFS Volume OpusIII - Data 102.2 GB disk1s1

2: APFS Volume Preboot 81.0 MB disk1s2

3: APFS Volume Recovery 528.5 MB disk1s3

4: APFS Volume VM 4.3 GB disk1s4

5: APFS Volume OpusIII 11.0 GB disk1s5

/dev/disk2 (external):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 1.0 TB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_APFS Container disk3 1.0 TB disk2s2

/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.0 TB disk3

Physical Store disk2s2

1: APFS Volume Preboot 1.0 GB disk3s3

2: APFS Volume Recovery 1.0 GB disk3s4

3: APFS Volume VM 1.0 GB disk3s5

4: APFS Volume Macintosh HD 500.0 GB disk3s1

oharag Author

Level 1

48 points

Jun 8, 2020 4:40 PM in response to Loner T

Please clarify. You want me to disconnect MBP then try booting using CMD+R? Or are you saying I can boot directly from SSD. Remember I haven’t installed Catalina yet. do you want me to try to hold down option +cmd+r on mini and try to install Catalina on MBP ssd?

im sorry this is taking so long. I am truly baffled by what happened, how it happened, and why this is so difficult

Loner T

Level 9

59,536 points

Jun 8, 2020 8:09 PM in response to oharag

Boot the Mini in Local Recovery using Command+R.
Click on Re-install macOS.
Choose the 2015 MBP SSD as the destination.
Install Catalina on the MBP internal disk.
Eject the 2015 MBP disk from the Mini.
Reboot 2015 MBP and select Alt/Option and verify that you can boot macOS.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Bootcamp/Win 10 corruption - Macbook Pro 2015 is crashing