After the update to TOS6 I can't use my F2-423 as target for Time Machine backups anymore. The initial backup finishes without error and I can access and restore from it. But if I want to start a new backup from my mac it doesn't come past "connection to backup disk" and stops with the error "The backup disk image “xxxx.sparsebundle” could not be accessed (error 19)."
During the time, when the mac is trying to connect to the nas I can see a lot of smbrichacl processes, maybe they lock the sparsebundle-files?
Any help is highly appreciated - Thanks Michael
Can't use Time Machine after initial backup
Re: Can't use Time Machine after initial backup
Thank you for your feedback. We are inclined to conduct a more in-depth examination of your error message. Kindly open the desktop Technical Support - Problem Feedback, and send the error log along with the screenshot to our after-sales engineers via email.
Re: Can't use Time Machine after initial backup
Also, what is your macOS version number?
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Can't use Time Machine after initial backup
As suggested above I just send an issue report to tech support.
fwiw:
my Mac is a MacBook Pro - 13-inch, 2017, Two Thunderbolt 3 ports
macOS: 13.7.1 (Ventura) - this should be the latest for my model
fwiw:
my Mac is a MacBook Pro - 13-inch, 2017, Two Thunderbolt 3 ports
macOS: 13.7.1 (Ventura) - this should be the latest for my model
- lunahart63
- Posts: 1
- Joined: 28 Nov 2025, 11:31

Re: Can't use Time Machine after initial backup
I’m experiencing a similar issue with Time Machine and my NAS. After the initial backup, subsequent backups fail at the connecting to backup disk stage with a sparsebundle access error. I also noticed multiple smbrichacl processes running while the Mac tries to connect.
Could you share if the technical support team suggested any solution or workaround? Also,orbit beats did you check permissions on the sparsebundle or try connecting via a different SMB version?
Could you share if the technical support team suggested any solution or workaround? Also,orbit beats did you check permissions on the sparsebundle or try connecting via a different SMB version?

