mlaurie

I have figured it out. In 7.3.0 rc.1 I created a pool named mirrored_pool using the remaining space on the boot drives. Apparently in 7.3.0 stable this became a reserved name which wreaked havok. ssh root@servername/ip cd /boot/config/pools rm mirrored_pool.cfg Back in your UnRAID gui. Stop the array Create a new pool with 2 slots. I chose server name_mirrored_pool assign the drives. Everything appears to have come back. Looks like the entire issue is that I just so happened to use a reserved name for the pool that wasn't reserved when I made the pool.

Expected BehaviorBoot pool listed Actual BehaviorIt’s not Steps to ReproduceInstall 7.3.0 Additional ContextPrior to 7.3.0 stable I was running rc.1. I had moved to internal boot and TPM licensing. I installed 2 new matching 1Tb NVMe specifically for this purpose. I used the included tool to setup a mirrored 128 gig partition for boot. I then created a second btrfs partition using the remaining space. After updating to stable, the boot pool list is empty and the drives show as unassigned. zpool status below: Screenshot of Main tab: WorkaroundsHave not found any fixes or work arounds yet. I tried using the bug report system but it keeps giving me an error about requiring a version field being filled but the field simply doesn't exist.