Problems with bootable Ubuntu 20.10 USB stick

Bug #1896557 reported by Marcos Nascimento
This bug report is a duplicate of:  Bug #1886148: failure to boot groovy daily. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu CD Images
New
Undecided
Unassigned
Ubuntu
Incomplete
Undecided
Marcos Nascimento

Bug Description

I recorded a ubuntu 20.10 flash drive, however my notebook starts only in legacy mode.
In efi mode it's as if the flash drive isn't connected.
With the Ubuntu 20.04 flash drive, it works normally.
My notebook is the Lenovo ideapad 330-15IKB.

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1896557

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

FYI: Given you can't boot the media in EFI mode; boot and run apport-collect in legacy mode which as I understand your description is where it works. This will provide details as to daily used & more specifics as to your hardware.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Marcos Nascimento (wstlmn) wrote :

Thanks for the reply. I started the system in legacy mode and executed the requested command (apport-collect 1896557), resulting in "No Additional Information Collected". Alternatively, I ran "lshw" for more information about the hardware. The file is attached.

Revision history for this message
Marcos Nascimento (wstlmn) wrote :
Changed in ubuntu:
assignee: nobody → Marcos Nascimento (wstlmn)
Revision history for this message
Marcos Nascimento (wstlmn) wrote :

Looking at the ubuntu 20.10 installation pendrive I checked the absence of the "EFI" folder. So I was wondering: How will the system start in EFI without said folder?

Revision history for this message
Chris Guiver (guiverc) wrote :

The problem of no apport-collect data being uploaded is no specifics as to image being tested, nor other details are provided.

Thank you for uploading lshw detail though.

Groovy images are 'daily' (~interval), so whilst currently spins are only being made when necessary, we can still get one or more per day.

Another way of recording detail where you're having trouble maybe recording the details on the QA (Quality Assurance) web site, and linking the problem you're having with this bug report. That will provide a means to record which ISO you've had problems with, and record subsequent tests.

For the Ubuntu groovy daily, see http://iso.qa.ubuntu.com/qatracker/milestones/413/builds
For the Ubuntu groovy beta, see http://iso.qa.ubuntu.com/qatracker/milestones/417/builds

You can use `zsync` to reduce bandwidth used to update your ISO instead of a full download.

Thanks again for taking the time to help make Ubuntu better

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1896557] Re: Problems with bootable Ubuntu 20.10 USB stick

On Thu, Oct 01, 2020 at 10:46:02PM -0000, Marcos Nascimento wrote:
> Looking at the ubuntu 20.10 installation pendrive I checked the absence
> of the "EFI" folder. So I was wondering: How will the system start in
> EFI without said folder?

Because the image contains an entirely separate ESP partition, which is not
part of the iso9660 filesystem.

Some systems (notably, certain Lenovo ideapads) don't respect this part of
the UEFI specification for USB booting, and require the non-standard
EFI/BOOT directory to be on the iso9660 filesystem.

This has been addressed for the first daily image after the 20.10 beta. I'm
marking this bug as a duplicate of the primary bug that is being used to
track this work.

Revision history for this message
Marcos Nascimento (wstlmn) wrote :

OK! I will follow the #1886148, but I would like to report that I recorded a USB stick manually and added the folder /EFI. That way the system started normally.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.