Tried to patch in the rasdaemon today to send ECC stats back to the monitoring node (since TrueNAS does not provide these stats, which is fine) and got hit with:
Err:1 https://apt.sys.truenas.net/fangtooth/25.04.0/debian bookworm/main amd64 libdbi-perl amd64 1.643-4
404 Not Found [IP: 136.0.77.4 443]
Err:2 https://apt.sys.truenas.net/fangtooth/25.04.0/debian bookworm/main amd64 libdbd-sqlite3-perl amd64 1.72-1
404 Not Found [IP: 136.0.77.4 443]
Err:3 https://apt.sys.truenas.net/fangtooth/25.04.0/debian bookworm/main amd64 rasdaemon amd64 0.6.8-1.1
404 Not Found [IP: 136.0.77.4 443]
E: Failed to fetch https://apt.sys.truenas.net/fangtooth/25.04.0/debian/pool/main/libd/libdbi-perl/libdbi-perl_1.643-4_amd64.deb 404 Not Found [IP: 136.0.77.4 443]
E: Failed to fetch https://apt.sys.truenas.net/fangtooth/25.04.0/debian/pool/main/libd/libdbd-sqlite3-perl/libdbd-sqlite3-perl_1.72-1_amd64.deb 404 Not Found [IP: 136.0.77.4 443]
E: Failed to fetch https://apt.sys.truenas.net/fangtooth/25.04.0/debian/pool/main/r/rasdaemon/rasdaemon_0.6.8-1.1_amd64.deb 404 Not Found [IP: 136.0.77.4 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Did a sanity check and yeup, the apt repos were taken down. 25.04.1 is the only repo available for fangtooth. This box is about 8 months old, 25.04.0 was released on April 15, 2025…
Is it expected that every TrueNAS box, everywhere update every time there is a new patch?
If so that’s an insane level of maintenance and instability for a storage appliance. Even rolling distros have longer maintenance windows!
This literally sounds like the community needs to maintain mirrors of the apt repos so TN boxes don’t brick themselves after 2 months.
The only way to update anything in TrueNAS has always been “wait for and then install the next TrueNAS update”. Even back in the FreeBSD days. There are no user servicable parts, it’s not Linux, it’s “firmware” for an appliance.
And of course users are expected to keep their firmware current. Just like with any other network or server product. OPNsense for example.
With all due respect Pat, that neither acknowledges nor addresses the question at hand.
The question has to do with the entire support infrastructure behind a release being blown away in less than 9 months, meaning that every user MUST subscribe to a monthly rolling release cycle. I know you can’t be so obtuse as to believe that iXSystem’s professional storage appliance platform mandates monthly rolling releases by all users, especially developers working on support tooling, and especially vital to support tooling like the edac ecosystem components.
To underline the point, Fangtooth, v25.04 is the CURRENT MINOR VERSION of TrueNAS.
Additionally, I’d recommend not drawing parallels to software whose internals and underlying dynamics you are unfamiliar with. OPNsense is actually the exact opposite to this specific example. Part of OPNsense’s long term stability and viability is because it provides package repos dating back to OPNSense 17 which was released on Jan 31, 2017, almost 9 years ago (core repo at: https://pkg.opnsense.org/). This is because it is expected that managers of appliances will not update a box unless there is a specific security or feature reason to do so. Doing so would introduce an unacceptable element of instability and compound the maintenance burden.
This is doubly true for core infrastructure components like storage boxes, routers, directory servers, and switches. It is a common badge of honor to have an uptime of at least 365 days on any core infrastructure component; it is a testament to how well it was built, managed, and serves its intended purpose.
OPNsense releases minor updates every two to four weeks and you are absolutely supposed to stay on top of the current version because most of the time security updates fixing published CVEs are included.
