CRC Error

[Dima P.]

Martin,

Bad block issue refers to the problem with your hard drive. If you restored to the same drive – it is expected. Kindly, check your hard disk with check disk (full scan), at some point third party tools, mentioned in this thread, are better in terms of bad block detection.

[majones]

Hi Dima. I've done some experimenting and I think there is a problem with "bad blocks skipped" messaging. In my case, it correctly appeared for my original disk and I managed to make a complete backup using "SkipBadBlocks (DWORD) = 1" in the registry. I then restored this backup to a new disk that had no bad blocks, and confirmed that backups from the new disk ran fine with "SkipBadBlocks (DWORD) = 0" (as I would expect). But if I left "SkipBadBlocks (DWORD) = 1" then I got the "bad blocks skipped" message, which must be a carry-over from the first disk affected by bad blocks but isn't appropriate for the new disk. In fact, I wasted quite a bit of time testing the new disk for bad blocks because of this message. I appreciate that you would want to flag in some way a restoration from a backup with skipped blocks, but not with a message that indicates that the new disk onto which the backup was restored itself had bad blocks. Sorry if this is posted in the wrong thread, but I haven't seen discussion of the SkipBadBlocks functionality anywhere else.

[AlexLeadingEdge]

Hi guys,

We have a client with Veeam B&R 8.0 running because they have a Server 2003 machine running specialised software (in a DMZ for everything except a connection to the backup server). On another server we have Veeam B&R is backing up a Veeam EP 1.5 on a Windows Server 2012 R2 machine, which acts as a replicated file server. Each time the backup kicks off we see this error message:

26/07/2017 3:16:19 a.m. :: Error: Data error (cyclic redundancy check). Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4]. The block at offset 65164804096 (length 1048576) is corrupt. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Data error (cyclic redundancy check).

I tried to submit a case but it just says "please upgrade to the latest version before submitting a case". My understanding is that I can't use Veeam Agent 2.0 with Veeam B&R 8.0. Can someone correct me if I'm mistaken?

They have a valid support licence for another 690 days, and plan to upgrade to Veeam B&R 9.5 once the Server 2003 machine has been deprecated.

Also, can someone also recommend what I should do to fix this error? I'm going to run a CHKDSK on the C Drive after hours but if anyone has another idea on how to fix this specific error I'd love to hear it.

[Dima P.]

Alex,

Take a look at this post. With the described regkey you get the ability to skip bad block on your hard drive in v1.5 Starting from 2.0 this functionality is enabled by default.

I tried to submit a case but it just says "please upgrade to the latest version before submitting a case".

Should be fixed. The case logic was accidentally disabled for 1.5 (we usually do that 2 months after release published in auto updates)

My understanding is that I can't use Veeam Agent 2.0 with Veeam B&R 8.0. Can someone correct me if I'm mistaken?

Correct. 2.0 does not work with Veeam B&R 8.0

[AlexLeadingEdge]

Hi Dima,

Thank you for the prompt reply. CHKDSK last night found 9 bad blocks. I have added the Registry change and restarted the backup. Will let you know how things go in two hours

[Dima P.]

Ouch, time to change the hard drive.

P.S. Keep in mind that this errors might be software related. In such case – you can back the drive up and then reformat it.

[AlexLeadingEdge]

Two good backups since the registry change, but Veeam 1.5 is still finding bad blocks, assumed that the drive is on its way out. We have scheduled a replacement of the C Drive and a clone of the OS partition, too many specialised programs to do a clean install unfortunately.

[techgirl]

UPDATE: We followed ACER's built-in "reset" process per their instructions, and it worked to repair whatever error it was!
I had finally taken time to get all my necessary programs running on my old computer, and moved (restored) all my content using the "entire computer" backup forced with the registry key tweak. It's been a few weeks and I have not come across any issues in my files yet. I am going to keep using my Win 7 again, and my son will take over this one.

UPDATE: Thank you Dima, yes, neither chkdisk F nor R report any issue - no errors. DISM found no issue. sfc /scnannow - nothing. Acer's diagnostics found no error. I have since tried Seagate Seatools on it, which did find an error but could not repair it. Then I have noticed in Windows Event Viewer ->Windows Logs->System: "The device, \Device\Harddisk0\DR0, has a bad block." This error was there starting exactly when Veeam started failing. EVERY windows tool or diagnostic shows the drives "healthy" and no errors except 'event viewer'! I am thankful that Veeam brought error this to my attention!

Asus wants to do a full wipe and restore, so I have done file level backup of my content as a safeguard, I am now off to tweak that registry key to force an "entire computer" backup to complete.

[vnavna]

Veeam agent for Windows version 3 has been showing CRC errors on incremental backups that are not consistent. A full backup always is clean with no errors then a few incremental backups complete as well without any issues. Then a CRC issue will come up then a couple of incremental backup will then succeed. This is occurring on a few Windows 10 systems that have been checked with the the chkdsk utility as well with no repair results on each of the systems. Each of the three Windows 10 PCs are all installed with SSD hard drives as well.
This seems to be more common since the upgrade to version 3.0.1.1039.

[Vitaliy S.]

Please review some troubleshooting tips posted in this topic by other users who had the same issue in the past. On a side note, do you see any errors in the Windows Event log of these computers regarding CRC errors?