Thread: Time Machine Slow then stops...

Hey all. Hope this is the right place since Time Machine is software, even though it uses network ID...

I can't get Time Machine to function correctly. It loads up find and sets up as normal. However it is very very very slow. The first backup is always the longest because it is copying your entire drive however, it shouldn't take 10 minutes to only be at 700MB out of 250GB

First it starts slow getting to a MB after a minute then it speeds up but every time it gets to around 27GB copied it doesn't move.


Any insight in this? I'm used EFI 10.3, Cham RC3 and the lifehacker guide.

Update... Seems to happen only if I plug the external via firewire. USB is fine and if I use an internal it's fine.

So anyone having firewire issues? I can read and write the drive but time machine doesn't like to firewire it.

Originally Posted by Bluenotes

Update... Seems to happen only if I plug the external via firewire. USB is fine and if I use an internal it's fine.

So anyone having firewire issues? I can read and write the drive but time machine doesn't like to firewire it.

I'm using Firewire only with my Sony HDV Camera and this worked fine under 10.5.8, but is still untested under 10.6.

Originally Posted by AsereBLN

I'm using Firewire only with my Sony HDV Camera and this worked fine under 10.5.8, but is still untested under 10.6.

Yeah. Mine worked too under 10.5.8 (EFiX).... hmm... adds to the mystery. Thanks for the input though

Boot in verbose mode and see if you're getting a line that says something like "FireWire: Unable to determine security mode. Defaulting to Full-Secure."

Full-secure mode will cause data transfer problems.

Originally Posted by Mike

Boot in verbose mode and see if you're getting a line that says something like "FireWire: Unable to determine security mode. Defaulting to Full-Secure."

Full-secure mode will cause data transfer problems.

I do get this line with the full-secure mode on my onboard FW.
What can I do about that?

(I'm not using firewire at the moment, but likely will do in the future).

A combination of a patched DSDT and fakesmc.kext should fix it.