2

Not a duplicate - this is a new, sub-question regarding the steps in the answer here: https://apple.stackexchange.com/a/375863/4018

I followed the steps in that question, however, after completing them, selecting the Windows drive on the standard mac boot menu no longer works, what happens is that the screen goes blank and it never boots into Windows.

Also, there is not option shown in the apple boot manager for Ubuntu - video to follow.

Possible lead to explore: instead of step 6 using mv Linux command to rename the Windows EFI folders - to stop GRUB altering it, make a copy - cp -R EFI EFI.win, for later to restore back at end of steps, instead. My theory is that macOS bootmanager doesn't find Windows on a subsequent reboot after I did step 6, it adjusts itself to ignore it. By having the original there, it wont do that - AND - at the end we can restore the copy, overwriting what GRUB did. I haven't tried this yet. I also haven't tried bootrec yet.

I don't know how, yet, to solve the other problem whereby the option for booting into Ubuntu is not shown in the Apple boot manager.

Machine: 2016 MacBookPro 15" touchbar, 2.9GHz Quad-Core Intel i7, AMD 4g graphics, 16Gb RAM, 1Tb SSD.

Running: macOS Catalina 10.15.2

Windows 10 Pro 64bit installed OK with BootCamp

Attempting to install 3rd operating system, Ubuntu 18.04.3 LTS 64bit, to be an option along side macOS and Windows in the standard Apple Boot Manager boot selection screen. DO NOT want to use reFind.

Here are my screenshots of some of the key steps I followed in that answer (from above):

Differences in my setup:

  • that my partition name identifiers are different from the original question, but I believe I've worked out the equivalents for my case

  • My Bootcamp Windows has only one (1) partition, unlike the (answer mentioned above) which has three partitions.

Screenshots from step 6

step 06 step 06 step 06 step 06 step 06 step 06

steps 08-13

steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13 steps 08-13

steps 15,16

steps 15,16 steps 15,16 steps 15,16

Step 16

step 16

Step 17

step 17

2
  • In the end, I stuck with dual boot macOS and Windows. I'm so appreciative of the efforts of folks to get a triple boot setup. The reason I abandoned this is because it necessarily had a lot of steps to go through as well as drivers to install for trackpad/touchpad etc, alpha at time. Also WSL2 works well for Linux on Windows - officially supported and ddev for php (Drupal) development. WSL2 seems to perform as well as, if not better in terms of speed on Windows, compare with using docker on mac. YMMV. I wanted to develop rather than develop my development environment. Dec 10, 2021 at 10:16
  • See my comment about a new development whereby Linux can be installed on the NTFS filesystem, potential to simplify "triple" boot: apple.stackexchange.com/questions/378754/… Dec 10, 2021 at 10:47

1 Answer 1

1

Possible Reason Windows Will Not Boot

The Ubuntu 18.04.3 LTS 64 bit installation software changes the Master Boot Record (MBR) partition table on the installation drive to cause hybrid partitioning. This would prevent Windows from booting on 2016 model year Macs. In 2012, Apple started to phase out the need for hybrid partitioning. Evidently, the Ubuntu installer does not check for this. The answer you reference has been changed to add a step where gdisk is used to remove any hybrid partitioning imposed by the Ubuntu installer on the installation drive.

You can also remove the hybrid partitioning by booting to the live version of Ubuntu from the installer flash drive. The steps are given below.

  1. Download the latest Ubuntu installation ISO file from the Ubuntu Home Page. The file download and used in this answer was named ubuntu-18.04.3-desktop-amd64.iso.

  2. Use Etcher to create a bootable Ubuntu flash drive installer, then boot from this flash drive. A tutorial can be found at the Ubuntu website Create a bootable USB stick on macOS.

  3. When the menu below appears, select Try Ubuntu without installing.

  4. When the Ubuntu desktop appears, press the control+option+T key combination to open a terminal window.

  5. Make sure the drive is not using hybrid partitioning. This can be accomplished by entering the command given below.

    sudo gdisk /dev/nvme0n1p
    

    This command is interactive. The interactive commands you will need to enter when prompted by gdisk are given below.

    x
    n
    w
    y
    
  6. Finally, enter the command exit to close the terminal window.

Possible Reason Ubuntu Will Not Boot

Below is a copy of an image you posted as part of your question with respect to steps 15 and 16.

The image shows the following message.

Warning: Filesystem is FAT32 according to fat_length and fat32_length fields,
  but has only 51068 clusters, less than the required minimum of 65525.
  This may lead to problems on some systems.

This warning occurred because the drive on your Mac has a sector size of 4096 bytes. However, the answer referenced an example Mac with a sector size of only 512 bytes. In other words, the new EFI partition you created was too small. The instructions have been changed so the new EFI partition is at least as large as the original EFI partition. In your case, this should be about 315 MB.

To create a larger new EFI partition, you will have to reinstall Ubuntu.

3
  • +1 thank you very much @David Anderson - I will do these steps and follow up here - hopefully to accept this answer. Jan 2, 2020 at 9:44
  • Following up, I've decided to stick with just macOS and Windows on BootCamp, using WSL2 on Windows for a Linux environment. apple.stackexchange.com/questions/378754/… Thank you for all your help. Dec 10, 2021 at 10:17
  • Interesting to note that one can now install Linux in the same NTFS partition as Windows, because NTFS being supported in Linux kernel and top-level Linux folder names don't clash with Windows ones. theregister.com/2021/11/22/install_linux_on_ntfs This may reduce the steps needed for running Linux with Bootcamp Windows and macOS. Perhaps it could be that in that case we configure the bootmenu option to point at the same partition and give a launch file for it to run. Could be much simpler! Dec 10, 2021 at 10:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .