[Bug 1847898] Re: System doesn't boot after installation - Legacy mode / 2 disks

[Herb Theriault]

My primary nvme drive shows up as sdb. Installing with 2 drives, and the
nvme as sdb fails. Machine will not boot, post install. Pulled the
secondary drive, reinstalled, and it does boot.

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

Title:
  System doesn't boot after installation - Legacy mode / 2 disks

Status in Release Notes for Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubiquity source package in Focal:
  Triaged

Bug description:
  Workaround installing on SATA drive (sda)

  * Click Something Else custom first
  * Change boot loader drop down from nvme to sda
  * Click back
  * Use wipe & install
  * Select sda for install
  * Complete install & reboot

  --

  Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)

  Dell Inspiron 7472 with 2 disks: sata and nvme
  Boot in legacy mode
  System installed on sda

  After installation the system doesn't find a bootable device.
  The same problem occurs if I install Ubuntu on the nvme drive instead.

  If I perform the installation in uefi/no secure boot mode, it boots
  fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubiquity 19.10.19
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.424
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 05:00:22 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash nomodeset ---
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1847898/+subscriptions