Error: The device is not ready. Failed to read data

[carlosbehlau]

Hello Veeam Gurus,

I am trying to perform backup on lenovo T540p laptop to USB drive.
The notebook is running default Windows 8.1 64bit (German).

When I try to perform backup I am getting to following error:
20.04.2015 16:21:48 :: Error: The device is not ready. Failed to read data from the file [\\?\Volume{0bd84d4e-3ef5-4f74-8e96-4c23c1131795}]. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Failed to read data from the file [\\?\Volume{0bd84d4e-3ef5-4f74-8e96-4c23c1131795}]. Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Failed to download disk.

The USB Disk is working. As the disk is from SEGATE, I am able to verify with Acronis.

How can I fix this error?

Thanks for your help.

Best regards


Carlos Behlau

[jweave]

Do you happen to have another USB drive to try? Or try another USB port on your laptop?

[Dima P.]

Hello Carlos,
Please open a support case thru the Veeam Endpoint Backup Control Panel > Support and post here the case ID, so we could troubleshoot the logs.

If possible check another USB device, or format the existing one in NTFS and test it again.

[vadimnad]

I had the same issue, using Lenovo T430s laptop + Win8.1x64.
From disk partition layout I found that there is a two additional partitions are present:
EFI System Partition & Recovery Partition.
If I removing a Recovery Partition from a selection backup job is working.

[Dima P.]

Vadim,
Just to clarify, the error you received in the backup log identical to the topic starter?

[harrym]

To whom it may concern:

I apologize If this has been covered already. If not, below is the issue I am encountering:

Windows 8.1 Enterprise 64bit Volume level backup to an external hard drive Z:

When executed the backup fails with the following information:

8/26/2015 6:09:19 PM :: Preparing for backup
8/26/2015 6:09:58 PM :: Creating VSS snapshot
8/26/2015 6:10:20 PM :: Calculating digests
8/26/2015 6:11:15 PM :: Recovery partition (disk 0) (2.0 GB) 1.0 MB read at 1 MB/s
8/26/2015 6:11:16 PM :: Finalizing
8/26/2015 6:11:33 PM :: Error: The device is not ready. Failed to read data from the file [\\?\Volume{8233ea06-498d-11e3-8256-f4b7e28a83fe}]. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Failed to read data from the file [\\?\Volume{8233ea06-498d-11e3-8256-f4b7e28a83fe}]. Unable to retrieve next block transmission command. Number of already processed blocks: [1]. Failed to download disk.
:: Processing finished with errors at 8/26/2015 6:11:35 PM

Uninstalled Veeam and reinstalled it. No effect.
Removed all backups from target hard drive and re-formatted. No effect.
Reverted to two previous versions of Endpoint backup. No effect.

Please let me know if there is anything else to try.

[PTide]

Hi,

Here is a discussion related to the same problem, have you checked it already? If nothing helped then please open a case with support: on the VEB machine, open the Control Panel from right clicking the Tray icon, and go to the Support tab. You can submit the ticket and info from there!

Thank you.

[jamie.g]

Case # 01094871
Windows 2012 Server Std R2
Veeam B&R 8 Update 3
Endpoint 1.1.2.119

29/10/2015 11:38:16 a.m. :: Preparing for backup
29/10/2015 11:38:48 a.m. :: Required backup infrastructure resources have been assigned
29/10/2015 11:38:55 a.m. :: Creating VSS snapshot
29/10/2015 11:39:12 a.m. :: Calculating digests
29/10/2015 11:39:28 a.m. :: Saving Recovery partition (disk 0)
29/10/2015 11:39:31 a.m. :: Finalizing
29/10/2015 11:39:51 a.m. :: Error: The device is not ready. Failed to read data from the file [\\?\Volume{9a7704b9-4356-41d2-b5a3-74c9646694df}]. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Failed to read data from the file [\\?\Volume{9a7704b9-4356-41d2-b5a3-74c9646694df}]. Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Failed to download disk.
:: Processing finished with errors at 29/10/2015 11:39:59 a.m.

Was there any confirmed fix for this?
I have the exact same error when trying to select B&R Repository (HP Storeonce) or local disk repository.
The odd detail is that I have two identical physical servers and one receives this error and the other works fine.

[chh]

Hello all,

I have the same problem backing up to B&R repository.
As asked above I opened a support case with the ID 01101764

[Mike Resseler]

Can you all check the size available on your recovery / EFI partition? It might not have enough space available (due to previous backup systems or other reason) to be able to take the snapshot. You should have 42 MB available

Cheers

Mike

[chh]

Not really sure how to check those. Can't mount the EFI partition the recovery partitions (interestingl there are 2) are RAW and can't be mounted either.
But I can tell you that there were no changes to the system since backup worked for the last time

Thanks

Chris

[Dima P.]

Hi Chris,

Could it be related to the antivirus? Try to disable it for testing purposes and run the backup once again.

[chh]

Hi Dima,

I deactivated AV and still get the same error.

[Dima P.]

Thanks for the update! I do remember we have a documented issue with throttling rules for file level backups in VEB - please double check that VBR's Use multiple upload streams per job Global Network Traffic Rule is not set to 1.

[chh]

Hi Dima,

the streams are set to 5. And I actually have 4 other users happily backing up their laptops to the same VBR server, so this probably is not the issue.

[Dima P.]

Understood. I got the last idea before passing the investigation to support team – try to run a check disk utility in order to make sure the source volume does not contain any bad blocks.

[chh]

So, checking that I found a way to mount the recovery partition and found out that it only had 19MB free. seems some update replaced the winrm.wim by a larger version.
I emptied the partition and now the backup is working again.
Just hope my system will boot cleanly.

[Dima P.]

Christian,

Thanks. Unfortunately, I am out of ideas, so let’s await for support’s team investigation results. Please do not forget to update the thread.

[chh]

Too happy too soon.
Today I get the device not ready error again today. The volume in question has over 200MB free.

[Dima P.]

Hello Christian,

I am sorry it seems I’ve missed your response. Did you fix this issue?

[Sistemi.informativi]

Hello,

I tried to backup the C:\ volume (Recovery partition + EFI + System) of our B&R 8 physical server but keep failing, these are the errors:
03/12/2015 14:47:39 :: Saving Recovery partition (disk 28)
03/12/2015 14:48:02 :: Error: The device is not ready. Failed to read data from the file [\\?\Volume{548b36b0-aaaf-4edd-bd26-f7a60e3753c6}]. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Failed to read data from the file [\\?\Volume{548b36b0-aaaf-4edd-bd26-f7a60e3753c6}]. Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Failed to download disk.

The backup is successful if i exclude the recovery partition from it.

1)is possible to recover the server without a backup containing the recovery partition?
2)How can I fix the problem to have a full volume backup?

Thank you

[Vitaliy S.]

Can you please check that there is enough space in the recovery partition?

[Sistemi.informativi]

From Windows2012r2 Disk Management: Recovery Partition is 350MB Capacity / 350MB free

[Vitaliy S.]

Hmm...so there is no data at all in the recovery partition? Can you boot from this partition?

[Sistemi.informativi]

Yes i can boot into Recovery Partition ( http://s17.postimg.org/me1q30skv/Recovery.jpg ).

[Dima P.]

1)is possible to recover the server without a backup containing the recovery partition?

Yes through bare metal recovery (using Veeam Recovery Media)

2)How can I fix the problem to have a full volume backup?

Do you have any idea how it was created (vendors partition or might be during the OS upgrade)? Can you see this partition as a volume in windows explorer? Next stop would be to run a disk part:

Code: Select all

//open cmd as admin

diskpart
list disk
select disk ###
 
// replace ### with the number  of the disk you got on the previous step – most probably 0

list partition 
select partition ###

// replace ### with the number of the recovery partition you got on the previous step – most probably 1

detail partition

//copy and paste info to this thread

[Sistemi.informativi]

Ws2012r2 was installed using HP Intelligent Provisioning. From Disk Management is not possible to assign a letter and explore the Recovery partition.

DISKPART> detail partition

Partition 1
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 RAW Partition 350 MB Healthy Hidden

[Dima P.]

Thanks - it looks like a regular hidden recovery partition which should be backed up as usual. Please open a support case thru Veeam Endpoint Backup > Control Panel > Technical Support an let me know the case ID. We need to check the application logs.

[jamie.g]

Hi All,

I finally got around this issue by recreating the recovery partition from RAW format to NTFS. I have 2 identical HP DL360 G9 servers, with SSD RAID disks.
For some reason one of the servers created a RAW hidden recovery partition where-as the other created an NTFS partition. The RAW one fails as Endpoint cannot read it.
Steps taken:

1. Take Veeam Endpoint backup of Windows C: partition
2. Win2012 R2 server - Install FREE Active@ Partition Manager and FREE HDD RAW Copy Tool
3. Take a backup of the RAW recovery partition with HDD RAW Copy Tool and save the data to accessible location
4. Use Active Partition Manager and/or Windows Disk Management to delete and re-create the hidden recovery partition in an NTFS format
5. Copy the backed up data into the new recovery partition, edit partition details and NTFS access permissions
6. Test booting into recovery mode for success - confirmed. Test Endpoint 'Entire Machine' backup for success - confirmed.

Hope this helps - cheers,
Jamie G

[Dima P.]

Jamie,

Thanks for sharing the solution with the community - appreciated!