Two Consistent Errors Without Solutions

[1763d147-8d9d-4c4a-a330-c96a707f8de7]

Hello everyone,

 

 

I am running Retrospect 8.2.0 (399) on OSX 10.6.6. I backup a Volume on a server every night where everyone saves their work. Below are the two errors that keep popping up

 

Scanning incomplete, error 24 (unknown):

For the past week I have had several execution errors every day on the same files. According to retrospect's logs, the files are located "here." When I follow the path to that location in finder, there are no files by that name. When I attempt to restore the file, unsurprisingly, it cannot be found.

 

Can't read, error -1017 (insufficient permissions):

This error only happens on occasion. I am guessing that it only happens when the file is in use but no one is in the building at midnight when the script runs. When I follow the path shown in the log, I can find these files. Their permissions are no different than the files next to them. Again, unsurprisingly, I cannot restore them.

 

I have looked through the forums and bogged down Google's servers with searches but I cannot seem to find a solution. I would appreciate any help this community may provide.

[Lennart_T]

For the scanning error: Repair the hard drive:

http://support.apple.com/kb/ht1782

[1763d147-8d9d-4c4a-a330-c96a707f8de7]

For the scanning error: Repair the hard drive:

http://support.apple.com/kb/ht1782

 

Thank you for the quick reply.

The machine with retrospect had a few inconsistencies but nothing major. The Volume on the server on the other hand, I am afraid of repairing the disk and something else going wrong. I am using a Promise VTrak with about 25T divided into three volumes: A, B, & C all controlled by OSX Server 10.6.3. On the server, I selected the VTrak drive in Disk Utility and verified it with many various errors. I do not want to repair it because I am not sure how that will affect the three sub-volumes.

[Guest Steve Maser]

If you don't want to attempt repairing the drive, then I'd recommend you copy all the data off the drive and reformat it.

 

Ignoring the problem won't make it go away, unfortunately.

[Lennart_T]

If you don't want to attempt repairing the drive, then I'd recommend you copy all the data off the drive and reformat it.

 

Ignoring the problem won't make it go away, unfortunately.

I agree: The problem will only get worse, with data loss just waiting to happen.

 

Copy all data off the drive and then repair it. If it can't be repaired, reformat it and put the files back.

[1763d147-8d9d-4c4a-a330-c96a707f8de7]

Here's what I've discovered while it's still fresh in my mind:

 

In the folder with the problematic files, there was a list of files that started with "..." and ended with a .zip.randomgarble which simply didn't make any sense. I found out that these were temp files created when rsync runs from point A to B and rsync runs again from B to A simultaneously. Since they are only temp files, they were deleted through Terminal on the server since they could not be edited otherwise. I am currently running the backup script to see if the error returns. Also, I did not run disk repair on any of the machines.

 

EDIT: That ugly red x turned into a lovely green check-mark. All is running well again.

Edited May 17, 2011 by Emmerich