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

Bug #1847898 reported by Jean-Baptiste Lallement on 2019-10-13
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Undecided
Unassigned
ubiquity (Ubuntu)
Status tracked in Focal
Focal
High
Unassigned

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)

Jean-Baptiste Lallement (jibel) wrote :
Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
tags: added: rls-ee-incoming
description: updated
summary: - System doesn't boot after installation
+ System doesn't boot after installation - Legacy mode / 2 disks
description: updated
description: updated
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847898

tags: added: iso-testing
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 19.10.20

---------------
ubiquity (19.10.20) eoan; urgency=medium

  [ Jean-Baptiste Lallement ]
  * zsys-setup: Force a re-read of the partition table before using the disk
    (LP: #1847748)

  [ Iain Lane ]
  * zsys-setup: Mark packages to kept in the init phase, rather than finalize.
    Finalize runs after ubiquity has removed files from packages which it has
    decided the target system isn't going to need. It's too late for us to try
    to save things then. (LP: #1847898)

  [ Dimitri John Ledkov ]
  * Automatic update of included source packages: partman-auto
    134ubuntu12, partman-base 206ubuntu6 (LP: #1847944)

 -- Dimitri John Ledkov <email address hidden> Mon, 14 Oct 2019 14:31:19 +0100

Changed in ubiquity (Ubuntu):
status: New → Fix Released
Jean-Baptiste Lallement (jibel) wrote :

Reopening, the wrong bug has been closed.

Changed in ubiquity (Ubuntu):
status: Fix Released → Confirmed
description: updated
Adam Conrad (adconrad) wrote :

We reproduced this in eoan, and then went on to also reproduce it in disco, meaning it's not a regression, and therefor not RC for eoan.

It is, however, really bad UX, and I want to make sure we do this better for 20.04.

Dimitri John Ledkov (xnox) wrote :

For future reference qemu reproducer is:

qemu-system-x86_64 -m 4096 -cdrom ./ubuntu-19.04-desktop-amd64.iso -drive file=generic.qcow2,if=none,id=D22 -device nvme,drive=D22,serial=1234 --enable-kvm -smp 2 -drive id=disk,file=generic-uefi-1.qcow2,if=none -device ahci,id=ahci -device ide-drive,drive=disk,bus=ahci.0 -boot menu=on

Dimitri John Ledkov (xnox) wrote :

It appears that we go by alphabetical order for both select_disk option and the bootdev, and never update grub-installer/bootdev to partman-auto/select_disk value post the "choose disk" screen.

tags: added: release-ff-incoming
Iain Lane (laney) on 2019-10-15
tags: added: rls-ff-incoming
removed: release-ff-incoming
Changed in ubiquity (Ubuntu):
status: Confirmed → Triaged
importance: Critical → High
tags: added: id-5da6d435fc0723668fde7f19
tags: added: rls-ee-notfixing
removed: rls-ee-incoming
Changed in ubuntu-release-notes:
status: New → Fix Released
oldfred (oldfred) wrote :

Related bugs:

Ubuntu Installer uses wrong bootloader location for USB/sdb UEFI installs
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457
Posted work around to manually unmount & mount correct ESP during install
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229488
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1229488
EFI doesn't show multiple installs of the same operating system
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1561712

tags: removed: rls-ff-incoming
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints