You mean the “null” output? That is to be expected. You can safely ignore stdout from the command.
just realised that after updating that my cpu temps dropped by almost 12°C and cpu usage doesn’t spike as often as it did before the update.
1 Like
The Time Machine backups to TrueNAS 25.10 could be silently corrupted. I zfs rolled back to an earlier snapshot of my Time Machine backup and right-clicked on the destination and chose “Verify Backups”. After a long time, Time Machine reported that the backup was corrupted and would no longer use it.
I started a new Time Machine back from the same macOS 26.1 Mac to a different TrueNAS running 25.04.2.5. That worked. So:
macOS 26.1 → TrueNAS 25.10 = Can’t create new Time Machine backups; may silently corrupt existing backups.
macOS 26.1 → TrueNAS 25.04.2.5 = Can create new Time Machine backup; can’t fix corrupted backups (as expected).
1 Like
Were the problematic backups created in 25.10.0 (before the fix in this release) or in 25.10.0.1?
The existing Time Machine backups were created over 1 year ago. Time Machine has been adding to and pruning them as needed for some time now. They’ve been working fine with TrueNAS versions 25.04 and prior. It was after a few weeks on 25.10 that Time Machine reported the corruption. While troubleshooting, I saw that even new Time Machine backups could not be created on 25.10.0 and 25.10.0.1 (Using macOS 26.1).
Might be related to this: https://bugzilla.samba.org/show_bug.cgi?id=15926
Looks like the bug report upstream was just reopened with an additional fix. We’ll bump samba minor version in 25.10.1 (which will include fixes for the referenced bugzilla report).
The additional fix addresses a potential NULL dereference / crash if the client sends a NULL (as opposed to empty) DACL.
2 Likes
I may have a new SMB issue after the 25.10.0.1 update. Ref: New 25.10.0.1 SMB Issue - Windows cannot access TrueNAS server, Error code: 0x80070035
I doubt that’s related. It looks like wonky broadcast resolution trying to use either netbios or WSD. Generally relying on broadcast protocols for mapped shares is not a great UX. Either use DNS or IP addresses.
1 Like
Don’t take my word for it, but I think maybe your system dataset lives in your boot drive where there isn’t much extra space. I moved my system dataset to a big pool years ago and don’t run into this. Something you can try.
another boring update
YAY!
2 Likes
to my understanding, this new version will remove sleep. fine. but how does this affect for hard drives added as spares? r the spares in sleep mode until they get actively added when a hdd dies and gets removed from the raid array?
just wondering if the spare is ALSO spinning as well 24/7 
No, it was always on the datapool, as the boot was always small, first 8GB, now 16GB.
My understanding was that unless you initiated a spin down script, that all drives spun all the time, including spares. Thats why I pull my spares after I qualify them. It’s simpler for me to have them stored in their carts next to the NAS, ready for use should the need arise.
1 Like
FWIW, I made the jump from 25.04.x to 25.10.0.1, bypassing the RC and the 0.0 candidates. I just ran a verification check on my time machine backup (pretty ancient and about 1.4TB worth of data) and it reported no issues. At least for now.
3 Likes
I see what you did there. 
2 Likes
… not intentionally, I swear!
1 Like
anyway hows 25.10.0.1
any issues? all good?
From my perspective, all good. The two big issues that I experienced was the SMB drive issue with disappearing directories and the App startup failing after reboot. Both appear to have been addressed with the 25.10.0.1 update. 25.10 also introduced a feature that allowed me to migrate the .ix-apps from the HDDs to the SSDs quite easily, and I did that yesterday and today noticing nice speedup changes with Audiobookshelf, Kavita, and Plex.
Still, the SMB issue has made me wary of newer 26.04 and 26.10 releases, so when the opportunity presents itself, I will be changing the release train from “Early Adopter” to “General”
4 Likes
TimeMachine keeps failing here too. Started with 25.10 - and then TM would start the backup process and fail after a shorttime or few minutes (few GB written). Now updated to 25.10.0.1. Newly added the TM share and now it wont even write to the share… it creates folders, but these are empty.
1 Like