Running Veeam agent for Windows free on an intel nuc, image level backup to external USB SSD.
Over a week ago we were getting the following in the backup failure reports;
One or more bad blocks were detected and skipped and skipped in the source disk
Error: Cannot process pending I/O request (offset: 28058845184, size: 65536): async reader terminated Corrupted block processing thread failed unexpectedly Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Cannot process pending I/O request (offset: 28058845184, size: 65536): async reader terminated Unable to retrieve next block transmission command. Number of already processed blocks: 9390]. Failed to download disk '50f5cc69-4da2-47ad-a384-fe605dfacfaf'
Ran all sorts of tools, benchmarks, SMART checks, chkdsks, etc and found no issues with C: (OS) or (eSSD). Noticed Veeam was due for an update, installed the new version, rebooted, started getting backups hanging with this in the logs;
eAP] (2f76) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
/AP] (b90b) output: --asyncNtf:--busy: Target backup repository is overloaded.
After a reboot, backup jobs now hang at 2%, roughly 14.5-14.9gb processed, and will sit there indefinitely. In the log file, once the backup gets stuck at 2%, I see this;
cAP] (5c0d) output: --asyncNtf:--vdisk_corrupted:\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
I have cleared out all the shadow copies on this device, thinking one was corrupted. Re-ran the backup, same issue, but now it's citing HarddiskVolumeShadowCopy1. If I just let the backup job sit, it keeps producing these logs;
At this point, the only thing I haven't tried is doing a clean uninstall of Veeam and starting over but based on the errors I'm seeing in the logs I suspect that won't fix the issue. Not sure what to do at this point, other than switch to another local backup solution because I can't seem to prove that there is anything wrong with the machine or either of its disks.