Jump to content
Sign in to follow this  
Don Lee

What does "verify error" mean?

Recommended Posts

I have a partial log from a scripted verify:

 

- 10/6/13 9:40:35 AM: Verifying v9_Virtue2
!Generated MD5 digest for file "/Volumes/VirtueHD/private/var/servermgrd/sessions/root@iYzfWhWOyfB9evtbRJbQhVJTgslsnV9L-admin" does not match stored MD5 digest.
Remaining: 1216 files, 2.1 GB
Completed: 475256 files, 37.8 GB
Performance: 4,117.1 MB/minute
Duration: 00:10:01 (00:00:36 idle/loading/preparing)

1 files were not verified


 

 

What does this mean?  It's clear that the MD5 digest did not match, there is some sort of corruption in the listed file.  I get that.

 

What does it mean: "Remaining: 1216 files, 2.1 GB"?

Did the last 2.1 GB get ignored/skipped?  If so, why?

 

Does this imply that the last 2.1 GB of data on this set is not accessible?

  • Like 2

Share this post


Link to post
Share on other sites

I just copied v9_virtue2 with a "copy media set" script to v9_virtue2_last, and it copied cleanly, despite a previous verify of v9_virtue2 that showed a verify error (as above).  Thinking that the copy op does not check the MD5 digest, I thought I would verify the copy.  The verify came through clean.  I am now running the verify again to see if this is some sort of media error on the disk (holding v9_virtue2).  Stand by.....

Share this post


Link to post
Share on other sites

Verify of the original results in the same error as above, yet when I copy the media set, it comes through clean, and the copy has the same number of files as the original.

 

There is at LEAST one bug in here.

Share this post


Link to post
Share on other sites

This is very strange. The system being backed up might have an evil spirit.

 

I now run a scheduled "verify" script to alert me when my disk media starts to go bad. I see the following on a particular media set, which backs up a single Windows 2008 R2 server VM machine:

 

- 10/6/13 9:40:35 AM: Verifying v9_Virtue2
!Generated MD5 digest for file "/Volumes/VirtueHD/private/var/servermgrd/sessions/root@iYzfWhWOyfB9evtbRJbQhVJTgslsnV9L-admin" does not match stored MD5 digest.
Remaining: 1216 files, 2.1 GB
Completed: 475256 files, 37.8 GB
Performance: 4,117.1 MB/minute
Duration: 00:10:01 (00:00:36 idle/loading/preparing)


 

I note that this same file failed MD5 prior to Oct 1st. The media set has since been recycled and re-filled with fresh backup data. Same error. Same 1216 file "remaining" (although the number completed is different)

 

This is mighty odd.  Restores from this media set do not seem to suffer.

 

Is the error incorrect, or the error not noticed on copy and/or restore?

 

The september verify (with the error) was run with Retro 10.2.  The most recent error is with 10.5.

 

Inquiring (and nervous) minds want to know.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×