Message-ID: <2073695241.967.1711721505969.JavaMail.Confluence$@Confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_966_624539534.1711721505967" ------=_Part_966_624539534.1711721505967 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A disk with bad sectors is permanently damaged and, if the bad s= ectors are in use by the file system, it is very likely that data in the da= maged area is unrecoverable. This can signify that your hard drive is comin= g to the end of its life. It is possible, however, to manage the situation = and create an Image for restoring or mounting and copying files and folders= . See this Wikipedia article http://en.wikipedia.or= g/wiki/Bad_sector for more information.
If a bad sector is encountered during image creation then you receive th= is error in your backup log:
Backup aborted!= Unable to read from disk - Error Code 23 - Data error (cyclic redundancy c= heck).=20
Open a command prompt with elevated privileges. See Running an elevated command =
prompt for help with this.
Run chkdsk c: /r from a command prompt, replac=
ing c: with the appropriate drive letter.
The /r switch is important and causes the entire file s=
ystem to be checked for bad sectors. This requires a reboot to complete and=
may take some time.
Immediately create an Image of your drive. This ensures all file sys= tem clusters are located on good sectors.
If running chkdsk is unsuccessful, force Macrium Reflect to continue on =
Error 23.
If the option 'Log each bad cluster detail' selected then each sectors w=
ill be reported in the Image log, e.g:
Read Error: Bad sector found in cluster 2353222
Read Error: Bad sector found in cluster 2353223
Otherwise a summary of bad clusters will be reported at the end. = p>
Bad Sectors: 112 Clusters located in bad sectors. Data may be lost