From owner-freebsd-current@freebsd.org Mon Nov 20 21:47:53 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 D9B49DF656A for ; Mon, 20 Nov 2017 21:47:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E4A06EA6C for ; Mon, 20 Nov 2017 21:47:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id q64so4428078iof.13 for ; Mon, 20 Nov 2017 13:47:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ztBICV7eePPgBiL+oOmBWWNPZ0hvGx9GqzD64QmnPeo=; b=1CI54ClzNYC7mc2VEy0oCClRUYnVgLl8PrC6dvFvgKrGkjuWKF9I7ThnSdpk+fR6bs J/m4ObHeQvJ3yw7kao8n2efydfF41iKcaN/S2WcWLoVTSMrFzwFJ/D5pwPVjkJIl/lZh VEYWwnQCi42KUwUzszkBmhVX67FrNl3yR4VIA0RqMh3oBxhVvpyY2ZGiyyBueE1U9SBZ ChpBPsAzAdidlN3u8b8QSoJSwyxnBUa5FEYIPGEmO7B//+fCyX175tHIugXi+v1r+Az4 ykZ7nHAgqfjqxg0RZGOwSfA60jDt/ccajv9zVcm/vC5GmIlXa0Ny4mCTA7a3NJ3sH7/h ebuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ztBICV7eePPgBiL+oOmBWWNPZ0hvGx9GqzD64QmnPeo=; b=O1eVlQTZttcLdrrN84AnkkxmesgMkOIfvEj0+I84/f0MPeYGbQv2pnTnfQCHfsXVHC Geuy6HUfax//h7sXuHMhI26jW/WvK9D2J4Npcq7LRlMnGoHdXy6b6ttaz3yO5V/V9rPU QSAj8JGKFUsNTtWMHnchOqED8TpqcLoGH8kVHysVgfptL/xWdiP+KkaN8ngJvi9CKLfa NaSfnM62NR9CpOpm1urETzZZFVCybLTBVS/nrBIDw1B5OGMPqUT7CGcwb1uL9ZGCZl33 UbD5IA4+C8aov/DSDNHTKt8rObn7n3B8o25PnQQns/GQ2htasFUF0lpAOSBUTIwt+b7B mnrA== X-Gm-Message-State: AJaThX7ExbyO4YGLxw4LZfL1lTIs22iyza1WdLaEv4YFLJY6AtNpXxS1 fZYD6agt4T9u2YiFGIMZ0haVLdBbEjbO9imLZqXMRQ== X-Google-Smtp-Source: AGs4zMZ4h37jQBI2Ar6TG17hL3/0a65xrGbt0QjZqZoozGubmKrbfV0owpAnuLzCcJPmKa2cbDDlEFCScL43fkC7S4I= X-Received: by 10.107.30.81 with SMTP id e78mr2511138ioe.130.1511214472902; Mon, 20 Nov 2017 13:47:52 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 20 Nov 2017 13:47:52 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:c91c:5e34:ef38:d5a] In-Reply-To: <20171120214220.GA18207@mail.laus.org> References: <20171120214220.GA18207@mail.laus.org> From: Warner Losh Date: Mon, 20 Nov 2017 14:47:52 -0700 X-Google-Sender-Auth: 7EMF2yxMXmed9M_U0DBDN-lChR4 Message-ID: Subject: Re: Loader.conf problem To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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:53 -0000 On Mon, Nov 20, 2017 at 2:42 PM, Thomas Laus wrote: > 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. Can you revert this part of the change? Go back to a known-working version of those files? Let me know if that fixes the problem? Bonus points for bisecting which one of the few dozen commits I did that caused this regression... I don't have a GELI + ZFS test bed here. Warner