Backup Fails: Agent failed to process method {DataTransfer.SyncDisk}.

[mlavie]

(Support Ticket 03753157)

Hi,

Backups via Windows Agent from a Win10 Laptop have suddenly started failing a few days ago.

On the server, the log shows:
The device is not ready.
Asynchronous read operation failed
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: The device is not ready.
Asynchronous read operation failed
Unable to retrieve next block transmission command. Number of already processed blocks: [34838].
Failed to download disk.

On the Win10 Laptop:
9/5/2019 7:43:39 PM :: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [163164]. Failed to download disk.

I think the difference between the Number of already processed blocks differs between Win10 laptop and the Veeam server because these are different attempts - on the Win10 there is no indication of when the backup attempt started, so I can't tell which server-side log it matches.

I think I read somewhere that this could be a disk problem. But is it a Veeam server side disk problem, or a disk problem on the Win10 laptop running the Veeam Agent? How can I determine what the cause is?

TIA,
Lavie

[mlavie]

Hi,

I managed to get a Veeam Agent Log and Veeam Server Log from the exact same failure event, in case this helps - now the number of processed blocks is identical:

Win10 Veeam Agent

9/7/2019 11:50:39 AM :: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [238892]. Failed to download disk.

Veeam Server
9/7/2019 11:50:39 AM :: Error: The device is not ready.
Asynchronous read operation failed
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: The device is not ready.
Asynchronous read operation failed
Unable to retrieve next block transmission command. Number of already processed blocks: [238892].
Failed to download disk.


Also, since some other posts suggested the bad sectors on disk was the cause, I ran chkdsk on the WIn10 laptop running the Veeam Agent, which didn't find any problems:

PS C:\WINDOWS\system32> chkdsk c:
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
2061824 file records processed.
File verification completed.
25656 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
10199 reparse records processed.
2649062 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
10199 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
293620 data files processed.
CHKDSK is verifying Usn Journal...
41501752 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

498828831 KB total disk space.
458225948 KB in 1527288 files.
770808 KB in 293621 indexes.
0 KB in bad sectors.
2247831 KB in use by the system.
65536 KB occupied by the log file.
37584244 KB available on disk.

4096 bytes in each allocation unit.
124707207 total allocation units on disk.
9396061 allocation units available on disk.
PS C:\WINDOWS\system32>

TIA,
Lavie

[mlavie]

I also ran chkdsk c:\ /f /r /x. It sound some problems, but no bad sectors. What should I do now

[Dima P.]

Hello Lavie,

What is your backup repository? Any change you've scanned it for bad blocks as well? Thank you!

[mlavie]

Hi,

I eventually ended up running "chkdsk: /f /x /r" on very disk on every client and server within a 100 kilometer radius of our office, and rebooted them all

Problem solved.

Any disk which had even minor issues will be replaced ASAP.

FYI
mlavie

[Dima P.]

mlavie,

Thanks for the update and glad to hear that your backups are up and running. Cheers!

[ulterior]

hey guys,

I have the same problem when I backup disk C: (WinSer 2008 R2 OS), but job runs without any problems on other disks.

I run "chkdsk: /f /x /r" for C:, but it is not resolve my problem.

veeam error:
18.09.2019 20:52:50 ::
Error: The drive cannot find the sector requested. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: The drive cannot find the sector requested. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [92315].
Failed to download disk.

chkdsk log:

Code: Select all

Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
Cleaning up instance tags for file 0x7c1f.
  309760 file records processed.                                          
  File verification completed.
  4525 large file records processed.                                      
  0 bad file records processed.                                        
  14 EA records processed.                                              
  191 reparse records processed.                                       
CHKDSK is verifying indexes (stage 2 of 5)...
  393228 index entries processed.                                         
Index verification completed.
  0 unindexed files scanned.                                           
  0 unindexed files recovered.                                       
CHKDSK is verifying security descriptors (stage 3 of 5)...
  309760 file SDs/SIDs processed.                                         
Cleaning up 1422 unused index entries from index $SII of file 0x9.
Cleaning up 1422 unused index entries from index $SDH of file 0x9.
Cleaning up 1422 unused security descriptors.
Security descriptor verification completed.
  41735 data files processed.                                            
CHKDSK is verifying Usn Journal...
  538660000 USN bytes processed.                                             
  Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  309744 files processed.                                                 
  File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  6979861 free clusters processed.                                         
  Free space verification is complete.
Write failure with status 0xc0000015 at offset 0x222c396600 for 0x200 bytes.
The second NTFS boot sector is unwriteable.

Internal Info:
00 ba 04 00 3a 35 03 00 29 33 04 00 00 00 00 00  ....:5..)3......
79 02 00 00 bf 00 00 00 00 00 00 00 00 00 00 00  y...............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

[Dima P.]

ulterior,

Please perform a check of your target repository. Whenever you have issues with the source disk you get completely different error code and warning notification. Thanks!

[nitramd]

I realize this is a dated post but I've just had a similar experience and wanted to add what fixed my problem.

The error message I received:
Error: bad allocation Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.

I found this thread and ran chkdsk on both the affected PC and the Veeam data repository, both came back clean (no errors).

Opened a case (04643511), Veeam Support engineer suggested I try the following:
1. Open up regedit.
2. Locate the Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
3. Add the following new DWORD: SkipBadBlocks and change the value to 1.
4. Close regedit, open up the services.msc console, and then restart the Veeam Agent for Microsoft Windows service.

Implemented reg key, ran a backup --> success.

[Dima P.]

Hello nitramd,

Thank you for sharing the solution with the community. Based on the error I'd still recommend to check your disk's SMART status or perform a full scan with any third-party disk scanner (for example Victoria disk check). Cheers!

[TomWest]

Hi everyone,

i've just tried to backup our Veeam for O365 DB to an external harddrive using the Veeam Agent. At 99% i get the following error

13.04.2021 16:11:04 :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Failed to reload metadata bank. Declared and actual CRC are different for all bank snapshots. Failed to download disk.

Any idea on how to get it running is greatly appreciated.

Best,
Thomas

[HannesK]

Hello,
and welcome to the forums. That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.

Looks like a hardware issue to me.

Without case number, the topic will eventually be
deleted by moderators.

Best regards,
Hannes

[nikolaj]

Hi Thomas,

Have you considered the possibility of disk errors on that particular HDD? I'd recommend running chkdsk utility for that drive to see if it reports any problems.

nikolaj