Date: Sat, 23 Jan 2021 20:52:44 -0800 From: John Kennedy <warlock@phouka.net> To: mike tancsa <mike@sentex.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: upgrade from releng12 to releng13 Message-ID: <YAz9HKgmhcAQTM1m@phouka1.phouka.net> In-Reply-To: <8e7a9688-b6ab-14b5-1413-c26e3cf99d0e@sentex.net> References: <8e7a9688-b6ab-14b5-1413-c26e3cf99d0e@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 23, 2021 at 03:59:07PM -0500, mike tancsa wrote: > I noticed when doing a src upgrade on a test zfs machine, I didnt > get prompted to re-install the boot blocks after upgrading the pool post > first reboot. I got a whole mess of feature upgrades just fine, but do > I not need to do a > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i <appropriate index> <drive> as well ? I don't know if it's written anywhere, but I always upgrade my bootloader before I do a zpool upgrade, just in case. If the loader doesn't know how to deal with an option it finds, it may bail which will require you to recover the system some other way (probably boot on some other media and upgrade your bootloader). When the OpenZFS stuff was installed, /usr/src/UPDATING mentioned issues (like not upgrading root pools until zstd was supported by the loader), so I'd be sure to track that for potential gotchas. I seem to recall that they yanked that warning out because it was wrong for UEFI systems (vs BIOS).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YAz9HKgmhcAQTM1m>