I just upgraded from Core to Scale and have lost all of my data pools and data sets. I tried importing without any sucess when i run sudo zpool status -v i can see 3 pools however i can’t see the largest pool i had. if i run lsblk i can see all of my drives. i don’t have a backup of the data that was in that pool. any assistance would be helpful
Were you using GELI encryption on Core? It’s also labeled “Legacy Encryption” in the GUI.
Reinstall CORE (or put back the CORE boot drive if you still have it).
i don’t believe the pool was encrypted. i will try and reinstall core. and see if i can get the pool back.
Even if the pool was encrypted (by ZFS), it would still be visible. AIUI, GELI, on the other hand, is a drive-level encryption.
EDIT: Added clarifications for the type of encryption.
1 Like
Ok attempted installing Core again with still no luck in seeing the pool i did some looking and there is mention of Klennet in some of the searches i have done. not sure where to go from here but i will keep going. Any help is appreciated
Are you sure?
Pools don’t just spontaneously disappear because you upgraded the underlying OS.
It would not. The underlying ZFS labels would be inaccessible (and unknown) until the partitions are decrypted.
The same is true for something like LUKS.
Well, mine did, I have the same issue as the OP. Pool disappeared after CORE->Scale upgrade.
You cannot import a pool in SCALE if you used GELI encryption under Core.
You either have to stick with Core or replicate the pool to non-GELI devices.
For both you and @Alex_Riddell, what version of TrueNAS did you upgrade from and to?
What method did you use (click upgrade in the UI or a fresh install and config restore)?
Did you follow the process and reccomendations in Migrating from CORE | TrueNAS Documentation Hub?
I had just upgraded to the latest Core version before doing the conversion. i beleive i went to the latest scale that was in the UI drop down afterwards.
i chose the update from the UI and not a fresh install. i did look through the migrating from documents prior to updating and i don’t remember it the pool being encrypted. there was nothing crazy going on with my setup no applications running on it it was just a NAS. and it’s only one pool i can’t seem to see or get data back from
I meant ZFS encryption. Perhaps I wasn’t clear enough.
1 Like
I didn’t have a geli encryption on my pool. I’ve double checked before update as advised in Migrating from CORE | TrueNAS Documentation Hub
I upgraded from 13.0-U6.7, via UI and yes, followed all the steps in the document.
Following this thread but not with many more ideas …
Could you try booting a current version of FreeBSD (14.2) from a USB drive, drop into the live system, and try
gpart show
zpool import
Kind regards,
Patrick
1 Like
So the upgrade path you followed was from 13.0-U6.7 to 24.04 using the UI? Or did you attempt to upgrade directly to 24.10 or 25.04?
From that page:
TrueNAS users wanting to migrate from the latest FreeBSD-based 13.0-U6 or 13.3 CORE release to the Linux-based TrueNAS version 24.10 or later can migrate to 24.04 and earlier using the UI update process, but must clean install if migrating to later releases. Attempting to migrate directly to 24.10 or later using the UI is not supported.
Do you have a saved config file from CORE?
I used the upgrade path to 24.04 in the UI. as for grabbing a config file from CORE i can’t find it i did save it to my desktop but my son was using the computer afterwards and i can’t find it
Ok that’s so far so good.
I don’t think zpool status shows an exported pool. What happens if you just run sudo zpool import without specifying the pool?
I will have to try this tonight when i get home.
Please also consider the steps in @pmh’s post.
As for this happening to multiple users after sidegrading from Core → SCALE, I’m suspecting it’s either:
- GELI encryption was used
- A process in the SCALE sidegrade actually did “something” to the partitions or labels on the attached drives[1]
Does anyone know if there is any code that would “touch” or do “something” to the partitions during a sidegrade?
This becomes more possible if the exported pool is not detected when reverting back to Core, while GELI isn’t involved. ↩︎