[Bug 1872463] Re: Duplicate marker files will make chainload fail to launch subiquity

[Dimitri John Ledkov]

I think I found the problem!

On x86_64
# Skeleton configuration file which finds the real boot disk.
cat >"$workdir/grub.cfg" <<EOF
if [ -z "\$prefix" -o ! -e "\$prefix" ]; then
	if ! search --file --set=root /.disk/info; then
		search --file --set=root /.disk/mini-info
	fi
	set prefix=(\$root)/boot/grub
fi
if [ -e \$prefix/$platform/grub.cfg ]; then
	source \$prefix/$platform/grub.cfg
elif [ -e \$prefix/grub.cfg ]; then
	source \$prefix/grub.cfg
else
	source \$cmdpath/grub.cfg
fi
EOF

is used inside the monolithic/gcdx64.efi

However, during d-i build, self-built bootaa64.efi is used with:
	cat >"$workdir/boot/grub/grub.cfg" <<EOF
search --file --set=root /.disk/info
set prefix=(\$root)/boot/grub
source \$prefix/$platform/grub.cfg
EOF


The monolithic one is the one that gets signed, and imho we should use that one on arm64 for now.

** Also affects: ubuntu-cdimage
   Importance: Undecided
       Status: New

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  Duplicate marker files will make chainload fail to launch subiquity

Status in subiquity:
  New
Status in Ubuntu CD Images:
  New
Status in debian-installer package in Ubuntu:
  New

Bug description:
  Focal beta iso efi.img manipulates grub when searching for the target
  device to boot. The current searching method uses /.disk/info as a
  marker file to identify the target live usb device. efi.img assumes
  there is only one live bootable device inserted with the marker file
  /.disk/info and searches in this way:

   search --file --set=root /.disk/info
   set prefix=($root)/boot/grub
   source $prefix/arm64-efi/grub.cfg

  In some use cases, people pre-insert many different distributions so
  they could easy to boot to and re-install different distributions. The
  marker file method will block this kind of multiple bootable setup.

  [Steps to Reproduce]
  1. Pre-insert one or more Ubuntu Bionic (or above) live usb sticks to your target machine
  2. Boot from focal beta iso live usb stick

  [Expected Result]
  We boot to the subiquity and start to install the system.

  [Actual Result]
  We will boot to the grub menu provided by the other live usb sticks. The unexpected grub menu may lead you to load incorrect installer files and fail on installation.

  [More Information]
  The issue is reproducible 100% by a combination of Marvell Cavium ThunderX2 Sabre with Bionic live usb pre-inserted and intended to install the system via focal beta iso live usb. Use dd to destroys the bionic live usb will make the chainload boot to the expected focal one (and completed the installation with subiquity).

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1872463/+subscriptions