Importing configuration creates pool that is not shown

[Gaspetaahl]

I own two identical system on which I installed Truenas (scale). I started to configure the first system and also created a pool there. I called the pool "pool". After I've done all my desired configuration I downloaded the configuration and uploaded it to the second system, thinking that that would be a smart way of not having to redo all the configs.
I then noticed that no pool was created. That I expected but when I tried to create a pool and also name it "pool" then truenas tells me that a pool with that name already exists. But it is not shown in the Storage or Datasets Tabs. I think this is unwanted behavior. Not creating the pools is what I expect because that would also mean writing to the disks but then taking the name from the config and "reserving" it is weird and leaves me wondering how I should proceed now.
Maybe there should be a warning about this and also the name of the pool should not be copied if the pool is not actually created.

 

[Patrick M. Hausen]

I would try this:

- create pool "foo" in the UI
- export pool "foo" from the UI
- on the command line: zpool import foo pool; zpool export pool
- import pool "pool" from the UI

But I agree, if not downright a bug, a severe POLA violation at least.

 

[Gaspetaahl]

Thanks that worked. Can I open an issue somewhere about this problem?

 

[Patrick M. Hausen]

Right at the top of this forum: "Report a Bug".