From owner-freebsd-questions@freebsd.org Sun Aug 2 01:29:54 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 8F8A136A48D for ; Sun, 2 Aug 2020 01:29:54 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [IPv6:2001:470:0:19b::b869:801b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.holgerdanske.com", Issuer "www.holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BK3NJ6w2qz3cmH for ; Sun, 2 Aug 2020 01:29:52 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (TLS_AES_128_GCM_SHA256:TLSv1.3:Kx=any:Au=any:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Sat, 1 Aug 2020 18:29:41 -0700 Subject: Re: freebsd-update - Cannot identify running kernel To: freebsd-questions@freebsd.org References: From: David Christensen Message-ID: <78c7d012-8c82-a25a-e70d-6a09d0098bad@holgerdanske.com> Date: Sat, 1 Aug 2020 18:29:41 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4BK3NJ6w2qz3cmH X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dpchrist@holgerdanske.com has no SPF policy when checking 2001:470:0:19b::b869:801b) smtp.mailfrom=dpchrist@holgerdanske.com X-Spamd-Result: default: False [2.86 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.12)[0.118]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.94)[0.943]; DMARC_NA(0.00)[holgerdanske.com]; NEURAL_SPAM_LONG(0.90)[0.899]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(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 01:29:54 -0000 On 2020-08-01 17:31, doug wrote: > On Sat, 1 Aug 2020, Doug Denault wrote: > >> I did an update from 11.3 --> 12.1 that did not seem to work. >> 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. I assume you mean "update to 12.1"? >> This update did not exactly work. It will boot and I suspect I can do >> anything not requiring access to /boot. On my system, /boot is a symlink; not a ZFS filesystem: 2020-08-01 18:10:51 toor@f3 ~ # freebsd-version ; uname -a 12.1-RELEASE-p7 FreeBSD f3.tracy.holgerdanske.com 12.1-RELEASE-p7 FreeBSD 12.1-RELEASE-p7 GENERIC amd64 2020-08-01 18:22:18 toor@f3 ~ # ll /boot lrwxr-xr-x 1 root wheel 13 2019/10/31 21:37:10 /boot@ -> bootpool/boot 2020-08-01 18:22:44 toor@f3 ~ # zfs list -r | egrep 'NAME|boot|/$' NAME USED AVAIL REFER MOUNTPOINT bootpool 372M 1.42G 190M /bootpool soho2_zroot/ROOT/default 4.23G 4.28G 2.22G / > 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 - So, a 1 TB HDD? I would use that for data. I put my systems on small SSD's: 2020-08-01 18:14:08 toor@f3 ~ # camcontrol devlist | grep ada0 at scbus0 target 0 lun 0 (ada0,pass0) >> So ... is my analysis correct? If so how do it put bootpool/boot/ >> where "it belongs"? Look for the symlink, as above. > 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. I have assumed 'bootpool' is hard coded into the bootloader(s), and renaming it will break boot. So, I have not tried renaming bootpool. I would advise taking an image of your system drive before proceeding, but an image of a 1 TB system drive could require a lot of storage (this is why I use small SSD's for system drives). > If so the next > question is did freebsd-update leave anything else behind? I keep my system configuration files in a version control system (CVS). I never do in-place OS major version upgrades. Instead, I make sure the system configuration files are checked in, stop services, backup the data, pull the system drive, insert a blank system drive, do a fresh install, update the OS, install packages, update the packages, check out the old configuration files to a side directory, configure the system as required, restore the data, and start services. David