Date: Sun, 24 Jan 2021 07:24:35 -0500 From: mike tancsa <mike@sentex.net> To: John Kennedy <warlock@phouka.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: upgrade from releng12 to releng13 Message-ID: <d8e880ed-7ddc-0a42-a2d5-32dc7c41a2f4@sentex.net> In-Reply-To: <YAz9HKgmhcAQTM1m@phouka1.phouka.net> References: <8e7a9688-b6ab-14b5-1413-c26e3cf99d0e@sentex.net> <YAz9HKgmhcAQTM1m@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/23/2021 11:52 PM, John Kennedy wrote: > 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 seem to recall that they yanked that warning out because it was wrong > for UEFI systems (vs BIOS). As someone who reflexively once did that too ( -i 1 instead of -i 2) I think maybe using "appropriate index" or some other none specific number with the warning again, is probably better than having no warning. I too always do it after an upgrade, but I suspect this will just create a class of new "damn, I cant boot my server after a zfs upgrade because I forgot to upgrade the boot loader" users ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8e880ed-7ddc-0a42-a2d5-32dc7c41a2f4>