TimeMachine stuck

DDKD726 · Mar 19th, 2009, 12:22 AM

I bought a new drive for time machine. Reformatted it to Extended(Journaled) and it gets stuck at 58gb every time. I've tried to repair the disk in DiskUtility but it can't find any problems with it. I also repaired permissions on my internal drive but still TimeMachine gets stuck at 58gb.

Any thoughts?

chas_m · Mar 19th, 2009, 05:59 AM

Time Machine, like every other app in OS X, keeps a log. There's a program called TM Error Logger that can help you track down the problem. It's free!

DDKD726 · Mar 19th, 2009, 08:35 PM

Thanks chas_m but I think this program only works when you actually get an error, in my situation TimeMachine just keeps on going even though it won't back up anything past the 58gb point...

I've deleted the inprogress file but that doesn't help either.

monokitty · Mar 19th, 2009, 08:41 PM

It might be an easy problem, or a sign of a deeper problem. I had a client with that exact same issue (get to a point, then crap out). Their system had to be backed up, reformatted, reinstalled, and a manual transfer of their data back before TM would work. Obviously there was a deep problem with her machine.

Griz · Mar 20th, 2009, 08:17 AM

I get that once and a while too...

It seems to only occur if I'm working on the machine while it's backing up (not always, but never when I'm not).

I have just force quit, deleted the in progress, and rebooted. Since I only back up once a day, I'll either do a "back up now" or just faggitabatit til the next day occurs.

It hasn't done it repeatedly though, just once and a while so I've never bothered to hunt down the cause. Like I said, it's only when I'm on it while it's backing up...so simple solution:

"Doc, my arm hurts when I do this."
"Then don't do that!"

Not much of solution, but at least you're not alone...right?

Love to hear the cause/solution though.

chas_m · Mar 20th, 2009, 08:22 AM

I'm with Lars. Your source drive may have a corrupted "block" that TM keeps tripping over. Could be on the target drive, but more likely on the source.

Workaround: Do a clone rather than a TM backup so you can complete the backup. Once that's done, test the clone, then boot from it, erase the original HD and clone back.

DDKD726 · Mar 21st, 2009, 08:46 AM

It had actually been a few weeks since I restarted the iMac as I usually just leave it on and let it go into sleep mode. I hadn't thought of just a fresh reboot, but turns out that's all I needed!

So glad it wasn't the drives themselves as I just replaced the iMac hard drive last month and this external drive is less then a week old.

Thanks everyone for you sugsstions!