Fwd: Re: Weird loader behavior

[parv/freebsd]

Forwarding to the list from the address I have actually subscribed to
(in "basic HTML mode" Google Mail uses the actual account address not
the alias already set up) ...

---------- Forwarded message ---------
Date: Sun, Jan 31, 2021 at 2:37 PM
Subject: Re: Weird loader behavior
To: Juraj Lutter <juraj at lutter.sk>
Cc: <freebsd-stable at freebsd.org>


Juraj L wrote on Jan 31, 2021 at 12:15 PM ...
>
>     Reading loader env vars from /efi/freebsd/loader.env
> Setting currdev to disk0p1:
...
>    Command line arguments: loader.efi
>    EFI version: 2.40
>    EFI Firmware: BHYVE (rev 1.00)
>    Console: efi (0x20001000)
>    Load Path: \EFI\BOOT\BOOTX64.EFI
>    Load Device: PciRoot(0x0)/Pci(0x3,0x0)/HD(1
,GPT,A7A0422F-6F85-11EA-8A55-00A09858FAF5,0x28,0x64000)
...
> Setting currdev to zfs:zroot/ROOT/default:
> ZFS: i/o error - all block copies unavailable
> ZFS: i/o error - all block copies unavailable
> ERROR: /boot/lua/loader.lua:1: unexpected symbol near '`'.
...
> - problematic version is stable/12-c243335-ge817c8f77fe

Could you show your /boot/loader/loader.conf if you have one?

Do you mean yo can boot with git commit 31c234974, one earlier than
e817c8f77fe? If not, are you able to boot with even earlier commit of
c48240fa6f8?

> - Booting off 12.2-STABLE snapshot ISO 20210128-r369150 and using -a flag
to ask
> for a root mount and specifying zfs:zroot/ROOT/default makes the system
run
> normally (apropriate modules have to be loaded from within the loadet,
ofc).
> - using in-tree zfs
> - zpool scrub did not show any anomalies
> - gpart bootcode has already been run (after first unsusccessful boot).
> - Another bhyve guest (13.0-ALPHA3) on the same host works OK

What is git commit hash for 13.0-ALPHA3?

   - parv

--