Date: Fri, 24 Nov 2023 18:25:20 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: mike tancsa <mike@sentex.net> Cc: Matthew Seaman <matthew@FreeBSD.org>, questions@freebsd.org Subject: Re: Upgrade form 13.2-RELEASE-p5 to 14.0-RELEASE took almost 24hours Message-ID: <20231124182520.9c48d2c6e659f723b7d6f5ed@sohara.org> In-Reply-To: <3e7bb90b-1f11-4937-9623-2d9c94621cc9@sentex.net> References: <93C2E7DA-5E04-454B-9532-318292EEAE9A@tellme3times.com> <aa80633d-dd2d-42c7-9013-66694f6bdf61@sentex.net> <baff4e67-801a-4d58-9791-151089953fb5@FreeBSD.org> <3e7bb90b-1f11-4937-9623-2d9c94621cc9@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Nov 2023 12:51:14 -0500 mike tancsa <mike@sentex.net> wrote: > I am very glad it doesn't. There was an thread (the one about the docs) > that seemed to imply this just happened as part of the upgrade process > without user intervention. To be completely clear not only does the zpool upgrade not happen as part of the OS upgrade but also the fatal reboot does not happen as part of the zpool upgrade or (usually - but it can) without user intervention. The advice to update boot blocks first is VERY good advice but failing that not doing so before rebooting is a great way of making life difficult. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231124182520.9c48d2c6e659f723b7d6f5ed>