From nobody Tue Feb 1 09:02:55 2022 X-Original-To: freebsd-stable@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 9D66619ADF94 for ; Tue, 1 Feb 2022 09:03:15 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JnzVV0MlYz4WP9; Tue, 1 Feb 2022 09:03:14 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mail-wr1-f51.google.com with SMTP id f17so30579329wrx.1; Tue, 01 Feb 2022 01:03:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zBlU403YqiakvszUjp9GbZI7F9bX0oOAeNi52Za343o=; b=k1aYGuYf1E5AhBt67EGClPV3F1oyk0O+si09Wqu90X2oyzdbfv8N6VekxEAFO/G7CA spgE+spOhaaVQC8m9i2sJBuJKl2V3DpArrtVtRHavXn/Vl3fqkEgXwgRsbh/43uPMrIh uaXZIIzqbnthTglhYcroCYoNDfLPc8slUWKVQdyYgFWMmbrMtJt7HWuaoY8S/Lb0uOB2 EB2QWFBeLCmJQ016i93nNTDcXRb6iyoxovILTMvxdqGFU5R+MnJsIoCf1k/08V0FMDZ6 IxCaRt0r3W4epJcai3kbxY+WHvJcdYw1946mJPY1RIF4hlTOmwO4FbAKrDLDLHvB6YNg Yeeg== X-Gm-Message-State: AOAM530+FIH7jCnGSMbExdxoz4LG1jbFnpt1OzWVjdA6x3HG+52cCqye bgZS8mnUvAznghyLJFyRc11Yn7iHoBEcvu6f0h2IG3Bv4Js= X-Google-Smtp-Source: ABdhPJyKDxsiUFzxgU9BS5RXVEwohELB1RMi/v4Lf5UCp+plhMBnQ3hXiDmLpi78Rg9Hrll3ZMD3+dk3Qt0i6TKYsCo= X-Received: by 2002:adf:a1d3:: with SMTP id v19mr21138936wrv.303.1643706186908; Tue, 01 Feb 2022 01:03:06 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <212cfd90-056f-d294-ae9c-fd2b632ae679@FreeBSD.org> <20220130030618.dd46cf514f98cdfa6caa1ad4@dec.sakura.ne.jp> <275959c1-60e0-623b-6e95-f892d7ab8566@FreeBSD.org> In-Reply-To: <275959c1-60e0-623b-6e95-f892d7ab8566@FreeBSD.org> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Tue, 1 Feb 2022 10:02:55 +0100 Message-ID: Subject: Re: gptzfsboot can't boot from 4TB SSD To: Andriy Gapon Cc: Tomoaki AOKI , Eugene Grosbein , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4JnzVV0MlYz4WP9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of uspoerlein@gmail.com designates 209.85.221.51 as permitted sender) smtp.mailfrom=uspoerlein@gmail.com X-Spamd-Result: default: False [-0.30 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-0.87)[-0.868]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.51:from]; MLMMJ_DEST(0.00)[freebsd-stable]; FORGED_SENDER(0.30)[uqs@freebsd.org,uspoerlein@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.51:from]; R_DKIM_NA(0.00)[]; R_MIXED_CHARSET(0.56)[subject]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[uqs@freebsd.org,uspoerlein@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Sat, Jan 29, 2022 at 11:43 PM Andriy Gapon wrote: > > On 29/01/2022 23:49, Ulrich Sp=C3=B6rlein wrote: > > This output is from_before_ loader is loaded > > What gives you confidence in that? > Do you know exact moment where execution passes from gpt(zfs)boot to load= er? Huh, you are right. strings(1) confirmed that the messages could come from both gptzfsloader as well as from loader. My assumption was that the version string of the loader would be printed as early as possible, but now that I've opened stand/i386/loader/main.c, I see that bootprog_info gets printed very, very late in the process, after all the GPT and ZFS frobbing was already done, though I don't see an obvious, definitive call to probing ZFS there and then, it only sets up some stuff. Anyway, that mystery will have to wait for some other time Cheers Uli