by incumbent » Mon Feb 10, 2025 10:58 am
I am updating `/etc/synthetic.conf` and about to give it a go. Last major OS release and openzfs package update I had a real adventure.
I inadvertently got greedy and wasn't paying attention and probably `zpool import -d` or something and wound up importing a mechanical pool of a single mirrored pair of 12TB disks as if it were my primary NVME pool, and as the filesystems mounted I about lost my entire mind but was able to export and annotate all the disks that match which pool via `diskutil list` and very deliberately imported the pools back with great gear to device uuid mappings. It felt very harrowing but I managed to recover gracefully after a reboot.
In case anyone is wondering why I use synthetic.conf - I make use of `/etc/synthetic.conf` to allow for a wide variety of mountpoints off `/` like `/localmedia/` `/av/` `/research/` `nethomes` etc. To create them and for apfs/jhfs I define them but you can get away with just setting `mountpoint=` values on your datasets and they'll get hitched up where they belong.
The NVME pool periodically sends itself to the mechanical pool, adding to my confusion ><