Did you do another 'freebsd-update install' after the reboot?
user@server:~ $ gpart show nda0 nda1
=> 40 1000215136 nda0 GPT (477G)
40 532480 1 efi (260M)
532520 1024 2 freebsd-boot (512K)
533544 984 - free - (492K)
534528 4194304 3 freebsd-swap (2.0G)
4728832 995485696 4 freebsd-zfs (475G)
1000214528 648 - free - (324K)
=> 40 1000215136 nda1 GPT (477G)
40 532480 1 efi (260M)
532520 1024 2 freebsd-boot (512K)
533544 984 - free - (492K)
534528 4194304 3 freebsd-swap (2.0G)
4728832 995485696 4 freebsd-zfs (475G)
1000214528 648 - free - (324K)
user@server:~ $ zpool status
pool: poolname
state: ONLINE
scan: scrub repaired 0B in 00:00:28 with 0 errors on Sat Oct 28 04:46:03 2023
config:
NAME STATE READ WRITE CKSUM
poolname ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
nda0p4.eli ONLINE 0 0 0
nda1p4.eli ONLINE 0 0 0
errors: No known data errors
It has to be done on both disks. If you only updated nda0 the system is going to fail to boot if that drive fails.
It's not the same filesystem. The efi partition isn't mirrored. Only your ZFS pool is. Besides that, a BIOS/UEFI has no notion of mirrors, RAID or anything like that. It only loads stuff from a single disk. Don't have to keep this mounted in any case, only mount the efi partition if/when you update the boot code. Just leave it unmounted the rest of the time.
# mount -t msdosfs /dev/nda0p1 /boot/efi worked just fine, but # mount -t msdosfs /dev/nda1p1 /boot/efi was giving an invalid fs type error (or something, I've already closed the kvm window so I can't verify). Verified several times that I ran the command correctly too, even paging up to the nda0 command I'd previously run and just arrowing over to replace the 0 with a 1. nda0p1 first, but I think it still would have mounted over top of it even so.root@server:~ # mount -t msdosfs /dev/nda1p1 /boot/efi
mount_msdosfs: /dev/nda1p1: Invalid argument
root@server:~ # mount -t msdosfs /dev/nda0p1 /boot/efi
mount_msdosfs: /dev/nda0p1: Operation not permittedThere was a bug in the installer that would never write the efi boot code on the second disk of a mirrored installation. Just newfs_msdos(8) it, and set up the same directory structure.
# dd if=/dev/nda0p1 of=/dev/nda1p1 or would I need to actually set it up by hand? I'll need to do this again on a server with 6 bootable disks later when I get home so that would be more expedient for me.
I had the same habit (a single command), can't recall where it was learnt, I'll no longer promote it.
Probably better to run two separate commands, as shown in installation files.
Graham Perrin (@grahamperrin@bsd.cafe)
Attached: 2 images freebsd-update fetch install – did not install an update from (end of life) FreeBSD 13.1-RELEASE-p3 to 13.1-RELEASE-p9. It was necessary to run a different command before proceeding (with an upgrade): freebsd-update install #FreeBSD #updatemastodon.bsd.cafe
freebsd-update fetch && freebsd-update install and freebsd-update fetch install and would't that be a violation of POLA?
install preceded by fetch in the same invocation
parse_cmdline () {
while [ $# -gt 0 ]; do
case "$1" in
# Commands
cron | fetch | upgrade | updatesready | install | rollback |\
IDS | showconfig)
COMMANDS="${COMMANDS} $1"
;;
esac
shift
doneget_params $@
for COMMAND in ${COMMANDS}; do
cmd_${COMMAND}
done
somefunc () {
if somecondition exit 1
if othercondition return 2
# implicitly return (0)
}You're not having any AC in Nimbin ?
freebsd-update here, it's just a matter of "don't ignore what the program is telling you"?