From owner-freebsd-questions@freebsd.org Sun Aug 2 00:31:35 2020 Return-Path: Delivered-To: freebsd-questions@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 AC725368F14 for ; Sun, 2 Aug 2020 00:31:35 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by mx1.freebsd.org (Postfix) with ESMTP id 4BK2524jkfz3b08 for ; Sun, 2 Aug 2020 00:31:34 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 2CD5863796 for ; Sun, 2 Aug 2020 00:31:28 +0000 (UTC) Received: from fledge.watson.org (doug@localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.15.2/8.15.2) with ESMTP id 0720VREY013255 for ; Sat, 1 Aug 2020 20:31:27 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id 0720VRlu013252 for ; Sat, 1 Aug 2020 20:31:27 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Sat, 1 Aug 2020 20:31:27 -0400 (EDT) From: doug Reply-To: doug@safeport.com To: freebsd-questions@FreeBSD.ORG Subject: Re: freebsd-update - Cannot identify running kernel In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 4BK2524jkfz3b08 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of doug@fledge.watson.org has no SPF policy when checking 204.107.128.30) smtp.mailfrom=doug@fledge.watson.org X-Spamd-Result: default: False [2.85 / 15.00]; HAS_REPLYTO(0.00)[doug@safeport.com]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.00)[0.001]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_SPAM_MEDIUM(0.86)[0.861]; NEURAL_SPAM_LONG(0.98)[0.984]; DMARC_NA(0.00)[watson.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11288, ipnet:204.107.128.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Aug 2020 00:31:35 -0000 On Sat, 1 Aug 2020, Doug Denault wrote: > I did an update from 11.3 --> 12.1 that did not seem to work. That turned out > to be my error but I rolled back to 11.3. I have a 12.0 system that did not > have the error so I thought I would update to 12.0 to try to get a handle on > my problem. > > This update did not exactly work. It will boot and I suspect I can do > anything not requiring access to /boot. The zfs boot process is not bothered > by this problem. > > zpool list > NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH > ALTROOT > bootpool 1.98G 274M 1.72G - - 15% 13% 1.00x ONLINE > - > zroot 920G 7.76G 912G - - 0% 0% 1.00x ONLINE > - > > zfs list > NAME USED AVAIL REFER MOUNTPOINT > bootpool 273M 1.59G 271M /bootpool > zroot 7.76G 883G 96K /zroot > zroot/ROOT 5.15G 883G 96K none > zroot/ROOT/default 5.15G 883G 5.15G / > zroot/tmp 168K 883G 168K /tmp > zroot/usr 2.59G 883G 96K /usr > zroot/usr/home 682M 883G 682M /usr/home > zroot/usr/ports 742M 883G 742M /usr/ports > zroot/usr/src 1.20G 883G 1.20G /usr/src > zroot/var 12.5M 883G 96K /var > zroot/var/audit 96K 883G 96K /var/audit > zroot/var/crash 96K 883G 96K /var/crash > zroot/var/log 572K 883G 572K /var/log > zroot/var/mail 11.5M 883G 11.5M /var/mail > zroot/var/tmp 96K 883G 96K /var/tmp > > In comparing this with a zfs system I have not so abused, I can tell that > bootpool needs to be added to the zroot/ROOT/default as boot thus the file > system visible to the OS would have /boot in it. I know my terminology is > likely all messed up, I am a zfs newbie. > > Anyway bootpool/boot/ has the right stuff: > > ls bootpool/boot/ > ./ delay.4th loader.efi* menu.4th > ../ device.hints loader.rc menu.rc > beastie.4th dtb/ loader_4th* menusets.4th > boot efi.4th loader_4th.efi* modules/ > boot0 entropy loader_lua* pmbr > boot0sio firmware/ loader_lua.efi* pxeboot > boot1 frames.4th loader_simp* screen.4th > boot1.efi* gptboot loader_simp.efi* shortcuts.4th > boot1.efifat gptzfsboot logo-beastie.4th support.4th > boot2 isoboot logo-beastiebw.4th userboot.so > brand-fbsd.4th kernel/ logo-fbsdbw.4th userboot_4th.so > brand.4th kernel.old/ logo-orb.4th userboot_lua.so > cdboot loader* logo-orbbw.4th version.4th > check-password.4th loader.4th lua/ zfs/ > color.4th loader.conf mbr zfsboot > defaults/ loader.conf.orig menu-commands.4th zfsloader* > > So ... is my analysis correct? If so how do it put bootpool/boot/ where "it > belongs"? > So after some reading, I might be making more of this than it is. Seems to me because so little data is involved make /boot, copy the data and perhaps rename bootpool to something just to be safe. If so the next question is did freebsd-update leave anything else behind?