Permission Issue - Change Owner on File

English Storage
1

Hey all,

After upgrading my TS-873A to Hero 5.3 I started having a problem with TimeMachine backups on one of my Macs. I cannot connect to my TimeMachine folder. I get an error. The other Mac works fine. And researching this problem only shows that it has to do with permissions and TimeMachine is very finicky about this sort of thing. So I opened an SSH session and looked at the permissions of my TimeMachine folder on the NAS. This is what I see:

[Jono@NA9D-NAS Tardis]$ ls -la
total 125
drwxrwxrwx 8 admin administrators    9 2025-09-27 07:46 ./
drwxr-xr-x 3 admin administrators    5 2025-09-24 10:06 ../
-rwxrwxrwx 1 Jono  everyone       8196 2025-09-27 07:44 .DS_Store*
drwxrwxrwx 4 Jono  everyone         11 2025-09-25 15:02 Jon’s Mac mini.sparsebundle/
drwxrwxrwx 4 admin administrators   12 2025-03-29 02:32 MacBook Air.sparsebundle/
drwxrwxrwx 4 admin administrators   11 2025-09-26 23:46 MacBook Pro.sparsebundle/
drwxrwxrwx 2 admin administrators   20 2025-09-27 07:30 @Recently-Snapshot/
drwxrwxrwx 4 admin administrators    6 2025-09-26 21:57 @Recycle/
drwxrwxrwx 3 admin administrators    3 2025-04-08 18:56 .streams/

The item I am having trouble with is “Jon’s Mac mini.sparesbundle.”

If you notice that is owned by user Jono and accessible to everyone. It should have owner admin and accessible only to administrators. I think that is my issue. What is the best way to fix this? I’m not a Linux expert so appreciate any advice.

2

If you want it all to match admin is just root.

So chown 0:0 "Jon\'s Mac mini.sparsebundle/" should work.
If you need it to be recursive I’d use xargs

find <someDirectory>/ -type d -print0|xargs -0 chown 0:0
find <someDirectory>/ -type f -print0|xargs -0 chown 0:0
3

@Weedy, why not chown -R ?

4

I’m used to using old or broken busybox versions so I just default to xargs.

If we have -R it should be same same

5

Thanks, guys. Unfortunately, I am not sure that’s the issue either. I renamed my TimeMachine sparse bundle to try to force TimeMachine to create a new one when it mounts the drive. It just won’t mount the drive. It sees it but gets an error when mounting it. And I’m not using a “new” Mac OS here. It’s Sonoma on my Mac mini but I’m running Sequoia on my laptop and it works fine. So I am rather perplexed about why I cannot mount the network share for TimeMachine…

6

I imagine you are signing into the NAS with the same passwords and that Sequoia doesn’t need SMB1 or something stupid right?

Debug level logging maybe?

image
image1158×822 70.3 KB

7

I’ll have to try but I don’t think it’s going to be anything that QNAP will tell me. From what I can tell, it’s logging into the NAS and seeing. It just won’t mount the share in Time Machine. Gives an error:

image
image336×275 27.2 KB

SMB1 is enabled as my Sonos system needs that.

Searches on this error are all about permissions, but from what I can tell, the permissions on the shared folder are fine - why would one Mac be able to access and the other can’t? So that doesn’t make sense. Apple in all their wisdom has made Time Machine a pain to troubleshoot. Reboot of the Mac didn’t help either.

8

Different user ID therefore different permissions?
Did you try as admin or set 777 permissions?

9

Maybe?

Error 5 trying to use time machine with a… - Apple Community

10

Yep. The shared folder has 777 permissions.

11

Yep. I read that in my searching for a resolution. I’ve got the smbd process already enabled for full disk access.