From nobody Sun Dec 14 13:05:28 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 4dTk2Z44Kbz6K937 for ; Sun, 14 Dec 2025 13:05:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 4dTk2Z38l4z3dNt for ; Sun, 14 Dec 2025 13:05:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-34c30f0f12eso760423a91.1 for ; Sun, 14 Dec 2025 05:05:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1765717540; x=1766322340; 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=MgHZ7EZO0ElriHyXedIuF7Wd6hfgy23nP3yVQURRenE=; b=jT0NxiBNze3cLSXWXEkXZ69CrclCf+XuS1adZJj0vw+TAfrEc3AjD0M+lh5upEQYZG UGgdwDDZWd8iYdxTKhaYUUi8lg0TNWM5jLMpdg+AYIEi3ZGBamjP+pDXS3oSVw19QDBQ N1cW8KKrF0MVDNN+SrIzNtuVPgOrkAFG2LnnebHAjK93dxSh73GI0/HeIJ/7YX4MlTcf GiHrq9ljrDq92j4PL5w47eMykBr/59Z022lbcPBGrWjl46V81y7125Sx+mtUv3jy2NwV VUo98gKKCe9q9PV3F/uuBP90Bp0zBrSz/lGuckdRn7dygI18uy1VQG2q4vcUZkcuESiA 14nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765717540; x=1766322340; 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=MgHZ7EZO0ElriHyXedIuF7Wd6hfgy23nP3yVQURRenE=; b=TGDfKVjuOUFFv/jGcKbAtNVbEujvnMxKEoncNbwj59TA2dc/C7fEujcBg2WTJIvvXn H6C8g6e0wjRBa97eXR+3bJz06ybUhS4TXiwg3259LTW9yNS1ea+zbA5wXyuv0FD81QEY oQd6r5BmL/oS/f13Ipt0ZC+ZB7mTTsjdx9F3UwKxEENlV9GEN4C8LKlB038Ow98jrvbj /fBzZqu97/NAP4ytigdgYG6uNZIWT76VcmV/eNwR7MdtZaU3dEmKDlVM512gKbwjkCj/ IYkRmhZpwF0rrgnhFaNkw63jzKp8V6SV61iVkAxAS06rZVDUSJ6ARydSwh0O9dF/Uz30 lsmg== X-Gm-Message-State: AOJu0YwFdD2Er7Sf/etz8cTvZKwdqxK0lSYqy0ohIJinhDKmGv1IqQ4B juFV5H0wmcAnrftgi/nJ4OTE+R2CYeBRNVJ17COm6JV8K6UCiVLok+JDWGOfsSjd8I/ctNpinzq vXijXKEQ6cws4/sTsBuuV37PRvMCEa+99xp387vwMaCzX13utUr7g X-Gm-Gg: AY/fxX7+vGlXuDf14/kgYlvdfnti92UOf3Imi6/DEgP8Z9nijMBWwb39hty8vr3Y2Ha s0YcNUTlInDjZM3svzmjiZXoiep+GDxPTgC2XJGGmt906+7H6vMKUmQCrqWnzb29vWGblEQpaOv ReYtHkY+l63G6WM2cpMkOQ6DBngqxEZpbX3bleM2s0uQpY7umQRv/trCrGO5xzyDDOsUT8gZ3rU jEzZmIFBgzkRqvO05313qWqhQwEqyZWEJ2AMfPiIDYkqY85eVTHFxoUs+M/DScD5NAfnC77u2y3 QGMr8Mxa338VKQqDEXb9sz09qyuG X-Google-Smtp-Source: AGHT+IHaA2eSb9FNZj3329cQMpoNGkXURfWauL0PdOPL0ZlciTD4fKJF5/1LtG1cAepCslfjHQqT+2R0epRpozkE9E0= X-Received: by 2002:a17:90b:54c3:b0:33e:2934:6e11 with SMTP id 98e67ed59e1d1-34abd7f7a9cmr6016185a91.11.1765717539668; Sun, 14 Dec 2025 05:05:39 -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> In-Reply-To: <198170948d34f4dc169e94934da82161@Leidinger.net> From: Warner Losh Date: Sun, 14 Dec 2025 06:05:28 -0700 X-Gm-Features: AQt7F2ogCnIbiSHnV4Jwg4AIQVW6s8Ziv8jMRgm6jBhNTedtE8j7Ni0-Nq3t9R4 Message-ID: Subject: Re: Changes in cam/nvme causes issues? To: Alexander Leidinger Cc: Current Content-Type: multipart/alternative; boundary="000000000000b9d3b00645e926dd" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dTk2Z38l4z3dNt --000000000000b9d3b00645e926dd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 First, let's start with pciconf -l of the nvme drive. I have a strong idea, but need some data. 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 > --000000000000b9d3b00645e926dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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

First, le= t's start with pciconf -l of the nvme drive. I have a strong idea, but = need some data.

Also, th= e disk report needs full logs with and without the settings that have uncor= rectable in them. I'd expect that a shorter timeout would lead to diffe= rent behavior, but maybe that error syndrome isn't one I've seen. I= t would also be helpful to know which of the times changes the behavior...<= /div>

Warner

On Sun, Dec 14, 2025, 5:06=E2=80=AFAM Alexander Leidinger <Alexander@leidinger.net> wro= te:
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---
=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 DEGRA= DED=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-WCC4N4KLEZT7= p3=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= p3=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-WX52D625R0NT= p3=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-WCC4N1PYJ3F8= p3=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-493504058890547p1=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 DEGRA= DED=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-WCC4N4KLEZT7= 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-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-WX52D625R0NT= 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-WX52D625R2TP= 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-WCC4N1PYJ3F8= p4=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-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=A0cache
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0diskid/DISK-S649NL0T819360Vp3=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 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 impor= t it
via "zpool import -m space" it shows me that the log and cache de= vices
(different partitions on the same hardware) are not available.
This is the device in question as seen from 15-current:
---snip---
nda0: <Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V>
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: <Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V>
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 0x8F3= 1830F9F2772BF
http://www.FreeBSD.org=C2=A0 =C2=A0 netchild@FreeBSD.org=C2=A0 = : PGP 0x8F31830F9F2772BF
--000000000000b9d3b00645e926dd--