PDA

View Full Version : SD Stalls During Smart Update


Drdul
07-10-2007, 06:03 PM
I've created an image of my boot drive on another hard drive within the same computer. I have set Super Duper! to run daily to "smart update" the image. Yesterday it ran fine, but today it stalled after it had evaluated 55,000 of 320,000 files. The task started at 12:30 as scheduled, but when I checked at 2:00 it was sitting there stalled (but keeping track of the elapsed time!). Any idea what happened here?

Unfortunately, SD quit (as I has set it to do at the end of the task) before I could copy the log file. When I restarted SD, today's log file was gone.

Thanks!

dnanian
07-10-2007, 06:12 PM
It's likely it was copying a large file, Drdul...

Drdul
07-11-2007, 05:38 PM
Really?! It stalled for a whole 90 minutes. Just out of interest, how long would it take SD to copy a 15 GB file (which is the largest file I can find on my drive) as part of a smart update?

BTW, it's "stalled" again today, so I'm gonna leave it and see how long it takes, and whether or not it completes the smart update. In the event that it doesn't complete, what else other than a large file could cause it to stall out like this?

Thanks!

dnanian
07-11-2007, 05:45 PM
It depends on how quickly your system is running. Typically, a Power PC copies to a FireWire drive at about 6MB/s, and an Intel at about 8MB/s. But if you're running AntiVirus, etc, it could take a lot longer...

Drdul
07-11-2007, 06:21 PM
I'm running a new Mac Pro, and I'm creating an image of the boot drive to another drive within the computer, and both are 7200 rpm SATA drives. SD is still stalled (this time at 55,700 files) after almost two hours. I can hear the hard drive grinding away constantly. Any ideas what this could be?

dnanian
07-11-2007, 06:28 PM
Drop me a note to support and I'll toss you something that'll hopefully show what's being copied.

Drdul
07-14-2007, 09:12 PM
Dave showed me how to access the log for Super Duper!, and it turns out that it was stalling out on the huge file that Parallels creates, because I had Parallels running at the time that SD was scheduled to do a backup. It works fine when Parallels isn't running, so I've simply rescheduled SD for a time when I'm not likely to have Parallels active.

FWIW, Entourage can cause the same problem, so that (and a bunch of other reasons) have convinced me to stick with Apple Mail.

Cheers!