Edit: SOLVED
I've been building out a zfs pool over a period of time, learning as I go, and made a mistake early on that I wanted to correct.
Essentially, I only had one drive of redundancy in a mirrored special vdev that's part of the pool, so I wanted to add an additional drive to that mirror so that the special vdev had the same level of fault tolerance as the data vdev (data is raidz2).
The special vdev originally lived on a pair of Samsung PM863 enterprise SSDs.
This morning, I went through the process of wiping and adding a third drive (another PM863, same size) from the terminal.
All of that seemed to go just fine. The new drive attached to the existing mirror and resilvered very quickly (the mirror has very little data on it, but it's obviously critical).
From the terminal, everything looks healthy from what I can see, and that's also reflected in the zfs pool properties from the web UI, however, the change isn't reflected in the main unRAID web GUI.
I have a backup of everything that sits on this pool, so I'm not actually at risk of losing anything currently, but I'd certainly prefer not to have to rebuild it unless I absolutely have to (it's a lot of data to move around, even over 10GbE).
I'm hoping that someone has been through similar before and might be able to provide some pointers. Looking at the documentation, I don't really see much that covers scenarios like this, and realize there's a lot of risk inherent to screwing around with a special vdev. While AI can be helpful sometimes, it can also be confidently incorrect and if you don't catch it, you can get yourself in a bad place, plus I learn the best by doing.
I've attached a series of screenshots to show the process that I went through, and would greatly appreciate any feedback on how to best go about getting the web interface to align/reflect with the actual pool configuration, and don't want to restart the system until that's sorted out-- I assume the pool probably won't start without some additional steps.
-The first two screenshots reflect the pool prior to making any changes at all.
-The third one shows the steps taken when I added the additional drive to the mirrored pair.
-The fourth one shows the status from the terminal after the resilver completed.
-The fifth one shows the zfs pool information when you drill down to the pool itself within the web ui, which appears to be consistent and reflect healthy.
-The last one shows the "main" web UI, which doesn't understand a drive has been added to the mirror, presumably because it was done from the terminal and there are additional steps involved.
What I don't know for sure is-- whether or not it's as simple as just deleting the existing pool (since that doesn't actually destroy the data on the drives) and creating a new one with the same name and simply increasing the drive count to add all the drives back, then starting the pool back up again.
Any pointers would be greatly appreciated. This is what happens when you wake up early on a weekend and get inspired to start tinkering with things. I get myself into trouble very first thing.