Can I update worry free?

I currently have TrueNAS-SCALE-22.02.4 installed and I’m nearing a maintenance window where I can take this offline and update it. Can I or can I not safely update the system using it’s own update mechanism? When I go to update screen, it shows attached:

This guy tried asking something similar, but wasn’t given clear answer: How to update TrueNAS Scale 22.02.4 to Bluefin and beyond

You’re now four major releases behind current, so no, I wouldn’t bet on it. If you do encounter problems, boot environments will likely save you.

If you do decide to upgrade, I’d go stepwise through Dragonfish (so first to Bluefin, then to Cobia, etc.), and wait there until EE hits .1 or .2.

2 Likes

As dan mentioned the recommended way to upate is to update to the next major release.
I saw a post on reddit where the update from angelfish to electric eel failed, but jumping to the next major version worked.
If you have apps running , there were also some major changes between versions (looking at you hostpath validation) which may break your apps.

That’s quite a few major versions behind.

Depending on the complexity of your setup, it might be easier to back up your configuration file and install a fresh copy of a newer release - maybe even on a new boot device, so that you can easily revert. As mentioned there are quite a few changes along the way, both in terms of UI and functionality.

I’d suggest that regardless of the method you use to update, refrain from doing a “pool version update” as that will prevent you from reverting to an earlier boot environment.

Edit: When is your maintenance window? 24.10 is doing very well for a new release but systems that need to be updated during a “maintenance window” usually have a more crucial load than a home system, so I might suggest the latest Dragonfish release.

You should also read through the release notes for each major version, starting here (SCALE 22.12 Bluefin Release Notes | TrueNAS Documentation Hub) as there are some changes and actions needed along the way that might catch you off guard otherwise.

1 Like

Thanks, I’ve briefly read the changelogs. I don’t see an issue. I use TrueNAS for VMs and storage. The storage is RaidZ2 pool with 6 units and 1 hot spare. Some datasets are encrypted. There’s some structure to permissions in datasets. Some data is shared on NFS shares, some through SAMBA, but permissions, ownerships and inheritance are set in TrueNAS, not in shares. VMs are basic VMs with some networking bridge done so VMs can talk to host (the TrueNAS). I collected two things:

  1. Even if I upgrade to the newest TrueNAS, that new TrueNAS will recognize the pool drives and will be able to work with them. So even if I completely wipe the boot disk and install fresh TrueNAS, it should be able to pick up the pool and offer upgrade to the pool definition on it’s own. Correct?
  2. VMs. Worst case scenario I can just recreate VMs, assign their volumes, possibly re-set their MAC addresses to their current ones, etc.

I don’t use apps, docker features, and everything on this box is backed up to another box, which is running TrueNAS Core.

My maintenance window is kind of sort of floating, I don’t want to poke this thing needlessly, because it was pretty painful to set it up (I documented my journey on old forums, compared to stability and dependability of TrueNAS Core, this release of scale was kind of crap tbh), but it needs to be done. I expect all additional and replacement hardware for maintenance at this particular location will come by the end of the month and I’ll be onsite in December at some point for a day or two to do this. I expect this is not going to be effortless upgrade, I just want to avoid some headstomper that’s gonna take 12 hours to figure out, because someone from iX felt lazy on a Wednesday and checked in buggy networking UI into the codebase.