New install of v24 or v25 for zfs 6-disk array built with v13

TrueNAS General
,
1

Howdy, folks

My v13 core USB boot drive ate it. The ZFS storage was built and running with version 13, and the data should be fine. Should I build a new USB with v24 or v25, or should I use the old v13?

Thanks all

2

USB is no longer recommended as boot medium, get a cheap sata ssd
As for version go with latest 25.04 if youre cautios or 25.10

3

Oh, that makes sense, but in my case I am out of SATA ports! Maybe I will; I will def look into a new card or something.

Thanks

4

Then get a USB to sata adapter, but definitely no thumb drive

2 Likes
5

While I’m waiting for an answer to the topic (and for an SSD to be delivered), I re-installed v13.0–u2 so that, for the time being, I could regain access to the ZFS shares.

But, some odd things happened, so maybe just installing v24 or v25 is a better way to go…

Odd things:

After install and upon 1st-time GUI access, the run-first-wizard did not run.
Although the 5 disks are all seen, the pool is not.
The pool should still be there, as the raidz configuration allowed for 2 disks to fail before data loss.

Questions:

Is there a way to force the new 13.0 installation to run the setup wizard?
Will running the setup wizard allow the OS to “see” the existing pool?
If I install v24 (or v25?) should it recognize my v13 pool?

Thanks all,
RG

6

Open up the Shell and give us the results from the following. Post back using Preformatted Text mode (</>) or Ctrl+e Each in their own preformatted text box.
zpool status -v
zpool import

7

Results of the 2 commands you recommended:

root@truenas(~]# zpool status -v
pool: boot-pool
state: ONLINE
config:
NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
daOp2 ONLINE 0 0 0

errors: No known data errors

root@truenas(~]# zpool import
pool: Centurion
id: 13327427276595939546
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
Centurion ONLINE
raidz3-0 ONLINE
gptid/8d7312f4-07bb-11lee-a472-e03f4948db98 ONLINE
gptid/8d4120cd-07bb-11lee-ad472-e03f4948db98 ONLINE
gptid/31431cal-09e4-11f0-84ff-e03f4948db98 ONLINE
gptid/8d38c22d-07bb-11lee-ad472-e03f4948db98 ONLINE
gptid/8cfd27d6-07bb-1lee-ad472-e03ÂŁ4948db98 ONLINE

8

Do you have a recent system configuration you can restore to the server? If not, you can go into the GUI and see if it lets you import your pool that way. The command didn’t report any errors.

You might have to set up sharing again but at least the pool will be showing in TrueNAS

9

Pool Imported!!!

Now I just need to make all the configuration changes to the defaults. No, I do not have the configuration saved anywhere. Or, maybe… Is it possible to save the configuration onto the ZFS set? Maybe I did that all those many years ago…

So, with that milestone cleared, can I upgrade to v24 or v25 straight from 13.0?
Thanks, all. You guys are great.

10

If you install TrueNAS SCALE by upgrading our current TrueNAS Core boot disk, yuo won’t be able to boot back from TrueNAS Core 13.

Best if you install TrueNAS SCALE 25 on a different disk altogether. You should be able to import the pool if it isn’t using the GELI encryption. If you have jails, they won’t work.

You should be able to run some of the VM if you have them.

11

@mudshark Unless you are interested in the latest bells and whistles of TrueNAS, I would update to 25.04.2.6. At the present time, this is the most stable version of TrueNAS. You will have no problem reading the ZFS disks from a Core system - unless they are encrypted.

A few months ago, I updated from Core 13. In my case, I had applications in FreeBSD jails which will not migrate to Scale anyway, so I decided to do a fresh install of Scale 25.04.2.6 on a new SSD, set up everything from scratch, and import my existing data pools. No problem. I chose to setup networking and applications from scratch rather than import an old configuration - mostly because I wanted to do a better job setting things up now that I had more experience about how everything works. It really didn’t take very long because my system was not particularly complicated. You mileage may vary on this.

The process went smoothly. The only issue I encountered was related to file access permissions and sharing - I had to redefine some of the file ownerships and access permissions because I had done a terrible job of setting them up in my original Core implementation many years ago. However, my data itself was never at risk.

12

Thank You