Well evidence shows that 25.04.2 is in the update release. This thread is to capture issues or success of the install. As soon as it is proven viable I plan on taking my EEL to Fangtooth with 25.04.2.
1 Like
I made the update on a Virtual Machine Manager (in Fedora 42) from a Truenas 25.04.01 install and it went fine. ssh login works, htop loads fast and is not showing any issues, GUI loads fast, and at first glance seems to work well. Have a few apps, they work but were made in 25.04.01 so I would not expect any issues. Might wait a day or so before I do a real machine.
Update:
Decided not to wait. Updated secondary server first then updated primary a bit later. Both were on EE 24.10.2.3. All apps updated fine on both servers Have no VM’s. ssh, GUI, all work fine. Upgraded the pool which went fine on both servers. CPU use, Temp, cache, memory, disk temps are all nominal values for my systems.
Only thing offhand I see missing that I occasionally used in EE is the NetData link under reports. Looks like the Reports might now use Graphite as the external report.
2 Likes
I’ve had a severe issue: Extremely poor performance on 25.04.2
@TheColin21 I saw your thread, but no ideas to help or try come to mind.
No problems so far, but i do not use vm’s and stopped my lxc migration plans and kept my jailmaker jail, which simply keeps running, udpate after update.
Successful upgrade from 25.04.1 on my end, a few key points:
- My Incus VMs created under 25.04 now show up under “Containers” with Type=VM
- My classic VMs created under 24.10 show up under “Virtual Machines”
- Both the classic and incus VMs could be started and they are working
- I can’t see nor measure any performance degradation, all look normal
Edit: My upgrade path: 24.10.2 → 25.04.0 → 25.04.1 → 25.04.2
1 Like
Did you upgrade from EEL or were you already running Fangtooth?
I was on 25.04 since it came out. Then upgraded to 25.04.1 when that came out, and today 25.04.2.
I will update my original comment.
You sad your Classic VM’s show up. Were they setting there idle while you were running Fangtooth without VM capability and they just showed back up when you did .2?
Yes, my classic VMs just showed up again like nothing happened. I am super happy about this 
When I went 24.10 → 25.04 I “lost” the classic VMs. I thought it will be sorted out later so I didn’t touch the Zvols, I left them as they were. I created a few new VMs under Incus from scratch.
Cool that is a good point to reference for someone that did that. I stayed on EEL and am watching for some EEL to Fangtooth .2 successes before I pull the trigger.
2 Likes
Same here. I am currently running 24.10.2.3, with 13 apps, and 1 VM. I am also waiting for at least two people to report a successful upgrade before I commit to the upgrade. What I currently have works. I want to be reasonably confident that I don’t shoot myself in the foot by upgrading to 25.04.2.
1 Like
It is a good idea to monitor the Software Status page. Install the version only from the Conservative channel to avoid suprises. At least I will stick to this in the future unless I have an issue/bug which requires an upgrade.
I upgraded to 25.04 without reading the changelog, but then decided to stay on it to try out the Incus integration.
So if you do not have a real reason to upgrade, stick with 24.10 as it is rock solid for many out there and it is the current Conservative version.
Edit: Just FYI a few users reported a blocking issue in 25.04.02 with VMs: 25.04.2 Oh No my VM’s not working
So I bought into Incus for VMs and was hoping it would bring modern features like host path mounts going forward. Sad to see that’s not the case, but it is what it is.
I am curious, though, is it possible to delete an Incus VM in 25.04.2, even if I can’t make new ones? I’m down to one VM right now and was planning to completely re-image it soon anyway, and I’d rather get a clean slate on the “old” virtualization system (which hopefully will have less churn going forward).
Edit: Okay, it looks like there is an option to delete existing Incus VMs, just not add new ones. Interestingly, after updating, I also see a pre-Fangtooth libvirt VM sitting around (disabled by default). I would have expected that to have been deleted with the switch to Incus, but I guess not.
Upgraded from EE 24.10.2.3. No VMs. 6 apps all working just fine. All SMB shares working just fine. So happy for the Server Side Copy on macOS! Tested it and it works great! No issues to report. Seamless upgrade for me.
1 Like
Upgraded one server from 25.04.1 to 25.04.2 successfully. This is my secondary remote server that I replicate snapshots to for backup. It runs Tailscale as an app. No issues.
My main server upgraded from 24.10.2.3 to 25.04.2. SMB shares, apps, networks (including a bridge network) came across fine. But the “Virtual Machine” page showed only a large exclamation mark and “Can not retrieve response”. None of my “classic” VMs appeared at all (which is what I been waiting for in Fangtooth BTW). I rolled back to EE where my VMs showed correctly. Two Jira issues have already been submitted for this issue:
NAS-136940
NAS-136941
I ran into a pretty nasty bug. I updated to 25.04 during the beta and in the process created an Incus VM that pointed to my Home Assistant Zvol. With this 25.04.2 update, it seems that the old libvirt based VM started up alongside the Incus based VM, both of them using the same Zvol, which resulted in the VM’s filesystem becoming corrupted. I was able to create a new Zvol from a snapshot created last midnight and pointed libvirt to that and it works fine now.
This is a major issue though that could potentially cause data loss. There should be a check to prevent an Incus VM and libvirt VM from starting up if they both use the same Zvol.
1 Like
So I updated my Fangtooth 25.04.1 system to 25.04.2
The good news is my pfSense VM came up.
The bad news is that I expected to see a ghost of it in the VMs section, I didn’t, instead the VM section fails to load.
https://ixsystems.atlassian.net/browse/NAS-136943
Turns out the reason is because I don’t have a password for VNC, and its rejecting the data already in the database when it queries the list of VMs.
Additionally, performance of the cli app is attrocious.
https://ixsystems.atlassian.net/browse/NAS-136944
EDIT: Here is a simple fix to the issue:
2 Likes
I just completed upgrade from 25.04.1 to 25.04.2; for the most part uneventful. The only negative is disablement of Active Directory sync. I had forgotten about the MS patching issue brought up in last week’s video. I’ll see if I can figure something out. However, the good news is that I still can access the shares via AD account.
The biggest surprise is the incorporation of Microsoft OAuth for email. AWESOME JOB Guys, works as expected. Please share this code with the rest of the world, “in lights”. Since providers move to OAuth not many projects have incorporated a viable alternative.
Thanks @Stux for sharing ! I had the same issue after update from 24.10.2.3. Some of my VMs have VNC with no password. I went back to 24.10.2.3 and add password; I delete 25.10.2 boot environment et make the update again. Now the VM tab show all my VMs now and they are working !
1 Like