![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
#7
|
||||
|
||||
Yeah. So, this did just correspond to a drive failure. There's nothing that we can do that would "cause" a drive to fail (we're simply reading files from it), but since a full copy obviously involves copying nearly every file from the drive, if it's already failing, or about to fail, well, there's no better time.
![]()
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 2 (0 members and 2 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Failed to enable ownership on SuperDuper BackUp | Anne West | General | 3 | 06-15-2023 01:50 PM |
Server drive won't mount after backup | rhennosy | General | 1 | 11-09-2007 04:49 PM |
Scheduled backup crashes, but only on one Mac | jonlevine | General | 1 | 02-21-2007 11:08 AM |
New MacBook C2D w/ OSX v10.4.8 crashes SD. | sfm | General | 3 | 12-11-2006 10:07 AM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 11:42 AM |