Zpool with latest feature com.delpfix:head_errlog can not be booted from.

I did upgrade my FreeBSD Current and with that i updated my storage pool and my zroot pool. I did add the new gptboot code on the disk. After the reboot i can not boot anymore. So i did reinstall the os on one disk of the old zroot mirror pool and did leave the second untouched. Then i can i

Re: Zpool with latest feature com.delpfix:head_errlog can not be booted from.

I’ll see into it. It would be nice to have at least heads up message about such features, or zfs code does have means to block feature upgrade on boot pool. Rgds, Toomas > On 20. May 2022, at 11:39, Johan Hendriks wrote: > > I did upgrade my FreeBSD Current and with that i updated my storage

loader_4th.efi broke?

Hi, something between 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3 made loader_4th.efi go all "failed to allocate staging area: 9" I am netbooting booting, no ZFS involved. One other data point: the base system compil

Re: loader_4th.efi broke?

> On 20. May 2022, at 20:00, Bjoern A. Zeeb > wrote: > > Hi, > > something between > 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and > 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3 > made loader_4th.efi go all > "failed to allocate staging area: 9" > > I am netbooting

Re: EFI framebuffer information, then nothing: GENERIC-NODEBUG

On Sat, 14 May 2022, Graham Perrin wrote: On 19/04/2022 23:37, Graham Perrin wrote: Sometimes, boot gets no further than EFI framebuffer information. Whenever this occurs, the computer will stop immediately in response to a simple, short press on the power button. … When I first wrote

Re: loader_4th.efi broke?

On Fri, 20 May 2022, Toomas Soome wrote: On 20. May 2022, at 20:00, Bjoern A. Zeeb wrote: Hi, something between 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3 made loader_4th.efi go all "failed to allocate staging a

Re: loader_4th.efi broke?

> On 20. May 2022, at 20:11, Bjoern A. Zeeb > wrote: > > On Fri, 20 May 2022, Toomas Soome wrote: > >>> On 20. May 2022, at 20:00, Bjoern A. Zeeb >>> wrote: >>> >>> Hi, >>> >>> something between >>> 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and >>> 255723.b3fa36efe797445cb0b

Re: loader_4th.efi broke?

On Fri, 20 May 2022 20:19:58 +0300 Toomas Soome wrote: > > > > On 20. May 2022, at 20:11, Bjoern A. Zeeb > > wrote: > > > > On Fri, 20 May 2022, Toomas Soome wrote: > > > >>> On 20. May 2022, at 20:00, Bjoern A. Zeeb > >>> wrote: > >>> > >>> Hi, > >>> > >>> something between > >>> 255

Re: loader_4th.efi broke?

On Fri, 20 May 2022, Emmanuel Vadot wrote: See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 It was bisected to the latest llvm update, I haven't digged yet. Thanks a lot manu for pointing to this; hadn't seen it yet. Happy weekend, Bjoern -- Bjoern A. Zeeb

Re: Zpool with latest feature com.delpfix:head_errlog can not be booted from.

Can you let me know when a replacement binary is available for EFI? I have my buildbox/dev system in a non-bootable state. It's RAIDZ-1 pool, and no place to put another disk. Thanks for any help. (If can email the replacement binary that would be wonderful). On 05/20/2022 4:47 am, Toomas S

Re: Zpool with latest feature com.delpfix:head_errlog can not be booted from.

Hi! You can find binaries from boot.tar root@freebsd:~ # zpool get all NAME PROPERTY VALUE SOURCE zroot size 29.6G - zroot capacity

Re: RockPRO64 exception 22 esr_el1 8a000000

I recompiled kernel, world and wireguard-kmod, and it still happens. Have opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264115 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe