It accepted the command but the subsequent backup failed. Based on other tips I tried using tmutil from the terminal to manually point to my backup target. Based on (ancient) tips from Apple's support forums, I renamed the target of the AFP:// credentials, renaming ".afpovertcp._tcp.local." to both ".local" and to ".local." This didn't solve the problem either. I deleted all credentials related to anything AFP:// in my Keychain and recreated a connection, and that did not solve the problem. I created a second AFP share which I too can access for both reading and writing, but Time Machine keeps repeating that the credentials are wrong. When I connect to the share I use for TimeMachine using Finder, or, after mounting it, using Terminal, I can create directories and files on it. You may need to re-select the backup disk and enter the correct username and password." "The network backup disk could not be accessed because there was a problem with the network username or password. I've had a few error messages along the way, but the short of it is this: Yesterday I rebooted my MacBook Pro (late 2013 retina), probably for the first time since installing Sierra, and my backups stopped working. The solution is based on netatalk and avahi-daemon and has mostly been robust as long as the actual network connections have been good. I've been running Time Machine backups to my Linux home server (currently running Ubuntu 16.04) for as long as I've had Macs. Just putting this out there, primarily wondering whether this seems to be a common problem, and secondarily if anyone of you guys here has any additional tips for troubleshooting beyond what I've already done.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |