#5
|
|||
|
|||
Sorry, not being clear here. If you connect an APFS disk to an OS that does not know how to communicate with APFS, SuperDuper will STILL try to copy, and takes time grinding away seeming to do it. But what you end up with, after a long wait, is a disk that won't boot, and probably doesn't even have a copy on it. My point is that SuperDuper doesn't seem to recognize that it's trying to copy to a disk that the OS formally can't communicate with, and you don't find out until the disk doesn't work. Are you saying that SuperDuper has no way of polling the disk to see if it is really writable?
|
Currently Active Users Viewing This Thread: 4 (0 members and 4 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Multiple errors of kind: "Caught I/O exception(5): Input/output error" | amagjo | General | 7 | 04-14-2009 10:01 PM |
Hard drive size doubled after backup.... | sanketr | General | 7 | 08-02-2008 12:16 PM |
Undersized disk image and a Boot Camp-related backup question | garybollocks | General | 3 | 10-23-2006 01:07 PM |
"Pull" a backup from a remotely mounted disk? | DrDan in MA | General | 6 | 02-08-2006 11:00 AM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |