I’ve TrueNAS 25.10.0.1 on my NAS and existing users are working fine, the first connected created a data set and they’ve been backing up for a while fine.
This week I created a new user, and Time Machine cannot complete its first backup. It successfully creates a temporary sparsebundle, populates it with ~1MB of data, and tries to rename it to .sparsebundle and according to the TM logs, this rename fails with permission denied.
The user obviously has permission to write into the new dataset as they created a temporary bundle. I’ve looked over all the settings and permissions that I can find and can’t see any differences that would cause this.
TM is broken in the latest version of Scale; seems like the storage is making a read only folder. It was scuffed in. 0 now it’s busted in.1. SMB is fixed but that’s cold comfort and unrelated to your problem.
I suggest you find the other threads about this (including the long page with the dot 1 announcement) and see if you can offer more info so the devs can chase it down. The more log data the better, ultimately.
Wow, I thought I was going crazy. Seeing this exact same thing - my laptop which is already set up for TM backups works just fine, but my other machine can’t set it up. Seeing the exact same thing - the sparsebundle can’t be renamed in initial setup due to a permission error. Haven’t been able to get it to work no matter how I fiddle with things.
Same here, cannot complete my first Time Machine backup, it just fails with “The backup disk image could not be created.”
Just installed 25.10.0.1, created a dataset with “SMB” as the preset. In Shares, I go to SMB, add, selected that dataset I just created as the path and chose “Time Machine Share” as the purpose. On my mac with Tahoe 26.1 I go to Time Machine in the Settings, select the destination that now shows up, auth with the account I created for that share and then choose to back up now and pretty much immediately I get the error
Created this Jira ticket (https://ixsystems.atlassian.net/browse/NAS-138730) since the other recent ones mentioning Time Machine did not seem like this issue
