TrueNAS 25.04.2 is Now Available!

Announcements
1

The TrueNAS team is pleased to release TrueNAS 25.04.2!

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

25.04.2 Notable Changes

  • TrueNAS 25.04.2 reintroduces “classic virtualization” with the Virtual Machines feature.

    • Virtualization features are now split between the Virtual Machines and Containers screens.

    • Virtual machines created in 25.04.0 or 25.04.1 using the Instances feature continue to function and appear in the Containers screen.

    • New VMs and those migrated from 24.10.2.2 to 25.04.2 use the Virtual Machines screen.

    • Virtual machines automatically migrate from TrueNAS 24.10 to 25.04.2.
      No manual migration of virtual machines is required.

  • Adds the ability to enter optional custom endpoints in cloud sync credentials that support Global and Select tiers in Storj (NAS-133835).
  • Adds a Secure Boot checkbox to the Add Virtual Machine wizard and Edit Virtual Machine form (NAS-136466).
  • Passes the Storj/iX cloud sync credential access key and secret access key in the UI when creating the credential (NAS-135837).
  • Removes the Mega cloud service provider for rclone.
    • Mega Technical Support states they no longer support rclone due to bugs in their implementation and requirements to properly troubleshoot issues (NAS-135844).
  • Adds the ethtool -m to the debug file, which brings additional layer1 troubleshooting to interfaces (NAS-135911).
  • Shows all object fields and explicitly lists all parameters and result fields for nested objects not previously included in generated API documentation (NAS-135959).
  • Adds starting and stopping services in the UI to the audit log records (NAS-136310).

See the 25.04.2 Release Notes for more details.

25.04.2 Documentation : TrueNAS Documentation Hub

Download : https://www.truenas.com/download-truenas-community-edition

Thank you for using TrueNAS! As always, we appreciate your feedback!

10 Likes
2

If only if worked properly for me😅 see: Extremely poor performance on 25.04.2

Edit: Ticket NAS-136938

3

@TheColin21 Please add the ticket number after you report the bug… we can then all track it here.

Thanks for the early warning. Users should note that while 25.04.2 is out, it is not yet recommended for all user profiles in the Software Status page. Waiting for issues to be identified, resolved, or worked-around can be the right strategy.

Update: this specific issue was a CPU utilization reporting issue with no TrueNAS performance impact.

https://ixsystems.atlassian.net/browse/NAS-135633

3 Likes
4

Note that I added a fix for 25.04.2 for server-side-copy over SMB for MacOS.

4 Likes
5

i update my backup server which also has most of the vms

something very strange happened…

the apps migrated fine, no issue i can see

the containers; i was under the impression that only the containers would migrate to the container tab, but all the containers AND vms migrated to that tab. they all seem to work as before so maybe i misread the update notes. and since they work i dont care

the virtual machines; this is a train wreck. not even sure what this is. i have 5 vms here that use vnc port duplicates from my original vms (which are now containers). but they are different names on different ports. no clue what this even is to be honest. perhaps a remnant of something else or something i had done before and deleted? but i dont recognize what these are.
i will do some testing to see if they are even attached to anything.

so overall; it updated, seems to work, apps fine, containers unexpected behavior, virtual machines a complete mystery
[edit] the virtual machines wont start. again, no loss since im not even sure where they came from, but they just spin and eventually give me an error
[EFAULT] VM will not start as DISK Device: /dev/zvol/ssd/Virtual_Disks/Ubuntu-is5xx, DISPLAY Device: 0.0.0.0:5900 device(s) are not available.

6

Smooth update, but then again, i don’t use vm’s and stopped my incus lxc migration plans and kept my jailmaker jail running.

3 Likes
7

After the update all my VM’s where gone! So I switched back to 24.10.2.2 intermediately and created a ticket * NAS-136940

1 Like
8

99.9% smooth update from 25.04.1 to 25.04.2

I have two TrueNAS systems, one of which is for testing purposes.

My test system is a VM running on my main TrueNAS. My test system is running a Home Assistant OS VM. (Yes, that’s a VM inside a VM.) The test system updated smoothly. The HAOS VM appeared under containers as expected and started back up without issues.

Then I updated my main TrueNAS system without any serious issues. The TrueNAS test VM appeared under containers as expected. It also started and works without any issues. Additionally, the HAOS VM inside the TrueNAS test VM also started and works as expected.

To my surprise, I also have two VMs under Virtual Machines. One of them is a VM that I never migrated over to Instances, so it makes sense that it would reappear given the circumstances. The only glitch was that the second VM reappeared. It is an old VM that I had deleted some time before updating to 25.04. I even booted back to 24.10.2 and confirmed this second VM did not exist. After returning to the 25.04.2 boot environment, I was able to delete the ghost VM again without incident; no tears were shed :laughing:

EDIT: I also have one official (dockage) and two custom apps installed. They are back up and running. No issues to report.

4 Likes
9

AD with RID is still very touchy… I suspect it will fault overnight as it faulted while I setting it up and a good automatic configuration for this still does not exist. I update here in the morning if it faults and or becomes inaccessible.

Update:
SMB is accessible but my AD in fact faulted again this morning.
Update:
krb5.conf was removed… so there is no saved bindpw for the domain even though it eanbled it and was healthy for awhile it just didn’t save it or something?

10

Glad to hear it went well, but ghost VMs are still a minor bug. If you have a chance to report with a debug that would be greatly appreciated.

11

Everyone else, please be detailed in your posts. If you created a thread elsewhere on the forums, post a link so we can just go to your main problem and not end up asking questions here.

12

Just updated from 24.10.2.3 to 25.04.2. Haven’t noticed any issues so far.

I have a Windows VM that migrated over just fine. TPM and Secure Boot are still working for that VM (I had got that working previously in 24.10.x by manually updating the VM config using the TrueNAS API). I appreciate that the UI now exposes the ability to enable TPM and Secure Boot without having to resort to that. I also have a Debian Linux VM that also ported over fine as well. I haven’t seen any issues with my docker containers either (I’m not using any built-in apps, I’m running them as all custom docker containers managed by Portainer).

2 Likes
13

Clarification since you asked: i updated the one titled “my truenas system”

both were running 25.04.1 before the upgrade to .2

i figure i misread the notes regarding the container portion since it makes sense that everything done under incus would stay there - and they all still work fine

i ended up deleting all the vms - they didnt work anyway.

14

Thank you for sharing your experience. The Windows VM is what I am most concerned about when I attempt an upgrade.

16

@Stux, one of your students just graduated. :mortar_board:

3 Likes
17

512×265 11.2 KB

3 Likes
18

Unusual… I assume you can roll back successfully.

It is the 2nd report of this… VMs disappearing

@louis did you also have nothing but VMs?

We probably never test a VM-only config in the lab… its always SMB, NFS or iSCSI as well (or is this what you mean by storage-only?)

Update:

The “bug” has been found.
https://ixsystems.atlassian.net/browse/NAS-136941

It looks like a check was added to make sure vnc port settings were high enough (10,000 +)

That check was too aggressive and stopped all VMs. It will be fixed, but in the meantime check VNC port numbers before migrating.

19

Two flawless updates for me:

Main system (with VMs) from 24.10.2.3 to 25.04.2. VMs still there and fine after the update.
System for replication backups from the main system from 25.04.1 to 25.04.2 was also smooth.

1 Like
20

I am using SMB and iSCSI. But they related to the TrueNAS core system. I do not think there is a VM or iSCSI instance related to a VM at this moment.

I do not know the TrueNAS internal ‘VM-structure’ however if it is IP-related be aware that:

  • the VM’s have their own vlan’s and their own ip-address and that is IMHO the way it should be.
  • that you can not assign an IP-address to a TrueNAS bridge and the same address to the VM - itself (see one of my earlier posts)
21

The VM tab issue is due to VNC password. You have to set VNC password to all your VMs in 24.10.3.2, make sure to delete 25.04.2 boot environment if you already updated and do the update again

2 Likes