freebsd stable - Mar 2020 - efi: WARNING: Unable to alias diskid/DISK-... to enc@n306168... - path too long

On Wed, Mar 18, 2020 at 10:37 AM Chris <bsd-lists at bsdforge.com> wrote:
> I'm getting the following message on a fresh install of 12.1:
> WARNING: Unable to alias diskid/DISK-WD-WCANM2154600 to
> enc at n3061686369656d30/type at 0/slot at 1/elmdesc at
Slot_00/diskid/DISK-WD-WCANM2154600
> - path too long
> Actually, there are several similar messages. Which required me to
> perform several disk related tasks in order to get a successful boot
> into the new system. It's GPT/UFS(2) if it matters. But I suspect
> it's more related to fbsd' implementation of EFI, as it relates to
my
> BIOS' implementation (Intel Sandy Bridge). What can I do to make
> everything happy?
>
> Thanks!
>
> --Chris
>
When did you see that message?  Was it printed from the bootloader, or
after you booted?  If it happened after boot, then they're probably
harmless, but you can make them go away by setting
kern.geom.label.disk_ident.enable=0.

On Wed, 18 Mar 2020 10:48:08 -0600 Alan Somers asomers at freebsd.org said
> On Wed, Mar 18, 2020 at 10:37 AM Chris <bsd-lists at bsdforge.com>
wrote:
> 
> > I'm getting the following message on a fresh install of 12.1:
> > WARNING: Unable to alias diskid/DISK-WD-WCANM2154600 to
> >
> > enc at n3061686369656d30/type at 0/slot at 1/elmdesc at
Slot_00/diskid/DISK-WD-WCANM2154600
> > - path too long
> > Actually, there are several similar messages. Which required me to
> > perform several disk related tasks in order to get a successful boot
> > into the new system. It's GPT/UFS(2) if it matters. But I suspect
> > it's more related to fbsd' implementation of EFI, as it
relates to my
> > BIOS' implementation (Intel Sandy Bridge). What can I do to make
> > everything happy?
> >
> > Thanks!
> >
> > --Chris
> >
> When did you see that message?  Was it printed from the bootloader, or
> after you booted?  If it happened after boot, then they're probably
> harmless, but you can make them go away by setting
> kern.geom.label.disk_ident.enable=0.
Thanks for the reply!
It's during boot, and found in dmesg.boot. I wouldn't care so much,
except I was unable to boot into the system until I performed a
gpart modify -i <N> -l <SLICE-LABEL> on all the slices, and modify
fstab(5) accordingly. Kind of a rough start for an install IMHO. :)

Thanks again, for the reply, Alan!

--Chris