Error Code 64

[tas3086]

Every so often I see this error in my logs:

[01/11/2022 01:19:22 AM] Image file I:\2022-01-10-1120-Win10(32)-(I)-.TBI is missing data written on completion.
[01/11/2022 01:19:22 AM] Program exiting with error code 64

Can you explain what this means?

[TeraByte Support]

it means there is missing data in the file (program didn't finish normally or the file has been damaged). The last bit of data written to the file doesn't exist.

You can try /recover option but depending on what is missing, it may not get back something working.

[tas3086]

I assume that if the .tbi file was corrupted, then it was found during the validation phase, and the backup-to drive is bad. If corruption was found
during the backup phase, then the backup-from drive is bad and one should be able to determine the file(s) involved somehow?
In either case there was a corruption on the backup from or to drive. Which is it, for this error 64 !!
The error implies the TO drive, but I want to be sure.

[TeraByte Support]

You'd have to show the full .log.

[tas3086]

This is the log:

[01/11/2022 01:19:22 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\IMAGEW64.EXE /ue /b /base:1@0x2:\2022-01-10-1120-Win10(32)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(32)-(I)-
[01/11/2022 01:19:22 AM] Image file I:\2022-01-10-1120-Win10(32)-(I)-.TBI is missing data written on completion.
[01/11/2022 01:19:22 AM] Program exiting with error code 64

[TeraByte Support]

the "Full" log.

[tas3086]

thats all that was available

[Bob Coleman]

Assuming IFW is being used (I don't know if this can be specified via the GUI) there is a command line option /logl: and ini value LogLevel= to specify how much is logged. See page 145 of the manual and probably use the value 9 to get the "Full" log.

[TeraByte Support]

So it wasn't part of the same operation, it was something done prior, that file was either corrupted or the backup was canceled/exited prior to being done , (or unlikely windows didn't write the last bit of data to the drive).

[tas3086]

That's the response I like to hear, Thanks.