Showing results for 
Search instead for 
Did you mean: 

BE 2010 R3 giving possibly bogus errors for RD1000 in SBS 2003

We have a customer running Backup Exec 2010 R3 Version 13 Rev. 5204 (32 bit) with Service Pack 2 and Hotfix 180429 installed on SBS 2003 with an RD1000. The RD1000 shows up as Disk 0 in Drive Management.

My backups are succeeding, and I have done chkdsk's and run the RD1000 utilities on both RD1000 cartridges, all of which passed. I am getting many errors in BE and the Windows Event Log, saying "The device, \Device\Harddisk0, has a bad block." The errors seem to happen hourly, most times at HH:45.

"This error signifies bad blocks. This could be the result of a outdated tape device driver, faulty tapes, or dirty read/write heads on the tape drive. Update to the latest Backup Exec tape device drivers, and run a cleaning job. If possible, replace the tapes with new tapes. If the issue continues, please contact the hardware manufacturer."

I found this document "" which seemed close to my problem. When I decode the bytes and refer to the chart, I get "End Of Medium (EOM) encountered" which seems unlikely for a Random Access device, unless it's trying to tell me that I'm out of room, which I would think would be handled differently.

Since the backups are succeeding, I'm mostly trying to figure out if these errors are ignorable, or better yet, fixable. Does this sound like something any of you have seen before?

3 Replies

Are you getting Event viewer

Are you getting Event viewer errors related to source - VolSnap

Refer to the link below and check if this update has been applied

Also see if this helps -


The only VolSnap entries I

The only VolSnap entries I have are Informational: "The oldest shadow copy of volume D: was deleted to keep disk space usage for shadow copies of volume D: below the user defined limit." I will check for that specific update from the first link, but I am up to date on all Windows Updates. And the second link basically says I need to run chkdsk and the manufacturers diagnostic utility, which I have already done for both cartridges.

So, several months later, and

So, several months later, and it turns out to have been a hardware issue with the RD1000. Not entirely sure what, exactly, but swapping the unit fixed the errors.