Truenas keeps looking for pool that no longer exists
I lost power while replacing a drive, and now the Truenas GUI is, in technical terms, being a dick. When I go to the Storage page, I get an error that it can't import a temp pool:
That's fine. That was a temporary pool of a single disk I was using to host 1 VM. Except that that error seems to be holding up the GUI from doing anything else related to the storage. If I close that message, none of my pools are visible. Checking via CLI though, everything is working. My apps are running and all of my pools, EXCEPT temp are visible. So let's just get rid of temp and keep going, right?
zpool status shows all of my pools except temp. It's not there at all. zpool import/export/clear/destroy all say the same thing, "cannot open 'temp' : no such pool". Back in the GUI, I can go to Storage > Disks, and see the disk that temp lived on. I wipe it. I delete the single VM that was on that disk. I go back to the CLI, use wipefs and then labelclear to wipe anything to do with zfs from that disk. labelclear fails, but I believe that's because there was no label after wiping. I use zdb -l on each individual disk in my array and there is no mention of temp anywhere. I restart my truenas server, go to Storage, and still get the same error. ZFS seems to be working fine. But somewhere within truenas, it is stuck trying to find that pool and then halting anything else when it can't find it.
Any ideas?
Posted Aug 13, 2026, 8:28 PM UTC