Error getting complete file - READ_ERROR (12)

for a few days now attempts to perform a file backup on my machine has failed with errors like

Error getting complete file "Xi5KDuRXmW4DjiNSNSXr|AppData/Roaming/Signal/attachments.noindex/04/04f62818903176363b96c4494de846f3edfe0b7b568cbd92692858689717a033" from gregor-PC. Errorcode: READ_ERROR (12)
Error getting complete file "Xi5KDuRXmW4DjiNSNSXr|AppData/Roaming/Thunderbird/Profiles/y4sj0ruc.default/global-messages-db.sqlite" from gregor-PC. Errorcode: READ_ERROR (12)
Error getting complete file "Xi5KDuRXmW4DjiNSNSXr|AppData/Roaming/Thunderbird/Profiles/y4sj0ruc.default/ImapMail/imap.googlemail.com/[Gmail].sbd/All Mail" from gregor-PC. Errorcode: READ_ERROR (12)
Backup failed

trying to open these files with another program (Notepad++) results in a “cannot open file” error message and a An error was detected on device during a paging operation. warning in the windows event viewer.
It may well be that my drive is on its way out, but I’d still like for urbackup to perform backups of all the other files. I know I could just add these files to the exclusion list, but is it possible to treat these errors as warnings instead?

What about readable files that are now potentially corrupt? Do you want to back them up and replace good backups?

Best to run crystaldisk or something similar to test the smart status of the disk.

CrystalDiskInfo says the disk is good (I’ve checked this before):

I have archives going back years, so I’m not too worried about corrupted files being backed up. I’d just rather have unreadable files skipped (and a warning generated for such an event) than a backup job not being completed at all (which results in no files being backed up at all)

I don’t think urbackup is designed to work with unreadable files. You could try moving them or running chkdsk maybe.

As a workaround I’ve added the affected files to the ignore list. I’ve already tried chkdsk etc, but that’s beyond the scope of this thread.
Urbackup may not be designed for this edge case, but also does not fail catastrophically when encountering unreadable files. I’m just not sure failing the entire backup job is better than skipping unreadable files.

Just noticed there is an option in advanced server setting for

Do not fail backups in case of hash mismatches or read errors

Maybe that will help?

Hi,

Think about it from the alternative angle, where a backup skips files and doesn’t report as failing [the dodgy files] and you wanted to go back to recover…only to find it’s borked…

This is actually similar to something I had to point out to some permanent staff when I was doing a project piece a few years ago - albeit they were cancelling the BExec job so they could get the tape taken off-site…

Guys were so worried about getting the tape out, they didn’t even consider that the backup was pretty pointless, as was unable to ensure the files could be recovered…ended up getting the manager to agree to retaining the last tape on-site for an extra day, as the tape guy arrived about 5 hours before the [long] daily job completed…

Anyway, you should be able to add the file/s that are having issues to the exclusion list (in Settings) so that the job can complete the files that aren’t FUBAR and you can have the success results…

Yeah, I’d just delete those files (after inspecting if they need to be rescued). Changes are they are actually causing issues with e.g. Thunderbird. If you restore them from backup etc. it’ll just reload the mail data from IMAP.

There is also the advanced setting on the server named Do not fail backups in case of hash mismatches or read errors

good find, I didn’t notice that option. I’m just wondering what “hash mismatch” refers to here. I’ll try enabling it and will report how it works out

thanks for the suggestion. Thunderbird has not had any (obvious) issues with the unreadable files until now. I’ll try deleting and restoring the files from backups and see what happens :slight_smile:

the drive died before I could try the Urbackup Server option and restoring unreadable files suggestions, but thanks to the ignore list workaround I have backups up until the failure.