ATIH-2014 ERROR HANDLING SETTINGS - what happens to IGNORE BAD SECTOR during backup?
I have a few bad disk sectors, like all real disks do, which were re-mapped by WIN-10 CHKDSK command, so everything works & windows does NOT generate errors.
However - for some reason, ACRONIS produces an error warning pop-up option - to (IGNORE, or IGNORE ALL) future warnings, which I accepted, and the backup completed normally and VERIFIED - seemingly just fine.
First, WHY is ATIH even trying to read a sector that Windows already moved to a spare good sector?
Second, if I change the Schedule SETTINGS (ERROR HANDLING General Tab - Error Handling) to checkmark the option for ATIH-2014 to "Ignore Bad Sectors" - THEN will ATIH drop the valid data in that sector?
It shouldn't even be reading a bad spot on disk that has moved its data to a good spot - in the first place.
It seems likely that choosing this ATIH SETTINGS option will result in a corrupted backup, even if this warning no longer pops up during a backup run.
So, what is the REAL purpose or use, of the IGNORE BAD SECTORS option?


- Log in to post comments
In reply to Joseph, if Acronis is… by truwrikodrorow…

Thanks Steve,
But on one particular Win-10 system, there are (or were) 3 bad sectors near the start of the C-drive partition, which I can easily identify using the MINITOOL program. I have run CHKDSK /R /F a few times, and Windows supposedly moved the data and remapped the bad sectors. So, ACRONIS should NOT even be looking at those 3 sectors during its backup of that main partition - and yet it does, even after the full disk cleanup. It always stops at the same sector block address, and offers to IGNORE them.
I assume, accepting this IGNORE option, results in a corrupt backup TIB file, and yet the VALIDATION is "good" after that. So, just how good or successful, would a future RECOVERY be of that C-drive partition from the backup?
Likewise, if, after a CHKDSK REPAIR, I set the option in ACRONIS backup task SETTINGS- ADVANCED - ERROR HANDLING - to "Ignore Bad Sectors" - will that backup still be bad, yet Validate as good?
ACRONIS shouldn't even be using those 3 bad sectors, which CHKDSK had already "remapped" them to good ones.
It sure seems as if ACRONIS is doing a "sector backup" and thus tramsfering all sectors in sequence, even ... when doing a normal PARTITIONS backup.
It has no business accessing "bad sectors", since they were remapped. Perhaps this is an ACRONIS 2014 bug, which still continues in later versions.
- Log in to post comments

Joseph, when you are making a backup with ATI 2014, what exactly are you including in your backup? To enable a full disk recovery, then you need to include all the hidden/system partitions on your disk drive, not just your C: Windows 10 OS partition.
CHKDSK can only work against partitions that have a drive letter allocated, so you cannot use this for the hidden/system partitions in your backup source. The bad sectors that you are seeing could be in one of those hidden/system partitions.
You could test this by making an ATI 2014 backup of only the C: partition, omitting all others and see if you still see a bad sector error.
I would recommend downloading any diagnostic tools available from your disk drive maker support site, i.e. Seagate provide their SeaTools diagnostics etc. These can then check the whole disk drive surface, all sectors on the drive etc.
Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:
- Western Digital drives: Data Lifeguard Diagnostic for Windows
- Seagate disks: SeaTools for Windows
- HGST disks: HGST Windows Drive Fitness Test (WinDFT)
- Intel SSDs: Intel Solid State Drive Toolbox
- Samsung drives: Samsung Magician
- ADATA drives: ADATA SSD ToolBox
- Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager
- Transcend SSDs: Transcend SSD Scope
- Silicon Power disks: SP ToolBox
- Toshiba disks: Toshiba PC Diagnostic Tool Utility
- Log in to post comments

Steve Smith wrote:
CHKDSK can only work against partitions that have a drive letter allocated, so you cannot use this for the hidden/system partitions in your backup source.
I realize this thread is a little old but it came up in one of my searches about and I wanted to clarify that this is a false statement. You can run CHKDSK on a drives hidden partitions.
Try this.
Open a command prompt. Execute the MOUNTVOL command which will tell you all the volumes on your system and give you the GUID of them.
\\I?\Volume{eb38d03b-29ed-11e2-be65-806e6f6e6963}\
*** NO MOUNT POINTS ***
\\?\Volume{eb38d03c-29ed-11e2-be65-806e6f6e6963}\
C:\
\\?\Volume{41ae7a1c-9849-11e2-be7a-0026b9dc157c}\
F. \
The ones without mounted drive letters will be displayed with ***No Mount Pounts***.
Then you can run CHKDSK using volume name in this fashion from a command prompt (may need to run as administrator):
chkdsk "\\?\Volume{eb38d03c-29ed-11e2-be65-806e6f6e6963}"
Ensure you leave trailing backslash ( \ ) out or command will fail.
Note: quotation marks not required but will work with them still.
- Log in to post comments

Kevin, welcome to these public User Forums and thanks for sharing your method of using CHKDSK with the volume GUID. Of course hidden / system partitions can also be allocated a temporary drive letter too which might be easier for some users.
- Log in to post comments