Imported from the Apple Support Forums via the Wayback Machine 🔗
Here's what an Apple Tech did with me today. #1) In Airport Utility make sure that all names for our TC and Net have only 8 characters or less, with no spaces, apostrophe's or underscores. #2) Make sure in Finder Prefs you check the box that says "show connected servers on desktop". #3) If you've never gone into your System Prefs "Sharing" folder and put something in the Computer Name Box (such as what you call your HD), TC/TM will not know what it is they're supposed to be making a 'disk image' for; that's the main reason for that error. Hope it helps!
Imported from the Apple Support Forums via the Wayback Machine 🔗
That seems to have done it for me. Would have been nice to have this in the documentation. Sometimes "cool" and "minimal" get in the way of "useful" and "effective"
0
John Kinard·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I suddenly starting getting the same error on my Airport Extreme with external hard drive attached. Time Machine backups were working fine for a couple of weeks, then started getting that error. Unplugging the Airport Extreme, then plugging it back in corrected the problem.
0
antlib·
Imported from the Apple Support Forums via the Wayback Machine 🔗
thanks for sharing this!!! I suddenly see my TC on my desk top!!!! After searching for it for 24 hours.... I really appreciate you taking the time to share this.
Have a great day!
Wendy
0
mruiz1021·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks so much for this! I did what you said and it seems to be working now!
0
CAGuk·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Works like a charm! Thanks very much!
0
Sapphire71·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This worked for me as well. Not sure what did it though. Is the 8 character name stuff for real? I am guessing it had more to do with Finder Prefs.
0
Mark Walkosz·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well I'll be ******!! It worked!! Thank you! Why doesn't Apple publish this to begin with?? Would save all of us from a bunch of heartburn!!
0
Max(IT)·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Sapphire71 wrote:
This worked for me as well. Not sure what did it though. Is the 8 character name stuff for real? I am guessing it had more to do with Finder Prefs.
I'm using a 6 characters name, with a space, and it's working fine since day one
0
lmeyer·
Imported from the Apple Support Forums via the Wayback Machine 🔗
unfortunately, didn't work for me. finder pref set, disk name is small, deleted the sparse file, but still getting the error. it works fine on the mac that i setup the tc with, which is powermac g5, but won't work with my powerbook...also do have a name for the computer...
0
d1g174l·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Basically Time Machine seems to be having trouble creating and/or mounting the sparseimage properly. The advice here is to create your sparseimage locally and then copy it to the TM drive or network drive you intend to use manually. It fixed this problem for me after all of the above advice did not.
Cheers,
d1g174l
0
Dr. Chris·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I struggled with the same problem, and your remedy worked perfectly. Thank you.
0
tim.jeffries·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Really great link up thanks so much d1g174l
0
warenext·
Imported from the Apple Support Forums via the Wayback Machine 🔗
For those of you using a third-party Ethernet card in your Mac, be advised that Time Machine seems to require the sparsebundle on the network share to be named using the MAC address of your built-in Ethernet, even if that's not the adapter you're actually using on the network.
Check the system.log in Console to see if Time Machine is trying to create a sparsebundle on the network share that has a different name from the one you put there.
0
rdinap·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had the same problem, but all I did was #3 and that alone solved the problem.
0
Victoria Carlin·
Imported from the Apple Support Forums via the Wayback Machine 🔗