TrueNAS 25.04.1 is now available!

Announcements
1

The TrueNAS team is pleased to announce that TrueNAS 25.04.1 is now available!

This is a maintenance release and includes refinements and fixes for issues discovered after 25.04.0.

Notable Changes:

  • Remove support for BOTH in share ACLs (NAS-135183).
  • Persist updated GMail OAuth refresh token to prevent deauthentication (NAS-135394).
  • Improvements to Instances, including:
    • Allow the same host path to be mounted inside multiple containers (NAS-135371).
    • ARC scaling and eviction fixes to prevent VM crashes due to OOM errors (NAS-135904).
    • Enhanced robustness of the Instances screen to handle edge-case configurations (NAS-135098).
    • Add a synthetic container root user (NAS-135375). This adds a built-in unprivileged root user for containers: truenas_container_unpriv_root. This account can be used in permissions related APIs / UI forms to grant permissions aligning to root in VMs and containers (see Managing Instance Permissions).
    • Improved error handling when instance ports conflict with other service or application configurations (NAS-134963).
    • Prevent accidental deletion of built-in idmap entries (NAS-135475).
    • Improved validation for attaching and removing zvols from instances (NAS-135308).
  • Increase middlewared.service timeout to prevent boot failure when upgrading systems with slow boot drives (NAS-135663).
  • Prevent JSON decode crash in smartctl output to fix issues with disk temperature reporting (NAS-135527).
  • Fix TrueNAS UI authentication with IPv6 entries in Allowed IP Addresses (NAS-135361).
  • Fix SSH service startup with auxiliary parameters enabled (NAS-135367).
  • Improve human-readable formatting of TrueCloud Backup log (NAS-134491).
  • Change how oplocks are handled for multiprotocol shares (NAS-135040). Removes kernel oplocks in favor of disabling oplocks on a per-share basis when they have been flagged for mixed-mode use. This avoids issues observed in the field with kernel lease breaks causing client timeouts as well allowing SMB leases globally, resolving limitations on multiprotocol shares and Time Machine backup seen in 25.04.0.
  • Fix API calls when connected to legacy /websocket endpoints (NAS-135643).

See the Release Notes for more details.

Download: https://www.truenas.com/download-truenas-community-edition/
Documentation: https://www.truenas.com/docs/scale/25.04

Thank you for continuing to use TrueNAS. Your feedback is appreciated!

6 Likes
2

I come home from work, i see update, i click, i wait, i’m happy.

2 Likes
3

I installed 25.04.1, seems to work fine. But dashboard’s system info box keeps saying “updates available”. But there are no more updates. So, how do I fix this?

7 Likes
4

FTFY :wink:

3 Likes
5

naaah, i like to live dangerously xD

1 Like
6

Can confirm this “Update available” on the Dashboard.

Otherwise the update itself was as smooth as always.

3 Likes
7

ducktales-darkwing-duck

1 Like
8

I’m getting a timeout error on the update?

9

I wanted to download the ISO for a fresh install on a new NAS, but the download link on the website still leads to 25.04.0.

10

Mine doesn’t now… can you reverify?

11

We have confirmed this issue exists for some users. It seems to be early adopters of 25.04.

There is a bug fix in 25.04.2 and 25.10

There is a slightly complex fix to remove a file in the system config. If you want to start a general issue, we’ll provide the fix and a NAS ticket.

1 Like
12

Quick question if it’s a bug or me missunderstanding something.
When i try to add the truenas_container_unpriv_root user to the incus id map i get this error

[EPERM] Users provided by a directory service must be modified through the identity provider (LDAP server or domain controller).

Is this supposed to happen?

13

If it did not happen in the previous version… then it useful to know it has changed.
Otherwise I’d suggest a thread in the General channel.

14

I thought this was only added with this update so i don’t believe it’s possible on 25.04.0 :thinking:

15

The error message can be improved. You’re not supposed to be adding that to the idmap. It’s automatically there by default because it’s literally the root account in the container. The change was merely to make the account visible in the UI permissions editors.

16

Aah ok i see. Thanks for the quick answer. But i must agree the error message is very missleading…

17

It’s automatically generated any time the id key for what is being modified is in what we consider the synthetic range used by directory services. So cosmetic and nothing else.

18

Nice framing! :rofl: Could have been the late fixers as well.

19

If this was directed at me, still have a timeout error.

To note, I have ensured that there is no VPN in place for the Truenas box so I don’t think it’s anything my end but could well be wrong.

20

I have the same problem of Updates Available still showing although I restarted a few times.

How or where can I find the fix for this?