From nobody Wed Feb 23 23:00:21 2022 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 88D5119D40FE; Wed, 23 Feb 2022 23:00:32 +0000 (UTC) (envelope-from makc@freebsd.org) Received: from mail.issp.ac.ru (mail.issp.ac.ru [77.236.34.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.issp.ac.ru", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K3s2R3RbZz4j6h; Wed, 23 Feb 2022 23:00:31 +0000 (UTC) (envelope-from makc@freebsd.org) Received: from 109-252-119-165.nat.spd-mgts.ru [109.252.119.165:7394] (HELO/EHLO mercury.localnet, authenticated with PLAIN) by mail.issp.ac.ru with ESMTPSA/inet id 21NN0M0q083332 (using TLSv1.2, with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits), verified NO) Thu, 24 Feb 2022 02:00:22 +0300 (MSK) X-Authentication-Warning: mail.issp.ac.ru: Host 109-252-119-165.nat.spd-mgts.ru [109.252.119.165] (may be forged) claimed to be mercury.localnet From: Max Brazhnikov To: FreeBSD Stable Mailing List , stable@freebsd.org Cc: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: bootcode update after zpool upgrade Date: Thu, 24 Feb 2022 02:00:21 +0300 Message-ID: <2400731.0dHE6SNnxz@mercury> In-Reply-To: References: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4K3s2R3RbZz4j6h X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 77.236.34.3 is neither permitted nor denied by domain of makc@freebsd.org) smtp.mailfrom=makc@freebsd.org X-Spamd-Result: default: False [-0.75 / 15.00]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[makc]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_MEDIUM(0.24)[0.237]; NEURAL_HAM_LONG(-0.89)[-0.886]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MLMMJ_DEST(0.00)[stable,freebsd-stable]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42317, ipnet:77.236.32.0/20, country:RU]; RCVD_COUNT_TWO(0.00)[2]; CTE_CASE(0.50)[]; RECEIVED_SPAMHAUS_PBL(0.00)[109.252.119.165:received] X-ThisMailContainsUnwantedMimeParts: N On Wed, 23 Feb 2022 23:40:42 +0100 Miroslav Lachman wrote: > I did "zpool upgrade tank0" on one of our machines with FreeBSD 12.2-p13 > amd64 and then got this message: > > # zpool upgrade tank0 > This system supports ZFS pool feature flags. > > Enabled the following features on 'tank0': > large_dnode > spacemap_v2 > allocation_classes > > If you boot from pool 'tank0', don't forget to update boot code. > Assuming you use GPT partitioning and da0 is your boot disk > the following command will do it: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 > > > > I am not sure what I should update. This machine is EFI boot only (this > is the only one EFI machine we have). > > # gpart show > => 40 1953525088 nvd0 GPT (932G) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 113624 - free - (55M) > 524288 20971520 3 freebsd-swap (10G) > 21495808 1932001280 4 freebsd-zfs (921G) > 1953497088 28040 - free - (14M) > > => 40 1953525088 nvd1 GPT (932G) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 113624 - free - (55M) > 524288 20971520 3 freebsd-swap (10G) > 21495808 1932001280 4 freebsd-zfs (921G) > 1953497088 28040 - free - (14M) > > Should I run: > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 nvd0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 nvd1 > > Or should I update EFI partitions? (if so, then how?) see https://www.freebsd.org/cgi/man.cgi?query=loaderupdate loaderupdate comes with ports-mgmt/bsdadminscripts2 > > This machine is very problematic with booting and mounting NVME disks. > They are not visible until I disabled PCI hot plug with > hw.pci.enable_pcie_hp="0" in /boot/loader.conf > > This is production machine so I would really like to do it right and not > make it unbootable. > > Kind regards > Miroslav Lachman > >