Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Post Reply
basictheprogram
Influencer
Posts: 11
Liked: 2 times
Joined: Mar 14, 2015 7:23 pm
Full Name: Bob Tanner
Contact:

Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by basictheprogram »

Upgraded from Veeam Agent for Microsoft Windows v3 to Veeam Agent for Microsoft Windows v4.0.0.1811 and now the agent is throwing and error:

Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.

Tried chkdsk multiple times. Every run shows no problems with the disk.
Tried backups for each volume and see which fails.

WinRE_DRV backup as a success
EFI System Partition backup as a success
Windows (C:) FAILED! (error above)

Windows 10 Professional version 1903

Same problem was documented back in 2015?
veeam-agent-for-windows-f33/backup-to-u ... 27576.html

Any help?

Dima P.
Product Manager
Posts: 11540
Liked: 1001 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dima P. »

Hello Bob,

Can you please raise a support case and share the case ID as we need the debug logs to investigate this issue. Thank you!

Stellarspace
Novice
Posts: 6
Liked: never
Joined: Sep 04, 2018 4:30 am

[MEGRED] #04116293 - Error: The device is not ready.

Post by Stellarspace »

I scanned every drive for bad blocks and none are reported. Veeam Agent only backs up successfully when I don't select the C drive. I reinstalled Windows too and it did nothing.
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: [0]. Failed to download disk.

Dima P.
Product Manager
Posts: 11540
Liked: 1001 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dima P. »

Hello Stellarspace,

Please keep working with our support team and let us know how the investigation goes. Cheers!

d.thompson
Novice
Posts: 3
Liked: 4 times
Joined: Jan 17, 2019 6:02 pm

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by d.thompson »

I'm experiencing the same issue. Open ticket Case # 04123082 with no resolution yet. CHKDSK runs clean.

Suggestion to change/add HKLM: Software > Veeam > Veeam Endpoint Backup > "EnableParallelDiskProcessing" (DWORD) to "0" did not work.

Dark
Novice
Posts: 3
Liked: 1 time
Joined: Apr 10, 2020 3:45 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dark »

Also running into this issue on one machine with 4.0.0.1811, other machines are fine

Support ticket 04114988

Jogile
Lurker
Posts: 1
Liked: 1 time
Joined: Apr 20, 2020 8:14 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Jogile » 1 person likes this post

Hello,

I had the same problem on my PC, since 1 month. After some days of searching, I found, that is not a problem of the agent version v4.0.0.1811. The problem comes with one of the Microsoft updates between February and March 2020. The next step is to find out, which one. I also send my log files to veeam, but without any response.

Maybe, there is a solution for this problem right now. Please give me a hint, if that is the case.

d.thompson
Novice
Posts: 3
Liked: 4 times
Joined: Jan 17, 2019 6:02 pm

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by d.thompson » 2 people like this post

By running mountvol, I saw that one of the volumes was "NOT MOUNTABLE UNTIL A VOLUME MOUNT POINT IS CREATED". This volume was the Recovery Partition and was formatted RAW.

I had a workaround that was working but Veeam supplied me with the steps below which also work.

On the agent machines, add HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes (REG_MULTI_SZ) and add the volume as the value. e.g. HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes=\\?\Volume{b80b6e86-a7aa-4e89-8fb6-789e24055c1d}\. Restart the Veeam agent.

Dark
Novice
Posts: 3
Liked: 1 time
Joined: Apr 10, 2020 3:45 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dark » 1 person likes this post

d.thompson wrote:
May 08, 2020 7:03 pm
By running mountvol, I saw that one of the volumes was "NOT MOUNTABLE UNTIL A VOLUME MOUNT POINT IS CREATED". This volume was the Recovery Partition and was formatted RAW.

I had a workaround that was working but Veeam supplied me with the steps below which also work.

On the agent machines, add HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes (REG_MULTI_SZ) and add the volume as the value. e.g. HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes=\\?\Volume{b80b6e86-a7aa-4e89-8fb6-789e24055c1d}\. Restart the Veeam agent.
Thank you for this workaround, can confirm it works and I've just successfully backed up with Veeam for the first time in 2 months!

Is there any chance this produces a backup that is missing something when it comes to being restored in full? (i.e. is this recovery partition essential / can it be re-created?)

d.thompson
Novice
Posts: 3
Liked: 4 times
Joined: Jan 17, 2019 6:02 pm

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by d.thompson » 2 people like this post

I believe this would still be considered a complete backup. The recovery partition is not essential to system functionality as it is used only to restore the system to factory settings in the event of system issues. Testing recovery is always a good thing to do though.

Dima P.
Product Manager
Posts: 11540
Liked: 1001 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dima P. » 1 person likes this post

Hello folks,

Thanks for updating the thread and sorry for keeping silence. I'll take this issue from here and will discuss it with RnD folks to make sure that this issue is addressed in upcoming versions.
Is there any chance this produces a backup that is missing something when it comes to being restored in full? (i.e. is this recovery partition essential / can it be re-created?)
Looks like the recovery partition causes the problem, so you don't loose any data by excluding such partition.

Cheers!

Mildur
Service Provider
Posts: 208
Liked: 70 times
Joined: May 13, 2017 4:51 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Mildur »

I had the same error on two computers.
The solution was similar on both machines:
1. disable other Software/Backup Agents which are using VSS Integration.

Had to disable Windows Shadow Copys on my Files and on an other conputer, there was s backup agent installed and running every night from another Company.

After disabling both, backup of the disks are successful everytime.

Dark
Novice
Posts: 3
Liked: 1 time
Joined: Apr 10, 2020 3:45 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Dark »

I had the same error on two computers.
The solution was similar on both machines:
1. disable other Software/Backup Agents which are using VSS Integration.

Had to disable Windows Shadow Copys on my Files and on an other conputer, there was s backup agent installed and running every night from another Company.

After disabling both, backup of the disks are successful everytime.
I think there may be multiple causes, verified with ShadowCopyView that the only shadow copy at time of failure (before fix above) was Veeam

Stellarspace
Novice
Posts: 6
Liked: never
Joined: Sep 04, 2018 4:30 am

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Stellarspace »

To solve this problem, I did a clean install of Windows and installed Veeam Agent.

Mildur
Service Provider
Posts: 208
Liked: 70 times
Joined: May 13, 2017 4:51 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by Mildur »

Dark wrote:
May 22, 2020 2:41 pm
I think there may be multiple causes, verified with ShadowCopyView that the only shadow copy at time of failure (before fix above) was Veeam
Ok :)

str
Lurker
Posts: 1
Liked: 1 time
Joined: May 26, 2020 1:17 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by str » 1 person likes this post

d.thompson wrote:
May 08, 2020 7:03 pm
By running mountvol, I saw that one of the volumes was "NOT MOUNTABLE UNTIL A VOLUME MOUNT POINT IS CREATED". This volume was the Recovery Partition and was formatted RAW.

I had a workaround that was working but Veeam supplied me with the steps below which also work.

On the agent machines, add HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes (REG_MULTI_SZ) and add the volume as the value. e.g. HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\ManagedExcludeVolumes=\\?\Volume{b80b6e86-a7aa-4e89-8fb6-789e24055c1d}\. Restart the Veeam agent.
With mountvol in PowerShell I had 3 volumes that showed comments like

Code: Select all

        *** NOT MOUNTABLE UNTIL A VOLUME MOUNT POINT IS CREATED ***
        *** NO MOUNT POINTS ***
They were some hidden recovery partitions of the main physical drive where Windows 10 was. Not Mountable were RAW partitions whereas No Mount Points was a FAT32 100 MB partition.

I received the error after a Windows Update.

glx
Lurker
Posts: 1
Liked: never
Joined: Jun 08, 2020 8:02 am
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by glx »

My solution was to "Edit Backup Job", in "Volumes" activate "Show system and hidden volumes", disable "Operating system" so only the volumes with names like "C:" are selected. Now start the backup job - it should work, since no "\\?\Volume{*} are being selected anymore (Recovery or System-reserved partitions).
After that re-select "Operating systems" and re-running the backup job should work again :D

cxwsrei
Enthusiast
Posts: 45
Liked: 2 times
Joined: May 22, 2017 1:18 pm
Contact:

Re: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk

Post by cxwsrei »

@glx : I experience the same problem (on a server 2016) . It´s veeam win agent 4.0.0.1811.
The workaround you mentioned works - but will not be useful for a full recovery in case of a hardware failure for exmaple I think !?
Anyway: how many time has you executed the backup since June 8 (date of your last post) ?
No more problems since that time ? Did you execute it all the time including the OS/recovery partitions since June 8 ?

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests