TrueNAS 13.0-RELEASE has been released

[eturgeon]

TrueNAS Community,

We are pleased to announce the release of TrueNAS 13.0-RELEASE. TrueNAS 13.0-RELEASE contains several fixes, improvements, and a few new features. Here are some Highlights: Improvements to the main dashboard, CPU dash widget and temperature colors, Enclosure rewrite, and Updated Asigra plugin. See the release notes for the full changelog.

With this release, we are excited to continue providing more opportunities for Open Source contribution and further reducing the barrier to contributing documentation! For the CORE 13.0 release, the Docs Hub expanded to allow readers to suggest new text to the content. The only requirement is logging in with a Google or GitHub account. In addition, the website uses Commento to add a Reddit-style comment thread after the content of each article, allowing suggesting new content on that page and readers to interact with each other and upvoting suggestions. To read about other changes to the Docs Hub as part of this release, see https://www.truenas.com/docs/#whats-new-on-the-documentation-hub.

Release Notes: https://www.truenas.com/docs/core/corereleasenotes/#130-release
Download: https://www.truenas.com/download-truenas-core/

Thanks for using TrueNAS, and we always appreciate all your feedback!

 

[tiberiusQ]

Last login: Tue May 10 13:15:51 on pts/1
FreeBSD ?.?.? (UNKNOWN)

Wow u seem to put it to freebsd 13.1rc6, pretty interesting;

root@truenas[~]# uname -a
FreeBSD truenas.local 13.1-RC6 FreeBSD 13.1-RC6 n245364-74831eea544 TRUENAS amd64

 

[NugentS]

Is there an upgrade path from 12.8 etc

 

[Patrick M. Hausen]

Wow u seem to put it to freebsd 13.1rc6, pretty interesting;

With TrueNAS 12 they started tracking FreeBSD -stable and doing their own QA. Which is a blessing because before that switch FreeNAS/TrueNAS releases tended to lagg behind FreeBSD so eventually you could not upgrade jails anymore.

Well done folks, and thanks for all the work.

https://twitter.com/Sweordbora/status/1524132732523233283

 

[morganL]

Is there an upgrade path from 12.8 etc

Yes, upgrade from 12.0 will be automated and simple from the UI. I assume there's a little delay while the CDN is updating.

Blog on the TrueNAS 13.0 is here:
https://www.truenas.com/blog/truenas-13-0-succeeds-truenas-12-0/

 

[morganL]

There is a demo of TrueNAS 13.0 managing 1200 drives here: https://www.youtube.com/watch?v=fn0CCZlFW54

 

[mav@]

Wow u seem to put it to freebsd 13.1rc6, pretty interesting;

It was going to be FreeBSD 13.1-RELEASE, but last moment OpenSSL vulnerability fix triggered another RC cycle and shifted FreeBSD release schedule by one week. TrueNAS 13.0-U1 will get the official release, but it is only a name at this point.

 

[Samuel Tai]

Yes, upgrade from 12.0 will be automated and simple from the UI. I assume there's a little delay while the CDN is updating.

http://update.freenas.org/FreeNAS/trains.txt still needs to be updated to reflect the new train. Otherwise, only manual updates using the TAR file at https://download.freenas.org/13.0/STABLE/RELEASE/TrueNAS-13.0-RELEASE-manual-update.tar are currently possible in the 12.0 UI.

Trying midclt call update.set_train "TrueNAS-13.0-STABLE" just results in:

middlewared.service_exception.CallError: [ENOENT] Invalid train name

 

[morganL]

http://update.freenas.org/FreeNAS/trains.txt still needs to be updated to reflect the new train. Otherwise, only manual updates using the TAR file at https://download.freenas.org/13.0/STABLE/RELEASE/TrueNAS-13.0-RELEASE-manual-update.tar are currently possible in the 12.0 UI.

Trying midclt call update.set_train "TrueNAS-13.0-STABLE" just results in:

middlewared.service_exception.CallError: [ENOENT] Invalid train name

this UI update will only be available after there is sufficient validation.

We'll communicate the plan tomorrow.

 

[elvisimprsntr]

I received the following Alert, but I don't see anything on the lease notes page or how to update the ZFS pool flags.

/core/gettingstarted/corereleasenotes/

New ZFS version or feature flags are available for pool data. Upgrading pools is a one-time process that can prevent rolling the system back to an earlier TrueNAS version. It is recommended to read the TrueNAS release notes and confirm you need the new ZFS feature flags before upgrading a pool.​

2022-05-10 20:52:40 (EST5EDT)

 

[elvisimprsntr]

I received the following Alert, but I don't see anything on the lease notes page or how to update the ZFS pool flags.

/core/gettingstarted/corereleasenotes/

Strangely, I received the Alarm on one system that has external USB SSD, but did not receive the alert on a system that does not have any external USB SSDs.

 

[Samuel Tai]

I received the following Alert, but I don't see anything on the lease notes page or how to update the ZFS pool flags.

The only way currently is via the shell: zpool upgrade <name of your pool>.

 

[elvisimprsntr]

Strangely, I received the Alarm on one system that has external USB SSD, but did not receive the alert on a system that does not have any external USB SSDs.

I stand corrected, it took awhile after reboot before I received the Alert on the second system.

 

[elvisimprsntr]

The only way currently is via the shell: zpool upgrade <name of your pool>.

I didn't see anything in the release notes regarding what the new ZFS pool flags are.

So using the webGUI to upgrade the pool is not an option?

 

[Samuel Tai]

I didn't see anything in the release notes regarding what the new ZFS pool flags are.

So using the webGUI to upgrade the pool is not an option?

Seems to be a known bug which will be fixed in 13.0-U1. See https://jira.ixsystems.com/browse/NAS-116142.

As for the new ZFS flags, this is probably due to the upgrade to OpenZFS 2.1 from 2.0 in 12.0. See https://openzfs.github.io/openzfs-docs/Basic Concepts/Feature Flags.html. The only change between 2.0 and 2.1 I can see is support for dRAID.

 

[elvisimprsntr]

Seems to be a known bug which will be fixed in 13.0-U1. See https://jira.ixsystems.com/browse/NAS-116142.

As for the new ZFS flags, this is probably due to the upgrade to OpenZFS 2.1 from 2.0 in 12.0. See https://openzfs.github.io/openzfs-docs/Basic Concepts/Feature Flags.html. The only change between 2.0 and 2.1 I can see is support for dRAID.

OK, this is the message I received

root@NAS-1[~]# zpool upgrade boot-pool
This system supports ZFS pool feature flags.

Enabled the following features on 'boot-pool':
draid

Pool 'boot-pool' has the bootfs property set, you might need to update
the boot code. See gptzfsboot(8) and loader.efi(8) for details.

 

[Samuel Tai]

@elvisimprsntr, @Kris Moore himself advises against upgrading features on the boot pool.

Is it safe to upgrade ZFS features on the boot pool?

When I run zpool status -v freenas-boot, I get: pool: freenas-boot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done...

www.truenas.com

 

[elvisimprsntr]

@elvisimprsntr, @Kris Moore himself advises against upgrading features on the boot pool.

Is it safe to upgrade ZFS features on the boot pool?

When I run zpool status -v freenas-boot, I get: pool: freenas-boot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done...

www.truenas.com

I assume this was a one way trip and I am hosed.

 

[Samuel Tai]

I assume this was a one way trip and I am hosed.

If you can still boot, then the bootloader doesn't care about this feature flag. If you can't then you're stuck reinstalling and reloading your config.

 

[mav@]

I assume this was a one way trip and I am hosed.

It is indeed one way trip, but not all enabled features are immediately activated. As you see the only enabled feature is draid, which according to `man 7 zpool-features` should not activate unless you add draid vdev to the pool.