Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Error EC8F17B7: Cannot create recovery points

Created: 20 Sep 2013 | 3 comments

I'm getting the following error when trying to image the C: drive using SSR 2013:

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of OS (C:\).
 Error E7C3000F: Device \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6 cannot read 8200 sectors starting at LBA 2233696.
  Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'The request could not be performed because of an I/O device error.' (UMI:V-281-3215-6071)

I also tried booting from the SRD and creating an off-line image but got the same error, although a different LBA was referenced.

This would indicate that the drive has bad sectors. Using Acronis Drive Monitor to access the drives S.M.A.R.T. data, that was confirmed. Here's a screenshot showing the SMART attributes:

acronisdrivemonitor.JPG

The Reallocated Sectors Count has a status of Failed. However, that means that those sectors have already been reallocated which in turn means any read operations on those sectors should be successfull since they have been remapped to spare sectors. So I'm wondering if anyone has a technical explanation of why SSR would fail. BTW, I also ran SSR with the Ignore Bad Sectors option enabled and was able to complete the backup. In addition, I did a disk image backup using Windows Backup (Win 7) and was able to create a disk image that way with no errors. Any idea why Windows Backup would succeed but SSR would fail?



Operating Systems:

Comments 3 CommentsJump to latest comment

Markus Koestler's picture

I'm a bit confused: Were you able to run a succsessfull backup with SSR using the ignore back sector option or not?

*** Please mark thread as solved if you consider this to have answered your question(s) ***

cmcfarling's picture

Yes, I was able to run a succsessfull backup with SSR using the ignore back sector option.

When a drive develops a bad sector, that sector is remapped to a spare sector. So once a sector is remapped it should no longer be seen as bad since read operations to the sector are deferred to the good spare sector. Does SSR honor this remapping sheme. In other words when SSR encounters a sector that has been remapped, does it read from the remapped good sector like the the OS would or does it treat that as an error condition?

That seems to be one possible explanation as to why SSR would fail while a Windows Backup disk image succeeds. Am I wrong?

Markus Koestler's picture

To be honest - I dont know! But maybe support can answer this question ?!

*** Please mark thread as solved if you consider this to have answered your question(s) ***