disklabel autoinstall arm64 broken

[Alexander Bluhm]

Hi,

My arm64 regress machines do an install every Saturday.  The other
days of the week it is only an upgrade.  Installing these machines
broke between January 30 and February 6.

http://bluhm.genua.de/regress/results/2021-02-06T16%3A17%3A03Z/setup-ot10.log

After install it cannot boot the kernel.

Installer reports problem with mount.

  Making all device nodes... done.
  mount_ffs: unknown option -- l
  usage: mount_ffs [-o options] special node
  Multiprocessor machine; using bsd.mp instead of bsd.
  Relinking to create unique kernel... done.

Partition i is FFS.
The auto-allocated layout for sd0 is:
#                size           offset  fstype [fsize bsize   cpg]
  i:             2.0G        100522880  4.2BSD   2048 16384     1 # /usr/src

The week before it was:
  i:            16.0M            32768   MSDOS                    

So installing the EFI Bootloader does not work.  naddy@ did 3 commits
in disklabel during this week.  I guess that changed something.

bluhm

[Christian Weisgerber]

Alexander Bluhm:

> http://bluhm.genua.de/regress/results/2021-02-06T16%3A17%3A03Z/setup-ot10.log

> The auto-allocated layout for sd0 is:
> #                size           offset  fstype [fsize bsize   cpg]
>   i:             2.0G        100522880  4.2BSD   2048 16384     1 # /usr/src
>
> The week before it was:
>   i:            16.0M            32768   MSDOS
>
> So installing the EFI Bootloader does not work.  naddy@ did 3 commits
> in disklabel during this week.  I guess that changed something.

Those commits only affect disklabel -T, which is not used in your
install:
URL to autopartitioning template for disklabel? [none] none

I'm afraid I broke fdisk -e, see md_prep_fdisk() in
distrib/arm64/ramdisk/install.md

If no MSDOS boot partition is created, 'i' is unused and disklabel
auto-partitioning will use it for... *counts table entries*... yep,
/usr/src.

--
Christian "naddy" Weisgerber                          [hidden email]