TM share setup not working - should I wait?

TrueNAS General
,
1

I have a strange issue and I am not sure which side it may be on. Setting up the tm share as described in the docs (doesn’t matter if dedicated user/share or auto dataset creation). TM starts to create a sparsebundle (something xxx.incomplete) and fails at the end in the process of renaming.

2025-11-23 21:30:22.301510+0100 0x380fd Error 0x10a32a 296 0 backupd: (TimeMachine) [com.apple.TimeMachine:DiskImages] Failed to rename ‘/Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini 2025-11-23-212722.incomplete’ to ‘/Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini.sparsebundle’, error: Error Domain=NSCocoaErrorDomain Code=513 ““mini 2025-11-23-212722.incomplete” couldn’t be moved because you don’t have permission to access “timemachine”.” UserInfo={NSSourceFilePathErrorKey=/Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini 2025-11-23-212722.incomplete, NSUserStringVariant=(
Move
), NSDestinationFilePath=/Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini.sparsebundle, NSFilePath=/Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini 2025-11-23-212722.incomplete, NSURL=file:///Volumes/.timemachine/truenas._smb._tcp.local./121DC4FE-F07B-4D11-AE50-73D141C8BA32/timemachine/mini%202025-11-23-212722.incomplete, NSUnderlyingError=0xc85e248a0 {Error Domain=NSPOSIXErrorDomain Code=13 “Permission denied”}}

I checked the permissions and the ACLs but no luck. The backup to an older NAS works like a charm. I can’t really understand where the permission denied comes from. If I access the mounted share I can do anything I want from the command line.

Now I am wondering if I made a mistake setting up or its some bug combination and I better wait for updates?

2

I’m having the exact same problem. Have you found a solution yet?

3

https:// discussions.apple .com/thread/256137390?sortBy=rank

This solved it for me. When you make a timemachine copy a disk image is created. The name of this image can contain special characters like äó and this is currently broken on osx.

You have to make a copy, let it fail, acces the SMB share, mount the image on disk utility, change the problematic characters, force to backup again.

For once it was a macOS Big, not me misconfiguring my shares! Lol

1 Like
4

The actual disk image had special characters? mine is named “mini.incomplete” to be renamed to “mini.sparsebundle”, so I wonder where the special characters may be?

5

I’m having also exact same problem.

Trying to setup Time Machine backup from existing mac to a new Truenas server (version 25.10.0.1) but it fails on renaming from xxxx.incomplete to xxxxx.sparsebundle.

Don’t see any special characters as well.

Have you found any solution yet @thinkberg ?

6

No, it looks like it’s broken at the moment. In this post it points to a general issue:

7

I reported this on Jira, another of the countless bugs in Goldeye :frowning:

1 Like
8

It seems that the TrueNAS people “cannot reproduce” this issue but I can clearly reproduce it.

Has anyone else had any luck fixing this issue? Or working around it to restore the Time Machine backup functionality? It works well on a system that I upgraded to the latest version, but not a freshly created system.

9

It’s pretty disappointing, as the answer is it will work in 25.10.0.1 while the ticket clearly states, it is affecting 25.10.0.1.

10

I have basically reopened the issue: Jira

I just had it again set up and created the share and tried it. To no avail.

11

I managed to work around this issue by using rsync between the old host and the new one.
Then, Time Machine worked without a problem and I could back up to the new machine just fine.

12

I also have the same issue on the clean installed TrueNAS 25.10. Before clean installing, it works.
I tried to recreate data sets and SMB shares, but it didn’t work :frowning:

13

The ticket I created was closed with the comment, it will be handled in 25.10.1

2 Likes
14

Yep, got the same answer pretty much for my ticket.