[Bug 1886148] Re: failure to boot groovy daily

[sudodus]

@ Steve Langasek (vorlon),

According to your request I continue the dialogue here about problems to
boot a Lenovo V130 in UEFI mode with the current daily Groovy iso files.

This problem was reported in comment #31

https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/31

- When I select the USB drive from the temporary menu, it skips to the
internal drive. This is a different failure mode compared to the
previous iso files. (This computer is willing to boot from the
grub-n-iso system of comment #26 and from cloned drives made from groovy
iso files from June.)

https://dustinweb.azureedge.net/media/494085/v130.pdf

---

Previously I have not touched the UEFI/BIOS system of the *Lenovo V130*
that I have access to, but now, that you ask about it, I had better do
it in order to help identify what goes wrong, when trying to boot USB
drives cloned from Groovy ISO files.

When testing Groovy iso files, the fix against the boothole bug was
entered into this computer, so that USB drives that used to boot would
no longer boot.

I turned off secure boot, and then it was possible again to boot for
example Ubuntu 20.04.1 LTS (cloned to a USB drive). This matches the
observation, that Groovy iso files worked until you modified the boot
system (when you removed syslinux boot in BIOS mode, but obviously also
modified the boot system in UEFI mode).

But USB drives cloned from the current Ubuntu Groovy as well as Lubuntu
Groovy do not boot.

This is when using the boot option in the temporary boot menu (F12)

"Linpus Lite (<name of the USB drive>)"

in the picture attached to the previous comment. This is the only
available USB boot option in UEFI mode.

Then I turned off UEFI mode and set teh computer to boot in 'legacy
mode'. Now there were more boot options in the temporary boot menu
(F12). These options are shown in the picture attached to the previous
comment. The option

"USB Hdd: <name of the USB drive>"

*works* also with USB drives cloned from the current Ubuntu Groovy as
well as Lubuntu Groovy.

So the problem in this case is not due to secure boot, but the "Linpus
Lite" boot option does not work with the current Groovy iso files. It
works with older iso files including Ubuntu 20.04.1 LTS and Groovy iso
files from before you modified the boot system (when you removed
syslinux boot in BIOS mode, but obviously also modified the boot system
in UEFI mode).

I attach the output of`efibootmgr -v`.


** Attachment added: "efibootmgr-of-lenovo-v130.txt"
   https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+attachment/5407572/+files/efibootmgr-of-lenovo-v130.txt

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

Title:
  failure to boot groovy daily

Status in Ubuntu CD Images:
  In Progress
Status in casper package in Ubuntu:
  Invalid

Bug description:
  When reported the groovy daily was failing on most boxes..
  Changes have been made and now it fails to boot on far fewer boxes.
  Originally occurred if ISO is written via `dd`, `mkusb`, `Startup Disk Creator`, or `gnome-disks` (Restore disk image)

  Boxes still impacted are (sudodus/nio-wiklund)

  * Lenovo V130

  and Leó Kolbeinsson (leok) has issues depending on what writes the ISO
  (see comment #53; failing in BIOS mode when media is created on a
  Windows box with Rufus and/or Universal-USB-Installer) on

  * Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics)
  * Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000)

  ---
  Original detail follows
  (with minimal edits; these boxes now boot groovy ISOs)

  This is very similar to https://bugs.launchpad.net/bugs/1883040

  Boxes that have failed to boot it are

  dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
  dell [optiplex] 780 (c2q-q9400, 4gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

  --  sudodus' boxes
  dell Precision M4800
  dell Latitude E7240
  Toshiba Satellite Pro C850-19w
  HP Probook 6450b - works now

  --  leok's boxes
  Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics, Realtek RTL8111/81681/8411 GB Ethernet, Qualcomm Atheros AR9462 Wireless, Bluetooth Atheros A315-53, 500 GB hd)

  Dell [Optiplex] 7010 ( i5-3470 , 16 GB, Intel Graphics 2500, Intel
  82579LM GB Ethernet ,1TB hd) VirtualBox

  Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd)
  --

  The ISO was written twice to two different thumb-drives. Same issue
  each time on same boxes.

  On a number of boxes it’s wanting me to download aka
  https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040 however it’s
  done that on boxes not impacted by that bug, which makes me think
  thumb-drive/squashfs errs related.  Also results of boot appeared
  different on varying boxes (inconsistent; dc7700 reported no thumb-
  drive; d755-5 also did that sometimes, sometimes it got to wanting to
  download - those two boxes were impacted by prior report; the
  remaining boxes were more consistent in response..; but if trouble
  reading data on thumb-drive then the slower boxes (dc7700/d755-5) may
  have more issues & thus be less consistent?)

  I'll file this as a bug report so I can close my failed QA-tests, but
  I'm considering changing the status to 'incomplete', and re-testing
  tomorrow, OR it needs me to re-write ISO from a different box to a
  third-thumb-drive as I don't think I've ruled out media issues given
  Leok's report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions