[18.04.4] Live system fails to reboot after installation

Bug #1860559 reported by Jean-Baptiste Lallement on 2020-01-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Critical
Unassigned
Bionic
Critical
Dimitri John Ledkov
linux (Ubuntu)
Critical
Unassigned
Bionic
Critical
Unassigned

Bug Description

bionic desktop 20190122

Since bionic 20191211 the system doesn't reboot after installation.

After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:

[sdb] tag#0 access beyond end of device

(in this context sdb is the USB stick)

20191211 includes a new kernel and a new gcc

This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM.

Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Jean-Baptiste Lallement (jibel) wrote :
summary: - System fail to reboot after installation
+ [18.04.4] System fails to reboot after installation
Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
tags: added: rls-bb-incoming
affects: ubiquity (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu Bionic):
importance: Undecided → Critical
Changed in linux (Ubuntu):
status: New → Fix Released
Changed in linux (Ubuntu Bionic):
milestone: none → ubuntu-18.04.4

Diff of the manifest between last known good image and first broken image.
noticeable packages are gcc-8 and upgrade of linux 5.0 to linux 5.3

description: updated
description: updated
Changed in casper (Ubuntu):
importance: Undecided → Critical
Changed in casper (Ubuntu Bionic):
importance: Undecided → Critical
Changed in casper (Ubuntu):
status: New → Fix Released
Changed in casper (Ubuntu Bionic):
status: New → Confirmed
Changed in linux (Ubuntu Bionic):
status: New → Confirmed
description: updated
description: updated
Steve Langasek (vorlon) on 2020-01-23
tags: removed: rls-bb-incoming
Łukasz Zemczak (sil2100) wrote :

If this is indeed the same issue we saw in LP: #1840122, I think the only sane way to fix this is to proceed in the same way as we did in eoan - adding a finalrd dependency to casper. This would need pulling in finalrd into main, but I guess that was the plan already. Hopefully the MIR review should be fairy quick, as finalrd is the same across as in disco.

Let me reach out to the MIR team about this.

Łukasz Zemczak (sil2100) wrote :

I'm re-using the LP: #1785267 bug for this.

Łukasz Zemczak (sil2100) wrote :

So finalrd is now in main for bionic-updates. The question now is: will we need finalrd to be in bionic-security as well for this? I think we won't, but I guess my brain is a bit fried right now.

On Fri, Jan 24, 2020 at 05:05:42PM -0000, Łukasz Zemczak wrote:
> So finalrd is now in main for bionic-updates. The question now is: will
> we need finalrd to be in bionic-security as well for this? I think we
> won't, but I guess my brain is a bit fried right now.

Don't see why you would. I think we just need the dependency. Thanks for
handling this!

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Changed in casper (Ubuntu Bionic):
assignee: nobody → Dimitri John Ledkov (xnox)
summary: - [18.04.4] System fails to reboot after installation
+ [18.04.4] Live system fails to reboot after installation
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers