Hello, I have migrated to 25.04 today. When I tried to set-up the Instances by selecting my pool and migrate my VMs, the dropdown menu @ Instances>Select pool>Storage>Pool gives me “[Disabled]”, instead of my pool:
I think you mean 25.04, since 24.04 is a year old and does not have the instance system…
Does your pool have a space in the name? There’s an upstream incus bug that prevents incus from seeing pools with spaces in the name.
Yes, I mean 25.04. Sorry for the confusion.
Yes it has 3 spaces.
So that is the reason… Do you know if the bug will be fixed soon, or do I need to rename my pool?
Also can you tell me how to rename it, because the Dataset tab is a little confusing for me. For example I am not even shure from where do I rename it. I assumed it is from Datasets>clicking on the pool>Edit (at the “Dataset Details”)>Name, but it is grayed out.
1 Like
Oh my God. They broke everything! 
I think, that I will wait a little to see if they will fix it via patch before I go down that rabbit whole.
It can take more then a “little while” until the fix will land in Truenas, maybe weeks or months…
It is probably best to share my story to help others.
I’ve been following the process to “rename” a pool and after doing the GUI Export, I cannot use CLI zpool to import/export again. Those instructions seem to no longer work as expected.
When I do sudo zpool import it returns no pools available to import.
When I do sudo zpool import 'Primary Pool' Primary I get no such pool.
When I do sudo zpool list I see the old pool sitting there named Primary_Pool so I tried to do an import with that name and it also did not work.
Now I’m in a limbo state and my server is useless to me as, if I recreate the pool I lose at least 1 VM and all my projects in Gitea (not my repo code thankfully). I’m just glad I forcefully sync 100% of my NextCloud because this would have been far worse if I had not.
Best I can say at this point is, Do not try the instructions to rename. I will reply here again if I can resolve my issue with the pool not being able to be reimported.
Yeah, I wrote to the devs. They said they aren’t planning to fix this issue, so we’re on our own with this one.
I think the best way to fix it (and the way I’m planning to do it) is to buy new drives (thank God my pool is only 2×12TB and 2×6TB), create a brand new pool without spaces, transfer all of my data to the new pool, and then add my older drives to it.
I think this is the least painful approach in my case. It’s also better to do it now, while I still have fewer drives, rather than wait until the pool grows to 6 or 8 drives, which would make the transfer much harder. For those who already have more drives than I do… all I can say is: good luck, guys.
Honestly, I have no idea what the devs were thinking…
My good part is that I was able to actually reboot, and the import showed up in the GUI. I restored my pool and everything was kosher. Ironically the export renamed my pool from ‘Primary Pool’ to Primary_Pool fixing the space all by itself.
None of the CLI was working for me at all and I just had to cross my fingers and dive in. I got lucky, I hope others will as well.
Moral of the story, I think, is to not be a silly “Windows User” about a naming convention for things in a *nix environment.
Maybe instead of that, TrueNAS should not allow space characters to be used for pool names, and then introduce a major feature that does not support pools with space characters in the name.
Just a thought.
2 Likes
I do not disagree with you, but I focus on things I can change not things I cannot. A company will do as it pleases regardless of my expectations, but I can establish better practices for myself.
This is a pretty cut and dry case where it really wasn’t your fault at all. You inputting valid characters into their input field in their web UI does not qualify as a bad practice, either. But hey, if you want to blame yourself, by all means go for it.
Facing the same problem… Do I really need to get new drives?
I would probably try to rename the pool first, although maybe ix staff will advise eventually on a recommended path.
Renaming the pool worked for me (don’t forget to encapsulate your name with space in quotes and use sudo) - luckily I didn’t have a lot of other services referencing it, so I didn’t have a lot of extra work to do. Now the pool shows up in Instances - we will see how it goes from here.
Boy what a turd of a global config, you give it the root pools, not even datasets. Pool names are generally treated as concrete, you pour it once and that’s that. Datasets are a little more flexible and give you some granularity. I hope they add datasets to the storage config in the future, unless there’s some super good reason for demanding the pool.
Hate to say it but I kinda miss jails already.
1 Like