[Bug 1591352] Re: Ubiquity copies efi boot information to wrong ESP

[Maxim]

*** This bug is a duplicate of bug 1396379 ***
    https://bugs.launchpad.net/bugs/1396379

I have a laptop with 2 SSDs and want to install Windows and Ubuntu separately.
Windows is installed on the first SSD and runs well.
Now I need to install Ubuntu on second SSD.
Every time I try to install it: Ubuntu installs GRUB to the first disk, to existing EFI partition alongside Windows bootloader. I tried all possible disk choosing options, and it still uses existing ESP. And, yep, it broke my Windows bootloader.

Please pay attention to this bug, it's ancient!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1591352

Title:
  Ubiquity copies efi boot information to wrong ESP

Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  I'm installing Ubuntu 16.04 onto an external HDD. My computer also has
  an internal Windows 10 HDD.

  When at the partitioning stage, it selected for the boot loader to be
  installed onto the external HDD.

  When Uniquity is installing the system, it mounts Windows 10's ESP and
  copies the Ubuntu/grub boot loaders over, when it should have mounted
  the ESP created on the external HDD. I attached a screenshot of lsblk
  to show what's happening. /dev/sda2 is the Win10 ESP and it's mounted
  to /target/boot/efi. /dev/sdb1 is the correct ESP but is not touched.

  Because the boot information is not on the external HDD, the Windows
  10 disk must be present to boot Ubuntu because the boot information
  pointing to Ubuntu is located on the Windows ESP.

  Ubiquity is version 2.21.63.

  I also attached the Ubiquity debug file, partman, and syslog. Sorry
  for putting them in a zip, can't attach more than 1 file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1591352/+subscriptions