Unable to boot with secondary zpool drives seated

Hello everyone! We've got a server configured with two zpools, one for storage and a zroot pool for the filesystem. After starting an upgrade from FreeBSD 12.2 to 13.1, every boot stalls out unless the storage pool's drives have been unseated. The only way to boot up and use the storage drives is to unseat them all with the server off, then boot, reseat all of the drives and import the pool. Clearly not an ideal situation!

We've upgraded the BIOS, IPMI firmware and upgraded to 13.2 in attempted fixes, but nothing seems to have helped. We have another server also upgraded from 12.2 to (now) 13.2, with a very similar configuration, which doesn't have the same issue.

Booting with all of the drives installed progresses to:
Code:
Consoles: EFI console
\

With the icon under Consoles: EFI console spinning, rotating through symbols |, \, -, /, until it stops, hangs for about 5 minutes on one symbol, then reboots itself.

Looking into similar issues, it seems like maybe it's attempting to check if the storage pool is bootable, but only the zroot pool has been configured as bootable.

Does anyone have any idea what may be causing this and how we'd go about correcting it? Or any way to enable more verbosity to have the console output what it's working on when it stalls?

Any help is appreciate! Thanks!
 
Does anyone have any suggestions, here, by chance? Clearly the EFI Console is trying to process something, but I can't figure out what it's getting hung up on, yet.
 
Thanks or the suggestion Emrion!

I finally had time to get back to this, mounted the efi partition, replaced the efi boot loader (like this) with the new one and it worked!
 
One thing to remember is 12.x used "FreeBSD native ZFS" while 13.x switched to OpenZFS. That pretty much mandated boot loader updates for both legacy (gpt) and EFI.
I think that kind of information was in the release notes.
 
One thing to remember is 12.x used "FreeBSD native ZFS" while 13.x switched to OpenZFS. That pretty much mandated boot loader updates for both legacy (gpt) and EFI.
I think that kind of information was in the release notes.

The most important caveat about that is, the OpenZFS version in 13.2 chokes on orphaned zfs labels:

View: https://twitter.com/DLangille/status/1671895016875368450



This also hit me on one system that refused to boot after upgrading from 12.4 to 13.2.
OTOH I still boot my desktop at work with the bootloader from the 12.4 installer, despite running 13.2, because there still seems to be a bug[1] with some of those crappy ASUS boards. and because supermicro couldn't ship anything micro-ITX in a reasonable timeframe when I needed a new workstation, I was forced to buy an ASUS board... (the other, even worse option would have been ASRock)

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209821
 
  • Like
Reactions: mer
One thing to remember is 12.x used "FreeBSD native ZFS" while 13.x switched to OpenZFS. That pretty much mandated boot loader updates for both legacy (gpt) and EFI.
I think that kind of information was in the release notes.
Good point! This upgrade has been a long time coming, so we jumped up a few versions. Looks like they did include a note to replace the bootx64.efi file in the 13.0 release notes and I just missed that part!
 
  • Like
Reactions: mer
Back
Top