From nobody Mon Dec 22 16:58:13 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dZkqX41S3z6LTLD for ; Mon, 22 Dec 2025 16:58:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dZkqW5tmQz3fRG for ; Mon, 22 Dec 2025 16:58:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=fQmAdfhe; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::102a) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pj1-x102a.google.com with SMTP id 98e67ed59e1d1-34c565b888dso4652263a91.0 for ; Mon, 22 Dec 2025 08:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1766422704; x=1767027504; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0iOZgLrIpRV7nEFZ6G7m6XorCQ/2vpOIy7C2mkOx08A=; b=fQmAdfhedKGdQ0bIoYAIrCWMj6Cm4f4JjWXA8INXRXXbneAP22LQeOCGxdet2OE0Qv YJIk8oofU4e7FHqfaaz6mGFz+ox72pu4TJtWgoikBWCHRpjGyRtOjYbkmmabv3t6A97e IELRvk8epO12ZnhID/waI9ZpSMEgk5HcCPLjbFybFHkPD09+SfWRGRz9yyqPDWQ4k3AZ bSGLLdSSHUYLDxOncBiPXJu4ErJg8Vtq5h7KfZEpORRE22MQrHzatXjSuqY3A05fE/1e 80W88TmZv/zhDnldJepgjTEVmg/0UVAcOO7HncJm/JlmU1qsbtU8L3PXmYUQ9lIeOVrp m79A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766422704; x=1767027504; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=0iOZgLrIpRV7nEFZ6G7m6XorCQ/2vpOIy7C2mkOx08A=; b=PVjRO0CuqlbyCpU2xBV9vZJYm6m8pZ7tnI3ztzx5FfqqcneF97yZfUCwdRFJ8B7sMc ZGdl3g6C6cugEiQkIinCF7o+7+xGUaxbwD8l7NS7SJ1uv8xwdWYtNWXE2cisHPDD+RVJ MHWzOmE01i6JjM8MRjZsaCqtafwn8lIFclzTwPKpO9DlS/ooii0nEAI4P/6NX4bdhu7O r+nzulnMAEHFjTpXET/+bciGO7VZ+S/HWiqeMZ4HtYSj5fErqohh9BzYp1t30PV6puZN MbR40+spj+QK5EnfA03HjjpB/AIHAv6P1U1yTxHiiq0H1R3jHl46BKYulyCrWRKBJzTr FIjw== X-Gm-Message-State: AOJu0YzpTtkZ36QjuIoipmXu3HYZKEmLVEMlrO9mYx70ehheBoNDBa8y TyQ4wzQNr62N+ngi4sPzuFYzveZY0LLvbO+G7RSc9B0ncP3/Khwl07WDbr6fCyKbrjSJ8zwVnCK mQVzEPQKuVxAtUDW1xIalU1sL54aIeUcuja/Y4m+iPSuUFJuL9XM22cA= X-Gm-Gg: AY/fxX50DHSoRt7E5/RbwMSrTROuu00T0lCK+OOtTmN/JTSEN+OJdvnhC1XAiEt9HFc FAiSr/kzr/caqUfYyOz2LnGgvIS8TaIe8Y6pIpDRi8gFdGxERql+fZ9NxNN6HyRdp2TMv3Fwgsw ZrYMrMY98Cb6woa9jFJtyKCMnnLt7grszFECYLMbdgux5Cqb1n9uJKBZVzN9MQiWTD0Rdq/yfR0 VUUNul/jedOf2BTnekMWbtXCUI+8ziDfzAjT4P3kP0bbJQEdLYCfo/wvcbtmozVr54H0RU= X-Google-Smtp-Source: AGHT+IF0Ixu8O5d8XsBJg5X+JvRvFbLNbl3BEXRvSEf9Q1qVf5TbPXhCJaGEM1OPnblTz/rWFStWChr5xMp5qjsPKwg= X-Received: by 2002:a17:90b:53c7:b0:34a:adf1:6781 with SMTP id 98e67ed59e1d1-34e92143b39mr9501561a91.9.1766422704320; Mon, 22 Dec 2025 08:58:24 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <198170948d34f4dc169e94934da82161@Leidinger.net> <89a92e0a926239e2c192dc0ff9c80d6e@Leidinger.net> In-Reply-To: <89a92e0a926239e2c192dc0ff9c80d6e@Leidinger.net> From: Warner Losh Date: Mon, 22 Dec 2025 09:58:13 -0700 X-Gm-Features: AQt7F2p1nnF6jzOxIod-rFSW22i7ahL-J7py8yhGkI76keM-fM2nOGnJZy9Dhgc Message-ID: Subject: Re: Changes in cam/nvme causes issues? To: Alexander Leidinger Cc: Current Content-Type: multipart/alternative; boundary="000000000000d0827c06468d5538" X-Spamd-Bar: - X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102a:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2607:f8b0:4864:20::102a:server fail]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; MLMMJ_DEST(0.00)[current@freebsd.org]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4dZkqW5tmQz3fRG --000000000000d0827c06468d5538 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Dec 21, 2025 at 8:37=E2=80=AFAM Alexander Leidinger wrote: > Am 2025-12-14 14:05, schrieb Warner Losh: > > Let's do one issue at a time. There's too much missing info. Top posting > since there's not a lot of context to this request > > > The disk died now completely, so the CRC errors are out of reach now. > > > First, let's start with pciconf -l of the nvme drive. I have a strong > idea, but need some data. > > > While already provided privately with some other data, here for the publi= c > so that people are aware that currently there is an issue with such drive= s: > nvme0@pci0:5:0:0: class=3D0x010802 rev=3D0x00 hdr=3D0x00 vendor=3D0x144d > device=3D0xa809 subvendor=3D0x144d subdevice=3D0xa801 > Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V > Yea, so far this is the only report I've received, and there's not enough data in it to reproduce it with any of the dozen NVMe drives that I have, or to spot a difference with what I know I check in the code. So if it's compiled into the kernel with cam also compiled into the kernel, I know it works. Warner > Bye, > Alexander. > > > Also, the disk report needs full logs with and without the settings that > have uncorrectable in them. I'd expect that a shorter timeout would lead = to > different behavior, but maybe that error syndrome isn't one I've seen. It > would also be helpful to know which of the times changes the behavior... > > Warner > > On Sun, Dec 14, 2025, 5:06=E2=80=AFAM Alexander Leidinger > wrote: > > Hi Warner, > > I try to update a 15-current (as of 2025-11-27-110715) to a recent 16 > (as of 2025-12-13-132815). It fails to import a pool due to a missing > nvme. I also have a broken HD in this system... to be on the safe side I > mention it. > > This is from 15-current: > ---snip--- > NAME STATE READ WRITE CKSUM > rpool DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > diskid/DISK-WD-WCC4N4KLEZT7p3 ONLINE 0 0 0 > diskid/DISK-WD-WCC4N1DF9DA2p3 ONLINE 0 0 0 > diskid/DISK-WD-WX52D625R0NTp3 ONLINE 0 0 0 > diskid/DISK-WD-WCC4N1PYJ3F8p3 OFFLINE 0 0 0 > logs > diskid/DISK-493504058890547p1 ONLINE 0 0 0 > cache > diskid/DISK-493504058890547p2 ONLINE 0 0 0 > > NAME STATE READ WRITE CKSUM > space DEGRADED 0 0 0 > raidz2-0 DEGRADED 0 0 0 > diskid/DISK-WD-WCC4N4KLEZT7p4 ONLINE 0 0 0 > diskid/DISK-WD-WCC4N1DF9DA2p4 ONLINE 0 0 0 > diskid/DISK-WD-WX52D625R0NTp4 ONLINE 0 0 0 > diskid/DISK-WD-WX52D625R2TPp4 ONLINE 0 0 0 > diskid/DISK-WD-WCC4N1PYJ3F8p4 OFFLINE 0 0 0 > logs > diskid/DISK-S649NL0T819360Vp2 ONLINE 0 0 0 > cache > diskid/DISK-S649NL0T819360Vp3 ONLINE 0 0 0 > ---snip--- > > The offline marked partitions are on the same HD (the broken one). The > DISK-S649NL0T819360V device use as log and cache in the second pool > causes the issue on 16-current. > > On 16-current I get "uncorrectable parity/CRC error" messages on boot > from the broken disk. I used this to get rid of those errors: > ---snip--- > # grep kern.cam /tmp/be_mount.MhLw/boot/loader.conf > kern.cam.tur_timeout=3D"60" > kern.cam.inquiry_timeout=3D"60" > kern.cam.modesense_timeout=3D"60" > ---snip--- > > But the second pool ("space") fails to get imported. When I import it > via "zpool import -m space" it shows me that the log and cache devices > (different partitions on the same hardware) are not available. > This is the device in question as seen from 15-current: > ---snip--- > nda0: > nda0: Serial Number S649NL0T819360V > [1] nda0: nvme version 1.4 > nda0: 953869MB (1953525168 512 byte sectors) > [1] GEOM: new disk nda0 > ... > [1] pass6 at nvme0 bus 0 scbus6 target 0 lun 1 > pass6: > pass6: Serial Number S649NL0T819360V > [1] pass6: nvme version 1.4 > ---snip--- > > In case you need some info from the 15- or 16-current BE, which info do > you need? > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > --000000000000d0827c06468d5538 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Dec 21,= 2025 at 8:37=E2=80=AFAM Alexander Leidinger <Alexander@leidinger.net> wrote:

Am 2025-12-14 14:05, schrieb Wa= rner Losh:

Let's do one issue at=C2=A0a time. There's too mu= ch missing info. Top posting since there's=C2=A0 not a lot of context t= o this request=C2=A0
=C2=A0
The disk died now completely, so the CRC errors are out o= f reach now.
=C2=A0
First, let's start with pciconf -l of the nvme drive.= I have a strong idea, but need some data.
=C2=A0
While already provided privately with some other data, he= re for the public so that people are aware that currently there is an issue= with such drives:
nvme0@pci0:5:0:0: class=3D0x010802 rev=3D0x00 hdr=3D0x00 = vendor=3D0x144d device=3D0xa809 subvendor=3D0x144d subdevice=3D0xa801
Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V
<= /div>

Yea, so far this is the only re= port I've received, and there's not enough data in it to reproduce = it with any of the dozen NVMe drives that I have, or to spot a difference w= ith what I know I check in the code. So if it's compiled into the kerne= l with cam also compiled into the kernel, I know it works.

Warner=C2=A0
=C2=A0
=
Bye,
Alexander.
=C2=A0
Also, the disk report needs full logs with and without th= e settings that have uncorrectable in them. I'd expect that a shorter t= imeout would lead to different behavior, but maybe that error syndrome isn&= #39;t one I've seen. It would also be helpful to know which of the time= s changes the behavior...
=C2=A0
Warner

On Sun, Dec 14, 2025, 5:06=E2=80=AFAM Alexander Leidinger = <Alexander@leidinger.net> wrote:
Hi Warner,

I try to update a 15-current = (as of 2025-11-27-110715) to a recent 16
(as of 2025-12-13-132815). It = fails to import a pool due to a missing
nvme. I also have a broken HD i= n this system... to be on the safe side I
mention it.

This is fr= om 15-current:
---snip---
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0NAME=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0STATE=C2=A0 =C2=A0 =C2=A0READ WRITE CKSUM=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rpool=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 D= EGRADED=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirror-0=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DEGRADED= =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-WD-WCC4N4KLEZT7p3=C2= =A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 = =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-WD-W= CC4N1DF9DA2p3=C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00= =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0di= skid/DISK-WD-WX52D625R0NTp3=C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 = =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0diskid/DISK-WD-WCC4N1PYJ3F8p3=C2=A0 OFFLINE=C2=A0 =C2=A0 =C2= =A0 0=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0logs
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-4935= 04058890547p1=C2=A0 =C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 = =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cache
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-493504058890547p2=C2= =A0 =C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 = =C2=A0 =C2=A00

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0NAME=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0STATE=C2=A0 =C2=A0 =C2=A0READ WRITE CKSUM
=C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0space=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 DEGRADED=C2= =A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0raidz2-0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DEGRADED=C2=A0 =C2= =A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-WD-WCC4N4KLEZT7p4=C2=A0 ONLINE= =C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-WD-WCC4N1DF9DA2= p4=C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2= =A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-= WD-WX52D625R0NTp4=C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2= =A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0diskid/DISK-WD-WX52D625R2TPp4=C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00= =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0diskid/DISK-WD-WCC4N1PYJ3F8p4=C2=A0 OFFLINE=C2=A0 =C2= =A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0logs
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DI= SK-S649NL0T819360Vp2=C2=A0 =C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 = =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ca= che
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-S649NL0T819360V= p3=C2=A0 =C2=A0 ONLINE=C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A00=C2= =A0 =C2=A0 =C2=A00
---snip---

The offline marked partitions are o= n the same HD (the broken one). The
DISK-S649NL0T819360V device use as = log and cache in the second pool
causes the issue on 16-current.
On 16-current I get "uncorrectable parity/CRC error" messages on= boot
from the broken disk. I used this to get rid of those errors:
= ---snip---
# grep kern.cam /tmp/be_mount.MhLw/boot/loader.conf
kern.c= am.tur_timeout=3D"60"
kern.cam.inquiry_timeout=3D"60"= ;
kern.cam.modesense_timeout=3D"60"
---snip---

But t= he second pool ("space") fails to get imported. When I import it =
via "zpool import -m space" it shows me that the log and cach= e devices
(different partitions on the same hardware) are not available= .
This is the device in question as seen from 15-current:
---snip---<= br>nda0: <Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V>
nda0: Seri= al Number S649NL0T819360V
[1] nda0: nvme version 1.4
nda0: 953869MB (= 1953525168 512 byte sectors)
[1] GEOM: new disk nda0
...
[1] pass6= at nvme0 bus 0 scbus6 target 0 lun 1
pass6: <Samsung SSD 980 1TB 2B4= QFXO7 S649NL0T819360V>
pass6: Serial Number S649NL0T819360V
[1] pa= ss6: nvme version 1.4
---snip---

In case you need some info from = the 15- or 16-current BE, which info do
you need?

Bye,
Alexan= der.

--
http://www.Leidinger.net Alexander@Leidinger= .net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org=C2=A0 =C2= =A0 netchild@FreeBSD.org=C2=A0 : PGP 0x8F31830F9F2772BF


--
http://= www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:= //www.FreeBSD.org =C2=A0 =C2=A0netchild@FreeBSD.org =C2=A0: PGP 0x8F31830F9F2772BF
--000000000000d0827c06468d5538--