Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Time Machine bug 26.6 Beta
- Thread starter QINirvana
- Start date
- Sort by reaction score
A simple reboot might fix this. If not, try deleting the backup folder as a destination and adding it back in.
I rebooted my Mac and NAS, deleted the old backup folder and created a new one, played with SMB settings on the NAS, nothing has worked. You can read and write to the backup folder from the Mac, but Time Machine fails with the message "Backup Disk Not Available." I submitted a ticket.
I’ve tried almost every method I can think of (including your advice), but I still can’t get it to work. I can’t back up, I can’t downgrade — all I can do is wait for the next version to fix this issue.
I’ve tried the same steps you mentioned, but unfortunately, no luck on my side either. all I can do is wait for the next version to fix this issue.😂
I have the exact same problem, and its driving me mad! Glad (in some weird kind of way) that its not just me that its affecting
If you have a spare drive around, might be worth making a Carbon Copy Cloner backup in the meantime.
I'm having the same issue and formatting the NAS and trying to setup as new still fails. I reported it already.
Yes I ran into this too. I thought it was some type of authentication (and maybe it is) but I tried a number of ideas and none of them have worked. I am a bit worried that Apple will say that Time Machine backup over SMB to third-party devices is not supported.
I submitted a Feedback Assistant report to Apple with the detailed info including Console logs for time machine.
I submitted a Feedback Assistant report to Apple with the detailed info including Console logs for time machine.
Last edited:
adrianlondon
macrumors 604
It's a bug in the beta - there's no fix apart from hoping it's fixed in the next beta. Either backup files manually, or use Time Machine with a usb drive temporarily.
AFP is being obsoleted in MacOS 27. SMB is here to stay, so no worries there.
AFP is being obsoleted in MacOS 27. SMB is here to stay, so no worries there.
Same boat on a Synology here — TM over SMB falls over on 26.6 beta but a directly-attached USB SSD as a second destination keeps backing up fine, so it's specifically the network path that's broken. For anyone who can't tolerate the gap, you can add a USB drive as a secondary destination (System Settings → General → Time Machine → Add Backup Disk) and macOS will alternate; the SMB target sits there error-ing without disturbing the local one. Worth pulling Console logs filtered on "backupd" before you submit Feedback — the error code under the hood tells you whether it's the mount, the sparsebundle, or the keychain credential that's choking, and 26.5 had a different fingerprint than what I'm seeing now.
From here:
I updated to Golden Gate last night and Time Machine was fixed, as you indicated it had for you. Thanks for doing this and putting here on Reddit! SOLVED thanks to you.
So I will try that after I backup to a usb disk
adrianlondon
macrumors 604
iPunkB
macrumors newbie
yep, just updated to macOS 26.6 Beta 2 and it is now backing up to my normal Time Machine drive, (been using a temp external hard drive since I found this thread last week)