After many hours diving down rabbit holes it turns out this is due to a
major change in the behaviour of update-initramfs introduced by Debian
in July 2018 which made its way into the Ubuntu archive end of april
2019.

01:02 <TJ-> Right! initramfs-tools had a MAJOR import from Debian with
"initramfs-tools (0.133ubuntu1)" April 29th; I've worked back through
the changes by Debian to "initramfs-tools (0.132) unstable" of 26th July
2018, which contains  "[f39625a] update-initramfs: Make "-k all" take
over other initramfs images"  and looking at that commit seems to
indicate it is the cause

https://salsa.debian.org/kernel-team/initramfs-
tools/commit/f39625afd6ba6c1aa2027286dc3ef1c933da14e0

Running the script with shell logging shows that when Calamares
initramfs module calls with:

# update-initramfs -k all -c -t

We get:

...
+ break
+ [ 0 -ne 0 ]
+ [ -z c ]
+ [ all = all ]
+ get_sorted_versions
+ linux-version list
+ linux-version sort --reverse
+ read -r version
+ test -e /boot/initrd.img-5.0.0-17-generic
+ read -r version
+ version_list=
+ verbose Available versions:
+ [ 0 = 1 ]
+ [ -z  ]
+ verbose Nothing to do, exiting.
+ [ 0 = 1 ]
+ exit 0

Because there is currently no /boot/initrd.img-$VERSION the version_list
is empty.

This shouldn't be a concern when we're using the "-c" create option so
it looks to be a bug in the logic.

The workaround for Lubuntu calamares installer configuration is to make
the file exist before calling it:

 touch /boot/initrd.img-$(uname -r)

Until initramfs-tools is fixed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829805

Title:
  Lubuntu Eoan Daily Image fails to boot after install on KVM

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Context: The live environment appears to function properly and install
  proceeds as expected with no noticeable errors.

  Expected results: After a system reboot the virtual machine enters the
  graphical environment

  Actual Results: After rebooting the virtual machine a kernel panic
  error screen appears. I will attempt to attach the screenshot after
  submitting this bug report.

  The collected data is from the live environment as the installed
  environment will not boot.

  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Eoan Ermine (development branch)
  Release:        19.10
  Codename:       eoan

  lubuntu@lubuntu:~$ apt-cache policy grub2
  grub2:
    Installed: (none)
    Candidate: 2.02+dfsg1-12ubuntu2
    Version table:
       2.02+dfsg1-12ubuntu2 500
          500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) 
eoan/universe amd64 Packages
          500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Tue May 21 00:30:39 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to