[Bug 1886148] Re: failure to boot groovy daily

Fri Oct 9 12:13:23 UTC 2020

Hi Thomas,

1. There was a name error, wrong name of the input iso file - easy to
understand and fix, but I asked before thinking twice. There was also an
ownership/permission error, the file was owned by root and there were
not enough permissions for the standard user (because I had copied it
from my main computer to the test drive with Groovy persistent live,
where I installed programs and ran commands according to your advice).

2. mkusb creates a GPT by default, when making a persistent live drive.
This can be modified in the settings menu. The default is not to use
usb-pack-efi, and it has not been necessary with previous versions of
Ubuntu (including 20.04.x LTS), it has worked to use 'grub-install
command lines' (in the script dus-persistent).

After the big modification of the boot structure is has been necessary
to use usb-pack-efi (selected in the settings menu) to make persistent
live drives from Groovy iso files. I have not yet tested how mkusb can
create persistent live drives with your modifications with the xorriso
command line.

3. And yes, previous Ubuntu versions from when UEFI mode and cloning
were established (I think around 12.10 or 13.04) it has worked to clone
to USB drives, and these USB drives can boot both in BIOS and UEFI mode
(including 20.04.x LTS and Groovy until the beginning of June and the
big modification of the boot structure.

4. I am afraid, that there are several other new and fairly new Lenovo
computers that are affected by this bug.

4.1 One of them is reported here by @RussianNeuroMancer in comment #151:

Lenovo Yoga C630 WOS with arm architecture

If I understand correctly, it can boot (in UEFI mode) from a USB drive
with the content of the current Groovy iso file *extracted* to a FAT32
partition.

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

Title:
  failure to boot groovy daily

Status in OEM Priority Project:
  New
Status in Ubuntu CD Images:
  In Progress
Status in casper package in Ubuntu:
  Invalid
Status in cd-boot-images-amd64 package in Ubuntu:
  Fix Released
Status in cd-boot-images-arm64 package in Ubuntu:
  Fix Released

Bug description:
  When reported the groovy daily was failing on most boxes..

  Originally occurred if ISO is written via `dd`, `mkusb`, `Startup Disk
  Creator`, or `gnome-disks` (Restore disk image)

  Box still impacted are (owned by sudodus/nio-wiklund)

  * Lenovo V130

  and owned by Leó Kolbeinsson

  * Lenovo V14 IIL,Intel Core i3-1005G!,8GB,256GB SSD

  ---
  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/oem-priority/+bug/1886148/+subscriptions