Re: zpools no longer exist after boot

On 28 Nov 2024, at 14:05, Dennis Clarke <dclarke@blastwave.org> wrote:
> 
> This is a baffling problem wherein two zpools no longer exist after
> boot. This is :
> 
> titan# uname -apKU
> FreeBSD titan 15.0-CURRENT FreeBSD 15.0-CURRENT #1 main-n273749-4b65481ac68a-dirty: Wed Nov 20 15:08:52 GMT 2024 root@titan:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 amd64 1500027 1500027
> titan#
> 
> titan# zpool list
> NAME   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP HEALTH  ALTROOT
> t0     444G  91.2G   353G        -         -    27%    20%  1.00x ONLINE  -
> titan#
> 
> The *only* zpool that seems to exist in any reliable way is the little
> NVME based unit for booting. The other two zpools vanished and yet the
> devices exist just fine :
> 
> titan#
> titan# camcontrol devlist
> <ST20000NM007D-3DJ103 SN03>        at scbus0 target 0 lun 0 (pass0,ada0)
> <ST20000NM007D-3DJ103 SN03>        at scbus1 target 0 lun 0 (pass1,ada1)
> <AHCI SGPIO Enclosure 2.00 0001>   at scbus2 target 0 lun 0 (ses0,pass2)
> <AHCI SGPIO Enclosure 2.00 0001>   at scbus6 target 0 lun 0 (ses1,pass3)
> <SAMSUNG MZVKW512HMJP-000L7 6L6QCXA7>  at scbus7 target 0 lun 1 (pass4,nda0)
> <FREEBSD CTLDISK 0001>             at scbus8 target 0 lun 0 (da0,pass5)

It has been my experience that with disks connected to external enclosures, these sometimes take a long time to come up. If they come up only after the kernel initially detects ZFS pools, they will not be shown or imported at all.

If you look at dmesg or boot logs, are the external disks detected around the same time as the NVMe device?

-Dimitry