From owner-freebsd-current@freebsd.org Mon Nov 20 20:33:23 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 CE40ADF4B64 for ; Mon, 20 Nov 2017 20:33:23 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) (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 8ED496BDC7 for ; Mon, 20 Nov 2017 20:33:23 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id GsiJecAf8XjiOGsiLetwL2; Mon, 20 Nov 2017 20:30:46 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id vAKKUgre018065 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 20 Nov 2017 15:30:43 -0500 (EST) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org To: freebsd-current@freebsd.org From: Thomas Laus Subject: Loader.conf problem Message-ID: Date: Mon, 20 Nov 2017 15:30:42 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfIvnIpfXRnKWsE6Zt9E/2d7hcOPqPF6gWqUPADGensP7ADWw/HFdKm703M+FAIPVG+rFQa3uJgXNx9S5kDF1w1sHlBsCvTDCAtE6t3i/6n+y9/POvj9I aOWRl2q3rVKU+9ED61MeamK89sGsf4Kg5WZQiVvipdsgQz8JNZTnvFrX 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 20:33:23 -0000 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? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF