Unable to get rid of a pool in 26.0.0-BETA.1

TrueNAS General
1

There was a pool, named POOL.

I have removed the disks without exporting the pool.

Then I brought in a blank set of disks and started up.

Up comes a warning “Can’t import POOL”.

In earlier versions, I would have opened Storage and there will be POOL, unmounted, but still exportable. So I would have exported it post factum and all is well.

In 26.0.0-BETA.1, there is no POOL under Storage so I can’t get rid of the phantom. If I go create a new pool, it says the name “POOL” is already in use.

It is a test system, so I realistically don’t even need a fix. Just thought that was unusual.

2

Can you

sudo zpool destroy -f POOL ?

3 

Welcome to TrueNAS
truenas_admin@truenas[~]$ sudo zpool destroy -f POOL  
[sudo] password for truenas_admin: 
cannot open 'POOL': no such pool
truenas_admin@truenas[~]$
4

Additionally, in that condition I can’t create another pool (named POOL1)

Plus also note somehow NaN bytes (lower right)

image
image895×630 26.9 KB

5

Maybe the disks are not as clean as you think they are? Use zpool labelclear on them, possibly?

6

The original disks are removed.

The new disks are definitely blank (it is an experimental VM, these are VHDX virtual disk images, and I know I have just created them). Furthermore, I used the previous TrueNAS version and everything worked as intended.

So it is a problem introduced in the latest beta.

7

Perhaps the output of these two commands should help show the current status?
sudo zpool import
sudo zpool status -v

8

Then report the bug. Its a BETA after all.