Well, I have nothing really attached, just the source drive and the target drive. This is how it used to work for a long time. I use SD since years. Never a problem really that couldn't be fixed fast. I just ran it again to backup a different partition and it worked, so it cannot be the drive or the app, only perhaps the partition (nothing bad though reported by DiskWarrior) or, what I suspect, it's a paricular file which simply refuses to be read.
David, somewhere you noted some command to get more log info about which file is accessed. You said while SD is running this log info can be obtained. Could you point me into a new direction to get me back and running? I'm now using CCC (slow as a snail) - can't wait to return to SD! |
If you're crashing with the dump provided before, the problem is very likely a bug in Tiger with the API that returns the volume list - it used to generate exceptions just like the one you sent when used with "null" named FAT32 volumes.
You can look in the console, of course, but if SD! is crashing there's not going to be any SD log to look at. |
Should I give up? I have no Microsoft formatted drive attached. I powered all off and back on. I even ran Surface Scan on source drive and wiped target partition, writing zeros. It's again stuck at two thirds of the way. All used to work for months before. This is crazy.
|
Stuck or crashing? They're totally different things.
|
SDCopy had crashed (like before). Next I will try to reinstall SuperDuper!
Code:
Host Name: factory |
OK. This is something specific to your system. Let's take it to email where I can ask for stuff that's inappropriate to post here to the forums.
|
All times are GMT -4. The time now is 05:35 PM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.