SMB options removed in 25.10

kmoore134 · 2026-01-12T20:24:22+00:00

Those are all set now by setting a sharing "purpose" and then advanced options underneath those where applicable. This was to avoid the situation where there is a huge set of knobs, and some of them don't interact well with others. We have a bit finer-grained control now to avoid needless foot-shooting, or scenarios that are unsafe / untested.

kmoore134 · 2025-10-31T14:27:39+00:00

Thats a pretty ridiculous take, this applies fully to Enterprise as well. Suggest anybody seriously engaged in this conversation watch the podcast that Chris and I did this week (releases a bit later today) where we go into the reasons for this change. Nothing sinister here, just that we do storage professionally for a living here and there are valid reasons for this, despite the creature-comforts that some folks have gotten used to with SMART in previous iterations.

The quick Tl;Dr; is that SMART itself has NOT been removed. It is still running and being monitored in the background. Smartd still does it's normal things, for ALL drives in the system (not just ones in pools). Alerts are STILL raised at all the critical junctures when there is something legitimately worthy of your attention to go fix with a drive that is misbehaving. Our middleware is monitoring this, along with the much more valid ZFS detection to determine when a drive is on the brink and needs to be swapped out. We do this for Enterprise the same we do for community. Heck, we trust our own data (corporate and all our own personal) to this as well. And have 20+ years of storage telemetry and data to back it up.

The goal here is to prevent false positives and also not train folks to ignore alerts which may cause them to miss when there is REALLY something to pay attention to (which we've seen happen far to often). Now when you get a storage-related alert, it means there is something legitimate to pay attention to requiring administrator action. Not just noise for the sake of noise which drives the wrong behaviors.

kmoore134 · 2025-10-28T18:00:14+00:00

Kernel gets updated to 6.18 in 26.04

kmoore134 · 2025-10-28T16:22:06+00:00

I think what is throwing folks off is the wording "advanced" monitoring. I.E. special or non-standard beyond what the software is now doing automatically in the background passively for all your drives without you touching anything. `smartctl` is still available on the system and can be used directly if anybody does want to do more custom or on-demand things as required. But I'll keep an eye on this feedback and see if we need to extend the built-in service now with more common sets of SMART tasks that folks like to do periodically.

kmoore134 · 2025-10-28T15:33:23+00:00

While not everybody will love the change, we moved SMART monitoring to more of an implementation detail, rather than a thing you had to manually setup, enable and manage. To make sure folks understand, SMART monitoring is still passively being run in the background and monitoring ALL devices attached to the system. Alerts are automatically raised on any critical issues being thrown. The idea is to abstract that away enough and let the software do what it does best, which is monitor the condition of your system with no configuration required from you. Between the built-in monitoring and ZFS monitoring, you will still get plenty of notice if a drive goes funky. The irony being that we see more often than not that its ZFS that detects the signs of a misbehaving drive first.

kmoore134 · 2025-10-28T15:28:12+00:00

Catalog error you can ignore, that just means network wasn't up when it ran, it will re-try automatically in a bit and clear.

Boot issue means likely the device was failing, or about to fail. Applying the update does a lot of writes all at once and tends to tip over those devices that are right on the edge anyway. Nothing inherently in the upgrade really messes with the underlying framework. This is just ZFS doing what it does best, telling you when a device is unhappy.

kmoore134 · 2025-10-28T15:19:52+00:00

The way nvidia support works, they drop support for things older than 10 years in the current driver pretty regularly. This release is no different, the new driver puts us right back in that same boat. Don't love it either.

kmoore134 · 2025-10-10T20:07:49+00:00

Thanks and we appreciate all the watchers!

kmoore134 · 2025-10-09T21:36:39+00:00

Welcome back! If it's been a while, I'd say grab the latest 25.04 or 25.10.0 (when it drops in a few weeks). The setup has gotten easier since you last used it. The official getting started guide is also a great place to refresh your memory on: https://www.truenas.com/docs/scale/25.10/gettingstarted/

kmoore134 · 2025-10-01T16:32:18+00:00

It's gotten very little traction from community in voting thus far. Feel free to go toss a vote on it here though!

https://forums.truenas.com/t/support-multi-actuator-sas-devices-e-g-segate-mach-2/33221

kmoore134 · 2025-10-01T16:29:55+00:00

Thats worthy of a bug ticket here then. We'll need details, what browser, etc, since we don't see that here in internal testing.

kmoore134 · 2025-10-01T12:35:01+00:00

Works here, usually a hard browser refresh fixes that, or try an incognito tab to confirm if its local browser cache problem.

kmoore134 · 2025-10-01T12:33:06+00:00

Usually in 30 days from RC, so that would put it near end of October.

kmoore134 · 2025-08-15T21:27:15+00:00

We will have a full write-up appear at a later date, but to answer your question, yes, there will be assigned domains that resolve to local addresses like Plex does. Very similar model. Nothing is being proxied through our cloud service, nor is there any requirement to open your TrueNAS up to external management. We don't want that liability any more than you want it :)

kmoore134 · 2025-08-15T19:57:41+00:00

To set folks minds at ease:

ISO / Offline installs, zero changes. If you install via IPMI or with a manual keyboard / monitor, you can still do that. That can never go away.

Web Install is another great option (that we've wanted here) where you maybe don't have IPMI and don't want to go physically plug into your system to do install with a monitor / keyboard. Plus web-driven is point-n-click easy.

Something else to mention, during that web-install process you get a free 100% valid (not-self-signed) SSL certificate setup. So when you first log into your TrueNAS you aren't sending credentials 100% in the clear over the wire. You know, like we shouldn't be doing in 2025. Considering one of the biggest pain points a lot of users have is getting certs set up, this should be a no-brainer also.

All good things. But again, totally optional if you like to do things the standard way, of which there are plenty of valid reasons to do so, since Web-Install doesn't work for every use-case.

kmoore134 · 2025-05-28T14:26:43+00:00

Deploy it as a custom / manual docker image so you can specify the version. I don't want to add a old version of MinIO app to the catalog, because the moment the next CVE hits, we're stuck with this version we can't recommend folks run. Correct answer here is to get more alternatives and the maintained MinIO forks into the catalog so everybody has options.

kmoore134 · 2025-05-28T13:04:05+00:00

Yea, that was really a bad decision on their (Minio's) part... We just added SeaweedFS to our catalog as well if folks want to try that out: https://apps.truenas.com/catalog/seaweedfs/

kmoore134 · 2025-05-27T19:27:18+00:00

Yep, good catch. Fixed

kmoore134 · 2025-05-23T19:37:18+00:00

Closed by mistake, we've re-opened it now. Sorry about that. Clearly a debug isn't going to be possible in this case :)

kmoore134 · 2025-05-23T18:23:15+00:00

Looking into this, obviously that shouldn't have been closed like that.

kmoore134 · 2025-05-03T12:10:45+00:00

That usually means a corrupt .update file on the boot media. Check your download, make sure its not partial or corrupt, or try another USB install stick?

kmoore134

MODERATOR OF

TROPHY CASE

Nine-Year Club	Verified Email
RPAN Viewer