[Bug 1901553] Re: Improve documentation around initrdless boot

Launchpad Bug Tracker 1901553 at bugs.launchpad.net
Mon Jan 4 16:04:41 UTC 2021


This bug was fixed in the package grub2 - 2.04-1ubuntu37

---------------
grub2 (2.04-1ubuntu37) hirsute; urgency=medium

  * debian/patches/grub-install-backup-and-restore.patch: Fix-up the patch
    to correctly initialyze the names of the modules to restore. LP:
    #1907085
  * 10_linux: emit messages when initrdless boot is configured, attempted
    and fails triggering fallback. LP: #1901553
  * grub-common.service: port init.d script to systemd unit. Add warning
    message, when initrdless boot fails triggering fallback. LP: #1901553
  * debian/rules: undo po/ directory patching in
    override_dh_autoreconf_clean.
  * minilzo: built using the distribution's minilzo
  * ubuntu-fix-reproducible-squashfs-test.patch: fix squashfs-test with
    new squashfs-tools in hirsute.
  * rhboot-f34-make-exit-take-a-return-code.patch,
    rhboot-f34-dont-use-int-for-efi-status.patch: allow grub to exit
    non-zero under EFI, this should allow falling back to the next
    BootOrder BootEntry.
  * rhboot-f34-tcp-add-window-scaling-support.patch: speed up netboot
    transfer speed.
  * rhboot-f34-support-non-ethernet.patch,
    ubuntu-fixup-rhboot-f34-support-non-ethernet.patch,
    ubuntu-fixup-rhboot-f34-support-non-ethernet-2.patch:
    add support for link layer addresses of up to 32-bytes.
  * rhboot-f34-make-pmtimer-tsc-calibration-fast.patch:
    speed up calibration time, especially when booting VMs.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Sat, 12 Dec 2020 00:50:47
+0000

** Changed in: grub2 (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1901553

Title:
  Improve documentation around initrdless boot

Status in grub2 package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Sometimes it is not obvious why initrdless boot is generated; when
  is it attempted; and when it fails and boots with initrd.

   * Improve UX by leaving breadcrumbs and emit messages about
  initrdless boot, in more places

  [Test Case]

   * Boot system with initrdless boot
     - for example minimal cloud image from https://cloud-images.ubuntu.com/minimal/releases/
     - boot without graphical terminal, i.e. -nographics qemu option
   * Upgrade to new grub package
   * Uncomment GRUB_TERMINAL=console in /etc/default/grub

  
   1. Call `sudo update-grub`, a message should be emitted that initrdless boot will be attempted.

   2. Inspecting /boot/grub/grub.cfg, there are comments that initrdless
  boot will be attempted

   * Reboot

   * Observe the following:

   3. Inspecting console log, there are echo message from grub about
  attempting initrdless boot.

   * Install linux-generic kernel flavour; and remove kvm kernel
  flavour, reboot.

   * Observe in the console log

   1. There should be message about attempting initrdless boot
   2. kernel panic
   3. message about initrdless boot failing and attempting to boot with initrd

  [Regression Potential]

   * This change adds a few more user visible message, without
  translations. The actual behaviour that is happening is unchanged.
  This simply better notifies users about what is happening, and can be
  inspected interactively, statically, and from boot logs.

  [Other Info]

   * CPC requested these UX improvements, as there have been concerns
  that users are failing to discover why initrdless boot is happening;
  or failing; and how to effect it.

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



More information about the foundations-bugs mailing list