Earlier today, we launched TrueNAS 25.04.0 for our community users. Unfortunately, an issue in a train string prevented some users from upgrading. Our team has fixed, staged, and tested the fix to ensure everyone can access this release.
For those who already updated, no action is needed. There were no product changes. For those who found the upgrade was unavailable, thank you for the quick reports and we apologize for the inconvenience caused.
We will work on updating the SHA and download links on the website as soon as possible.
This is the first stable release of TrueNAS 25.04 (Fangtooth). It includes numerous software component updates, polished features, and fixes for issues discovered in 25.04-RC.1.
Special thanks to (GitHub users): Gleb Chesnokov and Franco Castillo for contributing to TrueNAS 25.04.0. For information on how you can contribute, visit Contributing | TrueNAS Documentation Hub.
25.04.0 Notable Changes
Notable changes since 25.04-RC.1:
Prevent cloned blocks remapping after device removal to avoid data corruption (NAS-133555).
Numerous improvements and bug fixes to the experimental Instances feature, including:
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.
Improved upload speed for volume imports (NAS-134552).
New IO Bus configuration options for Virtual Machines (NAS-134393).
New IDMAP options for users and groups in Linux containers (NAS-134447).
Fixed bug to allow console access for VMs created with an iso file (NAS-134253).
Fix KeyError crash in ipmi.lan.query (NAS-134736).
Fix permissions for user app config file (NAS-134558).
Prevent upgrade failure if encrypted fields are not readable in the DNS auth table (NAS-134728).
Optimize Dashboard resource widgets and fetch metrics once per page load (NAS-132124).
See the Release Notes for more details.
Been hitting refresh on my Fangtooth RC1 update button for 2 days. Now it worked, updated without trouble and seems to be smooth sailing. One thing concerns me, for which I’ll be filing a bug report.
Thanks everyone @ ixsystems for your quick response and quality work.
There is still a problem with iser. The iscsi service that starts automatically when the system starts will not trigger “Registered iSCSI transport: iSER”. You need to manually restart the iscsi service before you can load iser.
I can be sure that the output of my device midclt call system.product_type is ENTERPRISE.
Another question is why iperf3 in 25.04.0 has regressed to version 3.12. I noticed in the 25.04 nightly snapshot in February that iperf3 has been updated to version 3.16.
Beware that if you have an IPv6 block in the allowlist of Electric Eel and you upgrade to Fangtooth, you loose access over IPv6. I had to disable IPv6 on my laptop to restore access.
25.04.0 - Question, is Disk I/O the only option under Reporting for Disk? I thought I could see temperature here previously? Am I in the wrong section?
Trying to migrate zvol with Windows VM to Instances, but get this error:
Error: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 560, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 287, in nf
rv = await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 88, in wrapped
result = await func(*args)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/instance.py", line 439, in do_create
verrors.check()
File "/usr/lib/python3/dist-packages/middlewared/service_exception.py", line 72, in check
raise self
middlewared.service_exception.ValidationErrors: [EINVAL] virt_instance_create.source: Source already in use by another device.
Anyone else encountered this? What is “source” in this instance?
This would mean that the zvol is currently being consumed by something else. This can either mean you have another instance consuming the zvol or that somehow you put the same zvol twice in the same instance. Both cases will result in data corruption and so the backend is stopping it.
I think you should submit a bug report for this. We had a similar issue reported earlier in the 25.04 cycle, but it should have been fixed before RC.1.
I am currently on 25.04RC.1 and it shows the update to 25.04 but after selecting it and applying pending update, system restarts but stays on RC… I have attempted to install update multiple times and even tried the manual update method. Still on RC, will not update.
Thanks for the suggestion. Unfortunately that also did not work. I activated the 25.04.0 boot environment, rebooted, still has the RC active and keeps showing “Restart” on the 25.04.0 boot environment.
