Yes, that's correct as noted in my 1st post.  Error code 23 can indicate HD issues although several utilities I've run find no issues.  121 seems to be a timeout issue.  Odd that verification failures are only happening with F&F backups.  Images written to the same storage device verify successfully.

The only difference between a disk image and a F&F backup is, as far as I know, that the first backs up used sectors and the 2nd backs up actual files.  So, it would seem the low level access has no issues, but the high level file access does.  But, that wouldn't explain a Verification error.  That would seem to be a target device issue.


I also find it a bit odd the error code changed.


A few things to check on:

1.) Did you try a manual Verify of this failed backup?  Does it fail manual Verifies as well?
2.) Did you try performing a manual Verify from the Rescue Media and see if it fails there, too?

Agreed on all counts!  I'll post back to your questions shortly.

+x

 

capair45 - 18 September 2023 12:28 PM

MR Support staff is researching this.  In the meantime, can anyone help me understand the significance of, "Error reading 262153 bytes from file"?  This is shown in all 3 of the failures I've seen so far.

Whenever I see an unusual decimal number like that I convert it to hexadecimal: 0x40009. Looks to me like the misinterpretation of some flag bytes as a length.  Feeble guess, and absolutely no help in dealing with the problem. 

My guess is manual Verifies in Windows would fail as well.  But, I would be interested to see how the manual Verify behaves in Rescue Media with all the normal Windows processes, etc. removed from the equation.

+x

 

dbminter - 18 September 2023 3:23 PM

The only difference between a disk image and a F&F backup is, as far as I know, that the first backs up used sectors and the 2nd backs up actual files.  So, it would seem the low level access has no issues, but the high level file access does.  But, that wouldn't explain a Verification error.  That would seem to be a target device issue.


I also find it a bit odd the error code changed.


A few things to check on:

1.) Did you try a manual Verify of this failed backup?  Does it fail manual Verifies as well?
2.) Did you try performing a manual Verify from the Rescue Media and see if it fails there, too?

Here's an oddity to add to the puzzle.

1 & 2.  The failed backup of the 14th (121) and the 18th (23) do not show in the Existing Backups tab nor are they on the storage device so I cannot verify them manually within Reflect or with rescue media.  The failure on 9/5 (23) has scrolled off.  I only retain these backups for 7 days.

If a backup fails verification, does Reflect discard it?  It would seem so but I've never encountered this before.

EDIT:  I ran a manual full F&F backup of the scheduled backup that failed this morning (18th).  The manual backup completed and verified successfully.  This backup shows in Existing Backups tab as well as on the storage device.

+x

 

Patrick O'Keefe - 18 September 2023 4:02 PM

+x

 

capair45 - 18 September 2023 12:28 PM

MR Support staff is researching this.  In the meantime, can anyone help me understand the significance of, "Error reading 262153 bytes from file"?  This is shown in all 3 of the failures I've seen so far.

Whenever I see an unusual decimal number like that I convert it to hexadecimal: 0x40009. Looks to me like the misinterpretation of some flag bytes as a length.  Feeble guess, and absolutely no help in dealing with the problem. 

Hopefully, the Support staff can sort it out.  I have plenty of images of this disk on several devices so no big worries.

The only time I would think Reflect would delete a backup that fails Verification is if the backup set used file splitting.  Each split part is Verified upon write completion.  So, if a Verify fails at that stage, the backup aborts.  Since it never completed a full backup, there would be no reason to retain a failed backup if the backup used file splitting.


You're not using file splitting though, right?


However, it is a good question to ask support.  I've never had a Verify fail during backup before.  I've had them fail manual Verifies after a backup completed, but never during one.  And since I always use file splitting, my backups would be deleted upon Verification failure cancelling backup.

I do not use file splitting.

I'll be away from the computer for a few hours but will check back later.