From owner-freebsd-current@freebsd.org Mon Nov 20 21:47:27 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1C42DF64EA for ; Mon, 20 Nov 2017 21:47:27 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DEE06E941 for ; Mon, 20 Nov 2017 21:47:26 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id GtnEeh7J30PSoGtnGeX2Tu; Mon, 20 Nov 2017 21:39:55 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vAKLgKpm018222 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Nov 2017 16:42:20 -0500 (EST) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id vAKLgKa2018221; Mon, 20 Nov 2017 16:42:20 -0500 (EST) (envelope-from lausts) Date: Mon, 20 Nov 2017 16:42:20 -0500 From: Thomas Laus To: Warner Losh Cc: freebsd-current@freebsd.org Subject: Re: Loader.conf problem Message-ID: <20171120214220.GA18207@mail.laus.org> Reply-To: lausts@acm.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.1-RELEASE-p4 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfIZ3vxw8DnrpvSHEXEzEiPtwNkGqegAkL6HwesZXG22W8ePEd3BjNXN1+sMjGUBE0fsJwYIwGXHyPtNKPxb0tb/4+ZVk6YmcaRs5GO6ovMRQqhtlVvH6 tUKh9w23XgGLSWTxY743Nol+ofoMzQV5s8U+PSRCDqBN41jr87cy0uDbL/4dUwZQxt5iirBcS+ND3oGYaACkDqUHzWLjx3EJJsg= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2017 21:47:27 -0000 Warner Losh [imp@bsdimp.com] wrote: > On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus wrote: > > > I recently upgraded my FreeBSD-Current system today and did not fully > > understand the impact of changes to loader.conf. My system has a Geli > > encrypted ZFS pool. In the past whenever I screwed up, I was able to > > use 'Beadm' into boot the most recent good kernel or enter a shell to > > reread the UPDATING notes for a clearer understanding of what needs to > > be done before rebooting. > > > > Is my system recoverable or does it require wiping and reloading from a > > snapshot? If it is recoverable, how to do? > > > > My changes to the system hasn't changed how things work. Or at least > shouldn't have changed anything. If they do, that's likely a bug, and > likely my fault. > > The one exception is if you're booting off GELI + ZFS with UEFI based on > boot1.efi changes that were in the tree for a few days... > This PC is not using UEFI to boot. After booting I get the following message: gptzfsboot: No ZFS pools located; Cant't boot That is as far as things go. I read the UPDATING file before I builtworld and built a kernel. This was the first boot after doing an installworld and performing mergemaster and then copying the /boot/gptzfsboot file to ada0p1 and ada1p1. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF