From owner-freebsd-stable@freebsd.org Thu Jul 9 14:10:51 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 48C6236C35F for ; Thu, 9 Jul 2020 14:10:51 +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 4B2dPR1Fylz45qV for ; Thu, 9 Jul 2020 14:10:51 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) (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 06A9423248 for ; Thu, 9 Jul 2020 14:10:51 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f173.google.com with SMTP id b25so1754548qto.2 for ; Thu, 09 Jul 2020 07:10:51 -0700 (PDT) X-Gm-Message-State: AOAM532+kGm+pfW48S3afI+MMKW8fEQnKiJqYbEwLocRR+VGj/h3tzKC tnnGALrG6LCyV7iptPDzEWT/g0KWfPFNjptwGyU= X-Google-Smtp-Source: ABdhPJyUsNIn5CizYpE6YEbugonTTIlWWgSGMzD0eo9XUFNhQ8V390a3eB3BimhVjC5Fh9Z3q2bifp6vVoHrFAJTI4Q= X-Received: by 2002:ac8:4b47:: with SMTP id e7mr67394714qts.242.1594303850450; Thu, 09 Jul 2020 07:10:50 -0700 (PDT) MIME-Version: 1.0 References: <20200709131201.GA3464@co.gvr.org> <78084555-7caf-d3db-0894-2fccce4bf249@ingresso.co.uk> In-Reply-To: <78084555-7caf-d3db-0894-2fccce4bf249@ingresso.co.uk> From: Kyle Evans Date: Thu, 9 Jul 2020 09:10:39 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 12.1p7 no longer boots after doing zpool upgrade -a To: 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: Thu, 09 Jul 2020 14:10:51 -0000 On Thu, Jul 9, 2020 at 8:50 AM Pete French wrote: > > > > On 09/07/2020 14:36, Kyle Evans wrote: > > We haven't quite standardized on a good process yet, IMO, but for > > right now the correct process is to just mount the ESP and replace > > loader.efi with your system's updated /boot/loader.efi. At some point > > we'll standardize a mountpoint for the ESP and mount it by default as > > is done on at least some other OS. > > Ok, that makes sense. Still curious as to why the other method might > fail though - as Karl points out in the other email, its just doing a > direct copy of the image file, so if the iamge is built correct then I > am surprised it wont work under all circumstances. > Yeah, so there's two problems here: 1.) That image is not built the way >= 12.x installations operate by default. It will install an ESP with an \EFI\BOOT\BOOTx64.EFI (or something like this) while we now, by default, setup \EFI\FreeBSD\loader.efi and the appropriate efibootmgr to point at it. In the former setup, that's actually /boot/boot1.efi which may or may not do GELI correctly in the new world order -- I don't recall, it's kind of special. 2.) That invocation clobbers anything else that might've been trying to reside on your ESP. If you had any kind of dual-boot setup going (perhaps rEFInd + grub + freebsdloader) then you've immediately hosed it by overwriting the partition completely. Thanks, Kyle Evans