[Bug 1809163] Re: Installer tries to put bootloader on install medium when installing from SD card

[Scott]

(Other bug that tracks the "Bootloader install failed" recovery dialog
getting stuck: bug 1809164)

-- 
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/1809163

Title:
  Installer tries to put bootloader on install medium when installing
  from SD card

Status in ubiquity package in Ubuntu:
  New

Bug description:
  When installing ubuntu-18.10-desktop-amd64.iso FROM an SD card ONTO an
  empty SSD using automatic partitioning, the installer chooses the *SD
  card installation medium* as the device to put the bootloader on.  It
  should choose the SSD where the rest of the OS is being installed.


  To reproduce:

  On another Ubuntu system:
  1. Download ubuntu-18.10-desktop-amd64.iso.
  2. Use Startup Disk Creator (usb-creator-common/bionic,now 0.3.5 amd64) to load the installation ISO onto the SD card.
  3. Write-lock the SD card using the slide-switch on the side.

  On the empty computer onto which Ubuntu will be installed:
  4. Boot from the SD card.
  5. Select "Install Ubuntu".
  6. Select "Normal installation".
  7. Select automatic partitioning with encryption: "Erase disk and install Ubuntu" + "Encrypt the new Ubuntu installation for security".
  8. Respond to key, timezone, username, hostname, etc. prompts.  Installation churns for awhile, saying "Copying files...", "Installing system", "Configuring hardware...", etc.

  This is where things go awry.
  * Installation says "Running 'grub-install /dev/mmcblk0'..."
  * An error box comes up:
       Unable to install GRUB in /dev/mmcblk0
       Executing 'grub-install /dev/mmcblk0' failed.
       This is a fatal error.
       [OK]
  * After pressing OK, this dialog appears:
      Bootloader install failed
      (X) Sorry, an error occurred and it was not possible to install the bootloader at the specified location.
      How would you like to proceed?
        (o) Choose a different device to install the bootloader on:
          [/dev/mmcblk0]
        ( ) Continue without a bootloader.
        ( ) Cancel the installation.
      [OK]

  The device selection drop-down has eight choices (including two apparent duplicates):
    /dev/mapper/sda5_crypt          Linux device-mapper (crypt) (255.3 GB)
    /dev/mapper/sda5_crypt
    /dev/mapper/ubuntu--vg-root     Linux device-mapper (linear) (254.3 GB)
    /dev/mapper/ubuntu--vg-root
    /dev/mapper/ubuntu--vg-swap_1
    /dev/sda                        ATA SAMSUNG SSD XXXX (256.1 GB)
    /dev/sda1
    /dev/sda5

  Interestingly, /dev/mmcblk0 does *not* appear as a drop-down option.
  After selecting one of the other options, /dev/mmcblk0 disappears and
  is not presented as an option.


  Installation cannot continue from here because the "Bootloader install
  failed" recovery dialog gets stuck, but that is a separate bug.  This
  bug tracks the problem where automatic partitioning choose the SD card
  (mmcblk0) as the target for bootloader install when it should have
  chosen the SSD onto which Ubuntu was being installed (sda).

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