On 15-8-2022 22:11, Warner Losh wrote:
This should be fixed now.

commit d98de7440507aea1648c8f4bc302bf88c0eb9458
Author: Toomas Soome <tso...@freebsd.org>
Date:   Mon Aug 15 00:49:50 2022 +0300

    loader: zfs reader should only store devdesc in f_devdata

    Use d_opendata for device specific data.

    PR:             265825
    Reviewed by:    imp
    Differential Revision: https://reviews.freebsd.org/D36202

is the commit you want to have in your tree.

I needed the system back, since it ran some critical applications.
But I split the zfs-mirror and only reused one disk.
Now see if I can find the time to verify Toomas's fix.

Problem is also that the system itself does no longer boot.
But "Idwer Vollering <vid...@gmail.com>" suggested ripping the
/boot/loader from 5th of Aug. So I can atleast boot into multi user,
and rebuild.

Probably next weekend.

Thanx,
--WjW
Warner

On Mon, Aug 15, 2022 at 6:23 AM Willem Jan Withagen <w...@digiware.nl> wrote:

    Hi,

    I tried upgrading a 14.0-CURRENT system from somewhere Dec 2021,
    to the
    most recent state.
    So I build everything and installed the things...

    Reboot and I end up in BTX....
    Oke, so I perhaps should also update pmbr and gptzfsboot.
    Booted from stick, and update...

    Still I end up in BTX.

    So get out the guns:
    Downloaded the latest snapshot, and even there I do end up in BTX
    once I have installed the system.
    The Stick does boot the mem-stcik into EFI, and lets me install the
    system. But upon reboot I again endup in BTX.

    So i anybody out there willing to help me figure out what is wrong
    here.
    I can sent you a foto of the BTX screen.

    System specs:
         ASUS M5A97 PLUS
         AMD FX-8370 Eight-Core Processor
         24Gbyte Ram
         1 HD (rust) seagate ST3250318AS 250G
             met auto-install ZFS stripe, 8G swap, BIOS+UEFI

    Thanx,
    --WjW

    BTW: I now installed 13.1-RELASE on another disk, and that (just)
    works


Reply via email to