|
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!
|