Skip to main content

Backup fails - bad sector

Thread needs solution

I'm trying to get a good backup for the entire PC. After 9.98GB (of 657GB), I get the error:

Failed to read from sector '31,710,225' of hard disk 1. Try to repeat the operation. If the error persists, check the dish using Check Disk Utility and create a backup of the disk. Failed to read the snapshot (0x10C45A) CRC error (0x100155).

I rand a CHKDSK on my C: drive, and it found no errors.

Any Ideas?

Dave

 

 

0 Users found this helpful

David, welcome to these user forums.

If you are getting sector read errors then this indicates that your disk drive has a problem and when you run CHKDSK you should use the /R switch option to check for any bad sectors, i.e. CHKDSK C: /R - this can take a significant time to complete if this is a large drive.

David, without using /R it is only doing a standard NTFS filesystem check and not looking a potential sector issues.

C:\Windows\System32>chkdsk /?
Checks a disk and displays a status report.

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B] [/scan] [/spotfix]

  volume              Specifies the drive letter (followed by a colon),
                      mount point, or volume name.
  filename            FAT/FAT32 only: Specifies the files to check for
                      fragmentation.
  /F                  Fixes errors on the disk.
  /V                  On FAT/FAT32: Displays the full path and name of every
                      file on the disk.
                      On NTFS: Displays cleanup messages if any.
  /R                  Locates bad sectors and recovers readable information
                      (implies /F, when /scan not specified).
  /L:size             NTFS only:  Changes the log file size to the specified
                      number of kilobytes.  If size is not specified, displays
                      current size.
  /X                  Forces the volume to dismount first if necessary.
                      All opened handles to the volume would then be invalid
                      (implies /F).
  /I                  NTFS only: Performs a less vigorous check of index
                      entries.
  /C                  NTFS only: Skips checking of cycles within the folder
                      structure.
  /B                  NTFS only: Re-evaluates bad clusters on the volume
                      (implies /R)
  /scan               NTFS only: Runs a online scan on the volume
  /forceofflinefix    NTFS only: (Must be used with "/scan")
                      Bypass all online repair; all defects found
                      are queued for offline repair (i.e. "chkdsk /spotfix").
  /perf               NTFS only: (Must be used with "/scan")
                      Uses more system resources to complete a scan as fast as
                      possible. This may have a negative performance impact on
                      other tasks running on the system.
  /spotfix            NTFS only: Runs spot fixing on the volume
  /sdcleanup          NTFS only: Garbage collect unneeded security descriptor
                      data (implies /F).
  /offlinescanandfix  Runs an offline scan and fix on the volume.
  /freeorphanedchains FAT/FAT32/exFAT only: Frees any orphaned cluster chains
                      instead of recovering their contents.
  /markclean          FAT/FAT32/exFAT only: Marks the volume clean if no
                      corruption was detected, even if /F was not specified.

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.

I tried chkdsk c: /R and got:

 

The type of the file system is NTFS

Cannot lock current drive

 

David, you should have been offered an option to schedule the CHKDSK /R to the next time you restart your PC as the OS drive will always be locked by Windows and thus CHKDSK prevented from locking it.

I added /x to CHKDSK and it's been running now for about 2 hours - still at 13%.

Thanks for the help.

 

David,

See attached screnshot of the chkdsk /r command run from an admin command prompt in Windows 10.  You should answer Y to the schedule question and then select Restart from the poser menu to run the task.

Attachment Size
411491-138565.png 21.42 KB

That's what the /x option did - prompted the schedule after the next restart. I restarted and the chkdsk is running now. Been at 13% for an hour.

Let it finish running.  It has found issue and is attampting to fix it.

Waited 2 houirs, went to PC and saw it had rebooted. Signed on to Windows and there was nothing displayed regarding the chkdsk. I assumed that it had repired everything. When back into True Image and backed up gthe entire PC - Failed to read from sector '31,710,225' of hard disk 1.

To make sure the error was on my C: drive, I backed up only My Partition - Failed to read from sector '31,710,225' of hard disk 1

I am not positive if the chkdsk completed successfully or not.

Thanks,

Dave

David, the results of the CHKDSK will get written into the System Event Log if you are not watching the display to see them when it finishes checking, but if you are still seeing the same sector number in the error message then this would suggest that there is a problem with the drive / partition.

Run MSINFO32 from the Run prompt and use that to identify the make / model of the drive, then go to the makers support web site and see if they provide further diagnostic tools to use to check the drive in more detail, i.e. Seagate have SEATOOLS etc.

The chkdsk results are put into the Event Log.

  1. Open the Control Panel
  2. Open Administrative Tools
  3. Select Event Viewer.
  4. In the Event Viewer expand the Windows Logs
  5. Select the Application log.
  6. Look for an information message with source Wininit at the time of the chkdsk and the results should be there.

Do you have multiple hard drives in your PC?  What version of Windows are you using?

No wininit in the Event Log - there is a 3 hour gap starting at 094115 - I'm auuming that is when the chkdsk ran.

Attachment Size
411521-138577.jpg 315.53 KB

David, if you want to create an Acronis System Report zip file and attach it to this forum topic, we could take a look at what that shows us, this will include the event log information too.

Did you run chkdsk from an administrator command prompt?  Are you attempting to create the backup on one of your external USB drives?  If you are attempting to create and store the backup on an external USB drive you should run chkdsk /r on that drive too.  (chkdsk X: /r where X is the intended drive target).

Corruption on either the source or the target disk will cause errors like you are getting.

I did run the chkdsk from the administrator command prompt.

I am trying to attach the  Acronis System Report zip file, but it is failing, saying it is too large. It's 9.1MB

Dave

 

David, are you sure the system report zip file is only 9MB in size as the maximum upload size for attachments is shown as being 20MB in the italic print below the File attachments area?

David, this looks like there is an issue with the Acronis web servers as there should be no issue with your system report zip when it is only 9MB in size.

I would recommend raising a Support Case directly with Acronis to report this issue plus also ask them to take a look through this forum topic and help you with the bad sector issue during the backup.