2 ms·
With care - and upgrading a test system or two first to re-familiarize myself - it's worked fine for me. Two tips: - Understand `gpart bootcode` (or equivalen
by bell-cot 3y ago
With care - and upgrading a test system or two first to re-familiarize myself - it's worked fine for me. Two tips:
- Understand `gpart bootcode` (or equivalents), and be really sure that your low-level bootcode gets upgraded.
- If you're running zfs, `zpool checkpoint` can give you a way to rewind the entire state of the pool to a prior point. Used with some care, it can be extremely useful. Or just reassuring, as your "Plan B".
- waynesonfire 3y agoThis is interesting. I was just playing around with a VM that had mirrored ZFS root and I wanted to test if I could boot from either mirror--it requires a bit of hand-holding since /etc/fstab seems to hard-code the gpt label of the boot device making it difficult to boot from the mirror without first changing that reference. I didn't realize this and went down a rabbit hole of trying to recreate boot partitions which I found interesting. With that said, I'm curious whether the upgrade procedure updates the bootcode on both drives in the mirror. --- Slight tangent. The reason for playing around on the VM was that when I installed FreeBSD, I selected the zfs root auto-fs feature. It created a zfs partition that spanned the entire disk which I later decided that I didn't want. My goal was to shrink the zroot, and I was able to accomplish that using zfs send / receive and re-creating the partition withe the desired size. Fun exercise. I need to revisit the installer to see if I'm able to provide any parameters to tune the size of the zroot. I really didn't want to create the filesystems manually from the installer shell.