zfs Cannot find the pool label for ‘tank’ on boot

ZFS boot system, hardware, so would need a USB, and it is very far away.

Upgrade from 12-release to 13-release went south on the second shutdown -r

[ excuse, this is an ocr from a screen capture from ipmi kvm ]

Code:
ukbd0: <Peppercon AGMultidevice, class 6/6, rev 2.60/@.81, addr 2> on usbus3
kbd2 at ukbdé
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Mounting from zfs:tank/root failed with error 5; retrying for 3 more seconds
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Solaris: NOTICE: Cannot find the pool label for ‘tank’
Mounting from zfs:tank/root failed with error 5.
Loader variables:
  vfs.root.mountfrom=zfs:tank/root

Manual root filesystem specif ication:
  <fstype>:<device> [options]
  Mount <device> using filesystem <fstype>
  and with the specified (optional) option list .

  eg. ufs:/dev/da0sla
       zfs:zroot/ROOT/default
       cd9666: /dev/cd@ ro
         (which is equivalent to: mount -t cd9668 -o ro /dev/cd@ /)
 
   ?            List valid disk boot devices
   .            Yield 1 second (for background tasks)
   <empty line> Abort manual input

mountroot>

Do I need to tell it to reassemble the ZFS array, and how?
 
i presume it is booting off the first pile of rust it could find; but IPMI display sometimes hides the first like of the screen. it is an efi system i was trying single abuser boot. if i take the BootEnvironments Beastie option, all say "Failure to include" am not seeing rescue mode, and my altzheimers device says it used to be somewhere.
geom part show
results in "invalid file system specification"
 
if you have access to efi shell and can download files via http you can probably prepare a mfsroot image and mount that
 
we're trying to mount the 13 iso over the net and then figure out how to use that to assemble the array
 
pciconf -lv shows the card, but no disks detected with camcontrol devlist' or other incantations
 
if you didn't upgrade the pool you can still roll back
and try with 13-STABLE
even you upgraded the pool you can still use openzfs from ports
 
yes, it is possible that the upgrade wanted to tweak /etc/rc.conf and didn't. mabe i'll be able to look at it under 12.3. i am booting over net from portland to dallas, so i have to be patient
 
freebsd-update rollback
but you need to have the original root fs
either boot kernel.old or boot from cd until loader and set root fs to zfs:zroot/ROOT/default or whatever it was
 
it seems the module is not in kernel nor built as a module by default
just build it and load it before rolling back

boot 12.x and copy the module to /boot/modules
then modify loader.conf if needed and reboot 13

on a 13 box go to /sys/modules/hptrr and
make all install
copy it from /boot/modules
 
yup. htprr.ko is in /boot/kernel.old (12) and not in /boot/kernel. will it work just to steal the 12 for 13?
 
It's in 13 src, check out sys/modules/hptrr. You can compile it yourself. Interesting though why it's not there by default. Maybe because it needs 3rd party blob to load (fw) ?
EDIT: probably not true as it exists in 12.
Interestingly enough ./sys/modules/Makefile includes this module on 13.
 
it seems the module is not in kernel nor built as a module by default …

… htprr.ko is in /boot/kernel.old (12) and not in /boot/kernel. …

I have the module readily available with GENERIC with 14.0-CURRENT but not with GENERIC with 13.0-RELEASE-p6. Weird?

Code:
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # uname -iKU
GENERIC 1300139 1300139
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # freebsd-version -kru
13.0-RELEASE-p6
13.0-RELEASE-p6
13.0-RELEASE-p6
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # kldload hptrr
kldload: can't load hptrr: No such file or directory
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # kldload hptiop
kldload: can't load hptiop: module already loaded or in kernel
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # kldstat | grep hptiop
root@mowa219-gjp4-vm-freebsd-13-zfs:~ # uname -a
FreeBSD mowa219-gjp4-vm-freebsd-13-zfs 13.0-RELEASE-p6 FreeBSD 13.0-RELEASE-p6 #0: Mon Jan 10 06:28:50 UTC 2022     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
root@mowa219-gjp4-vm-freebsd-13-zfs:~ #
 
just gettin the hptrr.ko over using 12 by putting it in an ftpable site. do i also need hptiop.ko?
 
Back
Top