#4
|
||||
|
||||
Sorry, I mis-read 44MB as 44GB. Definitely sounds like teh image was physically damaged -- I don't see how it could happen either.
No, I wouldn't suggest it was corrupt from the get-go, since you had already looked at it being correct, no? What I'd suggest is writing your backup directly to a drive, rather than to an image. That way, you can simply look at the files, and you won't have the (typically unnecessary) "indirection" involved with an image. Since I don't know how a 60GB file could get whacked to a 44MB file, it's hard to know whether Data Rescue can help. But you can try...
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
sparse image creep revisited | jotaro | General | 3 | 09-20-2007 08:20 PM |
Ever-Growing Sparse Image File... | Marco_Polo | General | 6 | 02-19-2007 10:21 AM |
Testing a sparse image... | macmidiguy | General | 5 | 05-14-2006 01:51 PM |
not ejecting sparse image after backup | rossb | General | 7 | 02-08-2006 05:20 PM |
Sparse image from aborted DMG backup? | Winston | General | 9 | 10-22-2005 12:28 PM |