One of the few #sysadmin things that worries me any more is updating boot code after a zpool upgrade.

[mwl@io.mwl.io]

One of the few #sysadmin things that worries me any more is updating boot code after a zpool upgrade. #FreeBSD

I'm sure it'll be fine, but if I disappear forever you know what happened.

[seanwbruno@infosec.exchange]

@mwl it has never caused me drama, but there is a bit of “clench” when I issue that reboot to test.

[jeanmimi@mamot.fr]

@mwl if you bootstrap, you will fly

[peteorrall@mastodon.bsd.cafe]

@mwl Good luck!

[raven@fedi.raventhemaker.com]

@mwl breathe...

[djfiander@code4lib.social]

@mwl I always forget that, then freak out when the next boot fails

[djb@social.shirow.net]

@mwl I should have checked the errata. The 5.0 had a problem with iLO devices and wouldn’t boot. So yes, it’s the only time I’ve borked a FreeBSD upgrade

[sko@bsd.network]

@mwl since I have mirrored boot devices on pretty much all zfs systems, I also have two efi and boot partitions - so on systems I'm paranoid about keeping bootable at all cost, I only update bootcode on one set of boot/efi partitions.
If it goes wrong, I boot from the second drive and restore boot&efi from there; otherwise the second drive also gets the updated bootcode after sucessfully booting with that.

[tallsimon@mstdn.ca]

@mwl Just get an extra long ethernet cable and tie it off to the server rack before you go down the rabbit hole. If you need help, tug it three times.