If you are talking about the “update is available” bug… yes it will be fixed in a future release. I expect 25.04.2 based on this bug report:
thank you. yes that is what I was talking about
Manual repair is no big deal. You just navigate to a system directory, find the file there and delete it. The instructions are right but also make it sound scary. It’s just deleting a junk file, that’s all.
FYI: TrueNAS 25.04.1 is now the most commonly used version of TrueNAS.
Thanks for all the testing and validation!
There will be more improvements in 25.04.2 but we now view this version as supportable for Enterprise use.
When is the .2 slated for release?
We’re still working through the issues to identify what will be included. After that we’ll schedule. I expect some time in July.
What does that mean exactly and with reference to the status page which still has 25.04 as “early adopter” status? Presume you mean 25.04.2 also.
I imagine that supportable is not the same as recommended.
Clear as mud
It’s a complex ,multi-dimensional problem.
We recommend 25.04.1 for users that benefit from the new features like fast dedup and Fiber Channel. We support them and have assessed the quality is acceptable with very low probability of seeing a disruptive issue…
For users that don’t need the new features, we currently still recommend 24.10.2.2. Its been validated by more users for 6 months longer. It has an even lower probability of seeing a disruptive issue.
That will change over the next 2-3 months.
So if you want black and white clarity… my answer is “turqoise”.
Does that clear the mud? @rungekutta
Thanks for the colour and yes what you write makes logical sense in itself, but it’s another line of reasoning to your official documentation elsewhere - also, isn’t this community edition you are talking about, are you now saying you want enterprise users on that?
I generally focus on the generic truenas… the same logic applies to Community Edition vs Enterprise, just some of the important features are different.
Where exactly? Happy to update documentation if it will clear up confusion on this. In fact we have a ticket open to update some of the lifecycle content in the next few weeks, but I’d be happy to add your notes to it.
I was thinking primarily of your software status page where for Enterprise you make no mentioning whatsoever of 25.04, in fact you still have “early adopters” and “testers” on 24.10. Which doesn’t seem compatible with the comments directly above.
Ah ok. When you said “official documentation elsewhere” I thought you meant somewhere else in the Docs Hub.
You’ve caught us in the waiting period.
25.04.1 came out May 27… we generally start to update the status page for Enterprise a few weeks later. The Community is our extra QA phase…thanks for helping out.
Changes are imminent.
This update caused several issues with the boot pool. I have two mirrored disks for the boot pool and another mirror for the data pool. After the update, the system would boot for a few seconds and then show an error related to the boot pool before freezing completely.
Initially, I suspected a hardware problem, so I replaced both boot disks with new ones and restored the configuration. Everything worked fine until I updated again to version 25.04.1 — after rebooting, the same issue occurred.
After some research, I found that the problem might be related to the instances. From the shell, I deleted all instances and reconnected the old boot pool with the original two disks. Then, from the boot menu, I selected an older snapshot (25.04) and booted from it. Once the system started, I set that snapshot as the active boot environment.
So far, everything seems to be working fine. I will hold off on any future updates until the next major release, as this one caused significant downtime and wasted a lot of time troubleshooting.
Please report a bug, so that we can at least track this. All details are appreciated as they may help replication of the issue.
Were you unable to use the blue grub selection screen to choose a different boot environment?
Even when booting from version 25.04, I eventually encounter the same issue after some time.
From my observations, the issue began after I attempted to create Windows 11 virtual machine instances—that’s when all the problems started.
These two forum posts helped point me toward a resolution:
- Virtual machine instances break after moving System dataset pools. 25.04 - #7 by Eddez
- Upgraded to 25.04 from 24.10 - fails to boot - #8 by craigywsm
To recover the system, I did the following:
- During boot, I used Option 8 to access the shell.
- I deleted all three files related to
middlewared
located in the audit folder. - I removed all virtual machine instances using:
incus list
incus delete
- I disconnected the data pool
- I then booted into the 25.04.0 environment.
- After verifying system stability for a while, I reconnected the data pool and restarted server
So far, the system has remained stable. I have not attempted to update again to 25.04.1, as I’m cautious about triggering the same issue.
I suspect the root cause is more closely related to the Windows 11 instances, rather than the system update itself. However, I haven’t yet confirmed this theory by testing 25.04.1 after removing the instances.