I like to think ixSystems aspires to be better than Microsoft. Talk about setting a low bar. 
2 Likes
To go lower than Micro$oft looks like a high bar to me. 
And “AI” to do their coding 
Welcome to the Community…. you get a free product and so you are not a “consumer”. Our lawyers have never lost a case…
I assume you didn’t read the software status page before being surprised? Its an easy mistake, but we do try to publiciize this. After having read it… is it good advice?
As part of the Community you do help us find and resolve bugs. The earlier you are in a release cycle, the more likely you are to find them. We thank you for good bug reports and help in any diagnosis.
In our defense…. TrueNAS is used on/with a huge variety of:
-
Processors
Motherboards
NICs
HBAs
BIOS versions
HDD versions
SSD versions
File protocols and options
Block protocols and options
Apps/Containers
VMs
Client OS versions (e.g MacOS SMB bugs)
GPUs
-
System Configs
For the Community Edition with BYO hardware, we make no claim that we can test it all. We rely on constructive Community reports. Hope you can join the Community.
We love the Testers and Early Adopters … they make the world go around!
For our Enterprise products we can constrain this set and deliver quality with thorough testing. The Enterprises pay for this robustness…. they have the rights to sue us.
14 Likes
Status update:
TrueNAS 25.10.0.1 has addressed many high-priority issues and is being widely deployed. It is now the 2nd most popular TrueNAS version and recommended for early adopters.
TrueNAS 25.04.2.6 is still the recommended version for General - & Mission-Critical users.
The distinction will remain for a while. TrueNAS 25.10.1 is planned for the week before Christmas. It has many minor improvements/fixes. After it has many tens of thousands of systems, it will become a candidate for recommendation to General.
Refer to the Software Status page for the latest recommendations.
4 Likes
I’m gonna stay on that big green column for a while, it’s comfy there.
5 Likes
@Captain_Morgan Thank you - not sure what the many combinations of hardware have to do transparency on the website? No I didnt read the software status page. How am I supposed to? If I want to download TN, I google for “TrueNAS download”, as I do it with all software. This takes me to a page, where I get several links. First a compare of enterprise and community, second to a post from Kris from 2020, where it clearly states: “Release is for business users”. I have to give to you, if I check the “reelase notes”, its says:
For adventurous users who want to experiment with the latest feature development, 25.04 (Fangtooth) nightly images are available from the TrueNAS downloads server.
Ah hang on, thats still fangtooth… thought this is stable now.
After clicking “No Thank you, I have already signed up.” It gives me a green button stating stable for 25.10. Green has a positive association, so does the term “stable”. Stable is much closer to the two categories, “general use” “mission critical” than it is to “early adoptors” / “developers”. So I click this. Lets speak about the meaning of “legacy” and grey buttons. Often grey buttons indicate its not working “greyed out”, legacy is often not maintained etc. So why would I click this grey button?
I m perfectly sure you guys at iXSystems know this pretty well and you did this on purpose. If you use your community as QA / beta testers, thats fine - happy to contribute - but voluntarily and not being tricked into this, in particular if if I pay for the “free” product with my time….
3 Likes
That’s a fair point… we can’t control Google, but we can maintain that on our download page. It wa the first edition of CE (then known as SCALE). I’ll get that link removed or a better doc created. Do not use: TrueNAS SCALE: The voyage begins with version 20.10 | TrueNAS Community
The Software status page is the place we want people to go. It’s on the download page. I assume it had the information that was needed. Should we highlight it more?
“Stable” vs “Legacy” is an interesting question. We use “stable” for 25.10 because it is where development is still ongoing and bugs will be fixed. If you found a bug in 25.04 as a Community user… it would most likely be fixed in 25.10. So we mark 25.04 as “Legacy” even if the Software Status page recommends it for General and Mission Critical.
(side note: we would fix 25.04 bugs for Enterprise users. They have to stay on Mission Critical versions. The Community users benefit from that process.)
I really don’t think it is. Unless someone already knows about the shenanigans you play, they’re going to expect that “stable” means stable–a release that’s been thoroughly tested, with minimal bugs, and suitable for your average user. IOW, it should mean the same as “recommended for general use.”
9 Likes
I agree with above definition of STABLE:
TrueNAS “Stable” Release has gone through 4 stages of rigorous testing
(2 weeks for each version - ALPHA, BETA, RC1, .0)
About 20,000 test systems (that is a lot)
Has well documented release notes with known bugs
And is suitable for average Community users
Its also the release that will get new bug fixes (as opposed to LEGACY)
Like Windows, MacOS, Linux, there is no claim that any version of TrueNAS is bug-free. The reason why any software gets minor updates is to fix bugs, some of which are caused by third parties.
We agree that there are heavy/business users who should wait for higher quality. However, that quality will not happen without average users testing with new releases. See Software Status.
If the Software Status page is wrong, we need to fix it. If someone doesn’t want to read the Software Status or release notes, that is their choice. We provide the free tools. Feel free to criticize the tools and suggest improvements… we make a lot of them. See the following blog:
If someone doesn’t like using free tools, then the option is to buy the TrueNAS products. We will happily deliver a product with fewer surprises and better support. We just cannot afford to do that for free.
The bottom line is that TrueNAS users get the experience they earn through being careful and reading the relevant docs. The forum lets people share that information and wisdom more easily. We do not hide any bugs… we transparently monitor, document and fix them with everyone’s help.
1 Like
Updated from 25.04 latest to 25.10.0.1 and joined it to a new Server 2022 with Active Directory.
-
It refused to join the find the realm for the AD until I manually input the realm on the Advanced Kerberos panel.
-
No matter what setting I choose it’s inventing it’s own UIDs/GIDs for my AD users. Initially I left the UIDnumber and GIDnumber null in AD as all my linux systems joined fine and have the same #’s but later I input them (UIDs/GIDs) into (AD) to match what my linux machines where showing. I’ve dis-joined/re-joined over 2 dozen times today, rebooted, rebuild AD cache and run out of things to try. *Note just to add I say inventing numbers as I don’t know where it’s getting them from but they are the same numbers through all the re-joins.
Any advise is appreciated as I’m fixing to reload 25.04 at this point.
I’d recommend starting a thread in TrueNAS General with all the details.
You can provide a link from this thread.
Link is here: Cannot get newly updated 25.10.0.1 to pull correct UIDs/GIDs from new Server 2022 AD
1 Like
I cannot put a link..
Read the F(ine) Documentation. In this case the mail you got from the forum bot about taking its tutorial, and you’ll be able to post links.
2 Likes
No matter what setting I choose it’s inventing it’s own UIDs/GIDs for my AD users. Initially I left the UIDnumber and GIDnumber null in AD as all my linux systems joined fine and have the same #’s but later I input them (UIDs/GIDs) into (AD) to match what my linux machines where showing. I’ve dis-joined/re-joined over 2 dozen times today, rebooted, rebuild AD cache and run out of things to try. *Note just to add I say inventing numbers as I don’t know where it’s getting them from but they are the same numbers through all the re-joins.
This describes default truenas behavior and is not a bug. If you have an existing environment, the onus is on the domain administrator to understand how you are assigning IDs to a variety of domain clients and make sure you do it consistently.
By default TrueNAS will assign uids / gids server-side algorithmically based on the RID value of the active directory account.
Some linux distros use a different algorithm for determining uids/gids (and it’s actually configurable). Some domains have populated Unix identities (uids, gids, etc) in the AD schema for users and groups.
There’s literally no way for us to know how you want the domain configured and so we choose something default and safe (values we’ve been using for around the last 7 years). Since this is surprising, I suggest taking some time to investigate how you’re doing this in your domain and then configure the “IDMAP domain” section of the UI in the directory services form accordingly.
I think some extra prominence for the Software Status link on the download page would be very helpful to mitigate against this fairly easy mistake being made 
4 Likes
Interesting how version 13.0-U6.7 is by FAR the most popular, when it’s so old, and 25.04.2.6 is so unpopular. /s
3 Likes
Lol - yeah some better colour variety in the bar chart may have been better. Or maybe core is still the most popular; @winnielinnie will be so happy.
3 Likes
FYI… CORE is about 27% of systems still and dropping slowly by about 7% a year. It’s still a fine and reliable OS if you don’t need Apps and VMs. If a NAS is 5 years old, it’s probably not going to upgrade. It will just retire-in-place.
Color coding is better today.
2 Likes
I personally find this quite confusing. “Stable vs Legacy” is something quite different from “Early Adopter vs General or Mission Critical”.
I’d probably rename it to LATEST and STABLE (although as the current naming also has a “STABLE” this might also confuse people so maybe… LATEST and rock solid 
?)
3 Likes