TrueNAS 25.04-RC.1 is Now Available!

Announcements
1

We are pleased to release TrueNAS 25.04-RC.1!

:warning: Early Release Software

Early releases of a major version are intended for testing and feedback purposes only. Do not use early-release software for critical tasks.

This release candidate version has software component updates and new features that are in the polishing phase as well as fixes for issues discovered in 25.04-BETA.1.

Special thanks to (Github users) René, jnbastoky, Bas Nijholt, jbsamcho, t0b3, Franco Castillo, Ljcbaby, Oskar, ken1010533, Gleb Chesnokov, markrieder, janekdz, Aurélien Sallé, Nicodemus Schoenwald, m.chernobrov, Jason Cheng, SejoWuigui, TheJulianJES, p0358, Janek, Dhananjay Kamble, wanyuehan, Georg Schölly, dany22m, xream, and Lee Jihaeng for contributing to TrueNAS 25.04-RC.1. For information on how you can contribute, visit Contributing | TrueNAS Documentation Hub.

Notable Changes

  • To prevent excessive resource usage, especially on systems with large HDD storage pools, SMART test results no longer appear directly on the Storage dashboard. Click View S.M.A.R.T. Tests on the Disk Health widget to open the S.M.A.R.T. Test Results of POOL screen.
  • Allow configuration of IO bus for disk devices in Instances (NAS-134250). This enables users to create virtualized disks using a standard other than VirtIO in cases where the OS image does not by default include VirtIO drivers.
  • To improve stability and prevent unsupported SMB configurations from breaking on migration from TrueNAS CORE, TrueNAS automatically removes the SMB auxiliary parameters wide links, use sendfile, vfs objects, and allow insecure during migration (NAS-132911).
  • To prevent unexpected failures in SMB shares, TrueNAS automatically disables SMB2/3 lease support globally when multiprotocol SMB/NFS shares are enabled (NAS-133680).
  • Reserve 2 GiB of disk space (but no more than 1%) to allow the data disk to be replaced with a slightly smaller one in the future (NAS-134309).
  • Bugfix: Ensure disk temperature reporting is available for all disks (NAS-130766).
  • Bugfix: Allow SMB authentication for usernames with a capital letter (NAS-134346).
  • Bugfix: Fix top toolbar icon colors for the iX Blue, Paper, and High Contrast UI themes (NAS-133853).
  • Bugfix: Enable the applications Web UI button when accessing from IPv6 or mDNS name (NAS-133655).

:information_source: Note

Instances (Incus-powered containers and virtual machines) are an experimental feature intended for community testing only. Functionality may change significantly between releases, and instances may not upgrade reliably. Use this feature for testing purposes only—do not rely on it for production workloads. Long-term stability is planned for future TrueNAS Community Edition releases.

See the Release Notes for more details.

Changelog: https://www.truenas.com/docs/scale/25.04/gettingstarted/scalereleasenotes/#2504-rc1
Download : https://www.truenas.com/download-truenas-scale
Documentation : https://www.truenas.com/docs/scale/25.04

If you find a bug, please create a ticket at https://ixsystems.atlassian.net/jira/software/c/projects/NAS/issues

Thanks for testing this early release of TrueNAS Fangtooth! As always, we appreciate your feedback!

7 Likes
2

Very excited! I’ve really been enjoying hearing details about the upcoming releases on the podcast. This is the first RC I’ll be testing since Cobia

2 Likes
3

Overall, enjoying Fangtooth.

Notes:

  • Dashboard now properly shows temps / utilization on my EPYC. It was not displaying/updating with the beta.
  • Storage Dashboard is still not showing drive temps. Highest/Lowest/Average all have “No Data.” Strange since Reporting has the disk temps.

Thanks for the update. Hope Incus continues to improve :slight_smile:

3 Likes
4

Instances page could just reuse the layout of the apps page with the metrics and coloured status indicator. Low hanging fruit, big convenience factor. The metrics are not working at all yet. I hope that can be fixed before official release.

So far stable on two of my systems with minor quirks and bugs I have already reported. Will mess around with LXC and VMs more this week and report my findings.

5

Another boring update process without problems

3 Likes
6

I’m actually excited to install this version later today. Been looking forward to it for a while now.

1 Like
7

Upgraded and tried recreating my Home Assistant VM. Both my zwave and zigbee dongles have the same hardware id. Incus didn’t seem to like that and errored on creation. Afterwards I was unable select any devices to add to the VM.

Previously was using bus and port id’s, hopefully this option can be added back.

1 Like
8

I don’t understand why they have the same IDs. Perhaps start a new thread and post a link.

9

About how long should it take to upgrade from ElectricEel-24.10.2?

10

Depends on a lot of stuff, like download time, install time, etc. But typically 2-5 minutes.

11

Smooth upgrade from Beta 1. Everything including a Windows 11 VM and Ubuntu container running fine in Instances.

2 Likes
12

Created a thread for it.

https://forums.truenas.com/t/incus-duplicate-usb-hardware-ids/36344

1 Like
13

Upgraded from 25.04-BETA.1 to RC.1 on a secondary system and all VMs still work as expected. Didn’t notice any obvious issues, except minor UI problems, like the “Community Edition” badge being barely readable on 1080p/1440p monitors or the icon for offline network interfaces only showing a single pixel—I’ll check for open issues later or create new ones.

Still wish it would be possible to change a VM’s MAC address from the UI, like possible in 24.10 and before. Workaround: incus config device set InstanceName eth0 hwaddr 6e:b1:f1:ec:51:12

And maybe also allow removing the root disk for VMs?

Regarding the release notes, the “Notable Changes” mention “Allow configuration of IO bus for disk devices in Instances (NAS-134250)”, yet the the known issues include “In 25.04-RC.1, VirtIO is the only available IO bus for VMs”.

It seems like only the middleware PR was merged for RC.1, not the frontend one, so it might be nice to make it a bit clearer that it’s only possible to change via CLI in RC.1 (not possible with only the UI yet).
With CLI, either a TrueNAS cli “virt instance device_update” call to change “io_bus” to “NVME” should work, or using incus config device set directly here is also “ok-ish”, as that’s basically what middleware does with a small validation before it.

And another thing, the link for “NAS-134660” in the “Upgrade Notes” section is wrong, as it’s missing a 0 at the end.

14

Thanks for the suggestions. Those should be fixed now.

1 Like
15

Will this also get created on already existing pools?

16

Tried upgrading from 24.10.2 to RC1 but had to revert because my HomeAssistant and Linux VM couldn’t boot (even though I followed the upgrade documentation).

Only got part of the error, sorry about that:
Your user does not have sudo privileges so /usr/bin/incus command will run

17

But Multi-Report still no workee, email report-wise?

18

I noticed that in BETA.1 and was hoping it would be fixed in RC.1, guess they are hardening the system more.

I may have a fix, I will post after I test it.

19

Interesting thing just happened… I tried to roll back to BETA.1 to verify a test but when I migrated to RC.1, my pool was modified and I had no shares, got a few error messages from the middleware, very unexpected. So then I made RC.1 active again, all was good. Next I thought, I wonder if I can roll back to 24.10.2, and it worked, a sigh of relief swept over me.

Not sure why the odd behaviour happened.

Then I changed from 24.10.2 to BETA.1 again and it does not work. All my shares are gone and I have invalid Grouping and Quotas. The thing is, I never set quotas.

So heads up, you may not be able to roll back to BETA.1 very well.

I will not report this as a problem, it was likely a problem fixed and rolling back fails. But back to 24.10.2 worked.

1 Like
20

The “hardware clock” in the new VMs/instances seems to be off by one hour (in Germany). Every time a VM is restarted, it defaults to the wrongly emulated hardware clock. Depending on the configuration, it causes Windows domains to break due to Kerberos requiring them to be in sync within 5 minutes.

This did not happen in 24.10 or earlier, as there was an option to either set the time to LOCAL or UTC. The default was LOCAL. This is no longer the case apparently.

You should be able to work around this with RealTimeIsUniversal, but I imagine keeping the current behavior will still break a lot of existing setups, especially when you’re running domain controllers with the PDC role and they’re not set up correctly to synchronize from an external source.

But even with normal Windows (client) VMs, it will break things and Windows doesn’t seem to sync time very often, so the time is always wrong on startup and maybe eventually gets fixed, until a VM restart.

If an option like that is enabled, middleware would just need to add -rtc base=localtime to the raw.qemu config.

EDIT: See NAS-134717

1 Like