Date: Sun, 2 Aug 2020 00:32:10 -0400 (EDT) From: doug <doug@fledge.watson.org> To: David Christensen <dpchrist@holgerdanske.com> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update - Cannot identify running kernel Message-ID: <alpine.BSF.2.20.2008020006480.79190@fledge.watson.org> In-Reply-To: <78c7d012-8c82-a25a-e70d-6a09d0098bad@holgerdanske.com> References: <alpine.BSF.2.00.2008012000320.83675@bucksport.safeport.com> <alpine.BSF.2.20.2008012027010.79190@fledge.watson.org> <78c7d012-8c82-a25a-e70d-6a09d0098bad@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 1 Aug 2020, David Christensen wrote: > 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 > <INTEL SSDSC2CW060A3 400i> 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 Thank you. All the systems I have that use zfs I either did the default zfs install or they are the way they came from the manufacturer. This system has no data on it so I can experiement away. I had assumed the bootpool pool came from freebsd-update. I do not remember that /boot was a symlink bur was wasn't really paying any attention to that. I appreciate all the info. From owner-freebsd-questions@freebsd.org Sun Aug 2 06:32:48 2020 Return-Path: <owner-freebsd-questions@freebsd.org> 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 60C283733CE for <freebsd-questions@mailman.nyi.freebsd.org>; Sun, 2 Aug 2020 06:32:48 +0000 (UTC) (envelope-from doug@safeport.com) Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by mx1.freebsd.org (Postfix) with ESMTP id 4BKB5p72cGz48Tp for <freebsd-questions@freebsd.org>; Sun, 2 Aug 2020 06:32:46 +0000 (UTC) (envelope-from doug@safeport.com) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id EC9C161447; Sun, 2 Aug 2020 06:23:56 +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 0726Nuc5020566; Sun, 2 Aug 2020 02:23:56 -0400 (EDT) (envelope-from doug@safeport.com) Received: from localhost (doug@localhost) by fledge.watson.org (8.15.2/8.15.2/Submit) with ESMTP id 0726Nu0m020563; Sun, 2 Aug 2020 02:23:56 -0400 (EDT) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Sun, 2 Aug 2020 02:23:56 -0400 (EDT) From: doug@safeport.com X-X-Sender: doug@fledge.watson.org Reply-To: doug@fledge.watson.org To: David Christensen <dpchrist@holgerdanske.com> cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update - Cannot identify running kernel In-Reply-To: <alpine.BSF.2.20.2008020006480.79190@fledge.watson.org> Message-ID: <alpine.BSF.2.20.2008020214280.79190@fledge.watson.org> References: <alpine.BSF.2.00.2008012000320.83675@bucksport.safeport.com> <alpine.BSF.2.20.2008012027010.79190@fledge.watson.org> <78c7d012-8c82-a25a-e70d-6a09d0098bad@holgerdanske.com> <alpine.BSF.2.20.2008020006480.79190@fledge.watson.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 X-Rspamd-Queue-Id: 4BKB5p72cGz48Tp X-Spamd-Bar: +++++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=fail (mx1.freebsd.org: domain of doug@safeport.com does not designate 204.107.128.30 as permitted sender) smtp.mailfrom=doug@safeport.com X-Spamd-Result: default: False [7.02 / 15.00]; ARC_NA(0.00)[]; R_SPF_FAIL(1.00)[-all:c]; HAS_REPLYTO(0.00)[doug@fledge.watson.org]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.43)[0.426]; REPLYTO_DN_EQ_FROM_DN(0.00)[]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; HAS_XAW(0.00)[]; NEURAL_SPAM_MEDIUM(0.32)[0.323]; DMARC_NA(0.00)[safeport.com]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; VIOLATED_DIRECT_SPF(3.50)[]; CTYPE_MIXED_BOGUS(1.00)[]; FROM_NO_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.77)[0.769]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:11288, ipnet:204.107.128.0/24, country:US]; GREYLIST(0.00)[pass,body] X-Spam: Yes Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 02 Aug 2020 06:32:48 -0000 On Sun, 2 Aug 2020, doug wrote: > On Sat, 1 Aug 2020, David Christensen wrote: > >> 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 >> <INTEL SSDSC2CW060A3 400i> 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 > > Thank you. All the systems I have that use zfs I either did the default zfs > install or they are the way they came from the manufacturer. This system > has no data on it so I can experiement away. I had assumed the bootpool > pool came from freebsd-update. I do not remember that /boot was a symlink > bur was wasn't really paying any attention to that. I appreciate all the > info. The problem of freebsd-update not working was caused by the absense of /boot. The fix is, as suggested above, make /boot a symlink to /bootpool/boot. I absoluted verified this as my first attempt was to copy /bootpool/boot --> /boot. I then updated 12.0 --> 12.1. However this boots 12.0. Apparently from posts not all 12.x systems have /bootpool/boot. From owner-freebsd-questions@freebsd.org Sun Aug 2 09:04:02 2020 Return-Path: <owner-freebsd-questions@freebsd.org> 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 85DB5377033 for <freebsd-questions@mailman.nyi.freebsd.org>; Sun, 2 Aug 2020 09:04:02 +0000 (UTC) (envelope-from jacques+freebsd@foucry.net) Received: from mail.foucry.net (fournil.foucry.net [95.217.83.231]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BKFSK0Rt4z4Ftm for <freebsd-questions@freebsd.org>; Sun, 2 Aug 2020 09:04:00 +0000 (UTC) (envelope-from jacques+freebsd@foucry.net) Received: from mithril.localdomain (2a01cb0400bb09004aa472fffe9e65a1.ipv6.abo.wanadoo.fr [IPv6:2a01:cb04:bb:900:4aa4:72ff:fe9e:65a1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.foucry.net (Postfix) with ESMTPSA id C1B211BE70 for <freebsd-questions@freebsd.org>; Sun, 2 Aug 2020 09:03:43 +0000 (UTC) Received: from mithril (localhost [IPv6:::1]) by mithril.localdomain (Postfix) with ESMTP id F36D413088 for <freebsd-questions@freebsd.org>; Sun, 2 Aug 2020 11:03:42 +0200 (CEST) Date: Sun, 2 Aug 2020 11:03:42 +0200 From: Jacques Foucry <jacques+freebsd@foucry.net> To: freebsd-questions@freebsd.org Subject: poudriere check-sanity failed Message-ID: <20200802090342.GA24415@mithril> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4BKFSK0Rt4z4Ftm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=foucry.net; spf=pass (mx1.freebsd.org: domain of jacques@foucry.net designates 95.217.83.231 as permitted sender) smtp.mailfrom=jacques@foucry.net X-Spamd-Result: default: False [-2.56 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.99)[-0.988]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_HAM_SHORT(-0.27)[-0.274]; DMARC_POLICY_ALLOW(-0.50)[foucry.net,none]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:95.217.0.0/16, country:DE]; TAGGED_FROM(0.00)[freebsd] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 02 Aug 2020 09:04:02 -0000 Hello friends, This morning I launch the update of my poudriere's packages ` poudriere bulk -j 12-1 -p 12-1 -f /usr/local/etc/poudriere.d/12-1.lst ` And it faile on sqlite3 `[00:00:56] Failed ports: databases/sqlite3:check-sanity` and all packages depending of sqlite3 faileѕ too. I did not find any comprehensive explainantion or solution. As experiented admins, you should already have this issue and may a solution. What's your advices? Thanks in advance and an lite bit late Happy Sysadmin day -- Jacques Foucry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2008020006480.79190>