Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Nov 2024 16:02:26 +0100
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Dennis Clarke <dclarke@blastwave.org>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: zpools no longer exist after boot
Message-ID:  <5165C4DB-8BA0-4579-A808-F98FBF3B797F@FreeBSD.org>
In-Reply-To: <5798b0db-bc73-476a-908a-dd1f071bfe43@blastwave.org>
References:  <5798b0db-bc73-476a-908a-dd1f071bfe43@blastwave.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Nov 2024, at 14:05, Dennis Clarke <dclarke@blastwave.org> wrote:
>=20
> This is a baffling problem wherein two zpools no longer exist after
> boot. This is :
>=20
> 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#
>=20
> 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#
>=20
> 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 :
>=20
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5165C4DB-8BA0-4579-A808-F98FBF3B797F>