 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
|||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
03-23-2011, 09:44 AM
|
||||
|
||||
|
I don't think that has anything to do with it. If a drive fails while we're copying to it, some system calls will convert its mount point to a folder. The drive *did* mount, otherwise SuperDuper! wouldn't find it at all when it tried to run the schedule and wouldn't even start.
What really happened is that, during the copy, the drive ejected itself. Why that happened is hard to say, but it could be a flaky drive, bad cables, compatibility issues with OSX, etc. Recreating the schedule would have no effect on this at all (if you *didn't* recreate the schedule it would work if the drive was reliable, etc).
__________________
--Dave Nanian 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How to upgrade to larger disks in RAID 1 system? | peterm1 | General | 1 | 08-28-2008 11:02 PM |
| Applying Software Updates to bootable external firewire | WalterW | General | 1 | 06-28-2008 09:37 PM |
| Recent Leopard Updates seem to kill automount | Van Helsing | General | 10 | 02-17-2008 08:28 PM |
| Software updates | cowtrail | General | 1 | 07-12-2007 01:10 AM |
| System crash on first backup attempt | cabo | General | 10 | 08-14-2005 05:27 AM |
Threaded Mode