Jump to content

Chunk Checksums - Frustrating!


Recommended Posts

 

I have Retrospect 6.0 on my Mac b&w G3, which is connected to a LaCie d2 160 GB external firewire drive, of which I do file backups. I also back up a client iBook G3 to the same drive, wirelessly.

 

Unfortunately, I can never get a legitimate working backup of either. I usually have numerous Execution Errors, which can be eliminated after several time-consuming tries of backup sets.

 

But worse, I get continual Chunk Checksum Errors on my Client backup, and in the past when I've tried to restore a file or folder from the backup set (even though the backup file is verified and shows not to need repair), I cannot.

 

In essence, R6.0 has been useless for me so far.

 

Any advice is appreciated.

Link to comment
Share on other sites

The external drive I have is not a tape drive but a 160 GB hard drive.

 

Also, the firewire ports have tested well with TechTool Pro and I've experienced no other Firewire problems. R6 is the only app causing trouble.

 

I hope that just getting this software to work properly for what it's intended to do does not require an additional hardware expense.

 

I also read the knowledge base article that requires a system restart after every checksum error... is that what I'll need to do every time?

 

Hopefully there's a solution for the issue since it's very frustrating buying backup software that doesn't back up...

Link to comment
Share on other sites

Quote:

R6 is the only app causing trouble

 


 

Retrospect is the only application pushing I/O through the FireWire bus hard enough to expose your hardware problems.

 

Fact: your Macintosh model has known FireWire hardware issues.

Fact: your FireWire device is exhibiting problems when used with Retrospect.

Conjecture: your Retrospect problems are caused by the deficiencies in your FireWire hardware.

 

>I hope that just getting this software to work properly for what it's intended to

>do does not require an additional hardware expense.

 

Retrospect requires hardware that works correctly; if you don't have it, you might have to pay extra to get it.

 

Dave

Link to comment
Share on other sites

Before I go out and spend money on a firewire card, that logic must be confirmed somehow. After all, just because there is a known firewire issue on my model (of which there were two revisions), doesn't necessarily mean there's a firewire issue on my particular machine. I'm not necessarily convinced that I definitely have it since I've done video editing via the same firewire drive (which pushes through loads of I/O as well) and haven't had a problem.

 

I'm going to try backing up to a set on my internal drive, where no data will be passing via Firewire, and we'll see what happens.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...