From owner-freebsd-stable@freebsd.org Fri Jul 10 19:28:25 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DACA13714F5 for ; Fri, 10 Jul 2020 19:28:25 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B3NPP5PtRz3XjZ; Fri, 10 Jul 2020 19:28:25 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f51.google.com (mail-qv1-f51.google.com [209.85.219.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 97E0F10601; Fri, 10 Jul 2020 19:28:25 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f51.google.com with SMTP id di5so3096586qvb.11; Fri, 10 Jul 2020 12:28:25 -0700 (PDT) X-Gm-Message-State: AOAM531AYp3QD6SQGtQye7emB9WRK7+26QdBsnUG80D/4bQwrU6+300/ Z4NMpKq8k1eo1p+n75ma3q0LlVxNPWcd38HWYOM= X-Google-Smtp-Source: ABdhPJxnO8eQyRf/rVj12MY7R3Udykwh94xDpIBWVgv4m9DonKzhv1IjbmiotNxGQcmEP5R7TLYsmLlzB2JXvaZJ0Tk= X-Received: by 2002:a0c:fb47:: with SMTP id b7mr59276075qvq.129.1594409305197; Fri, 10 Jul 2020 12:28:25 -0700 (PDT) MIME-Version: 1.0 References: <20200709131201.GA3464@co.gvr.org> <20200710182903.GA7412@gvr.gvr.org> <20200710184446.GA8358@gvr.gvr.org> In-Reply-To: <20200710184446.GA8358@gvr.gvr.org> From: Kyle Evans Date: Fri, 10 Jul 2020 14:28:12 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 12.1p7 no longer boots after doing zpool upgrade -a To: Guido van Rooij Cc: Kyle Evans , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2020 19:28:25 -0000 On Fri, Jul 10, 2020 at 1:44 PM Guido van Rooij wrote: > > On Fri, Jul 10, 2020 at 08:29:03PM +0200, Guido van Rooij wrote: > > On Thu, Jul 09, 2020 at 08:24:54AM -0500, Kyle Evans wrote: > > > On Thu, Jul 9, 2020 at 8:12 AM Guido van Rooij wrote: > > > > > > > > I did a zpool upgrade -a to enable large_dnode and spacemap_v2. > > > > After that, I did: > > > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada0 > > > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada1 > > > > and: > > > > gpart bootcode -p /boot/boot1.efifat -i 1 ada0 > > > > gpart bootcode -p /boot/boot1.efifat -i 1 ada1 > > > > > > > > Now the system no longer boots from either disk and drops to the efi shell. > > > > > > This method of updating the ESP is no longer recommended for new 12.x > > > installations -- we now more carefully construct the ESP with an > > > /EFI/FreeBSD/loader.efi where loader.efi is /boot/loader.efi. You will > > > want to rebuild this as such, and that may fix part of your problem. > > > > Hi Kyle, > > > > Thnaks for your asnwer. I have not got it to work with that > > configuration. What did work was to replace the /efi/boot/BOOTx64.efi > > with loader.efi and and change the content of startup.nsh with > > loader.efi. Withoyt the above answer I wouldn't have figure it out > > that quickly so thanks! > > > > I will investigate further once I have more time (early next week probably). > > There was one question I forgot to ask: > Could I have known that my method of updating the ESP was not correct? > If so, where is this documented? > It is probably unlikely, to be honest. I don't know that we do a good job of advising people/documenting how to update the ESP. In fact, I have no idea where any of it's documented except the wiki: https://wiki.freebsd.org/UEFI >From your previous e-mail: > I did not set this sysctl so most likely that was the cause. As the system > is up and running again I didn't test it. > Let me know if you want me to. It's working now, so I wouldn't bother- this is probably the most likely cause, the pool's demonstrably intact based on your latest report. Thanks, Kyel EVans