2020 True Image "File system error is found"
I've run CHKDSK /f /r on all drives. The Windows drive C: had fixes while the storage drive D: and the backup drive X: were okay. I get the same error whether I run a system backup (C: & D:) or a disk backup (D:). This is a client machine running Win7.
I'm happy to share a system report by private message.
Thanks!


- Log in to post comments

Steve,
I'm unable to upload a file here for some reason. I'll send a link.
Thanks for your help.
Nick
- Log in to post comments

Nick, thanks for the disks.txt file - there is no evidence shown there of any file system errors on any of the partitions of the drives that were connected when the information was captured in the system report. The drives shows were your C:, D: and X: external USB backup drive.
Can you attach a copy of the log where this error was reported, plus also confirm the type of backup being performed here, i.e. Disks & Partitions or Files & Folders.
There is a new log viewer tool that has now been made available by Acronis via the Community Tools KB page. See the link in my signature for the MVP Assistant tool.
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backup using same) then look in the Demon logs.
Ideally, please zip the original log file to preserve its file name when attaching to the forum as otherwise all files get renamed by the forum software!
- Log in to post comments

Nick Kraft wrote:Steve,
I'm unable to upload a file here for some reason. I'll send a link.
Thanks for your help.
Nick
Nick, there looks to be problems in the forums at present that are stopping any file attachments from being uploaded! One of the other MVP's has also reported this too.
- Log in to post comments

Steve,
I'm sending you a link to 3 Disks & Partitions logs from 3 days that have the word, "error," in them. The error appears to be the same in each. There are many logs per backup. Let me know if you need them all.
Thanks, Nick
- Log in to post comments

Nick, thanks for the backup worker logs, these are showing a VSS Snapshot error rather than a file system one.
28/10/2020 10:45:33:862 PM -07:00 type=commonerror; value=A backup error.
$funcAda_backup::Commit
$lineNa??(????Read error.
$funcA`anonymous-namespace'::PartitionBackuper::ReadDrive
$lineNe????v???Failed to read the snapshot. See VSS logs for details.
$funcAwin_snapshot_volume::IoOp
$lineNU?R?*{??CRC error.
28/10/2020 10:45:33:862 PM -07:00 type=retcode; value=4095; id=1;
Please download and run the Acronis VSS Doctor standalone tool and let it fix any issues that it identifies for your PC. (link below)
- Log in to post comments

Hi Steve,
I fixed the VSS Shadow Storage error.
Event Log showed, "The device, \Device\Harddisk1\DR1, has a bad block."
I ran CHKDSK /f /r on that disk again (16kb bad blocks found) and installed SeaTools and ran the following.
--------------- SeaTools for Windows v1.4.0.7 ---------------
10/29/2020 9:53:33 PM
Model Number: ST1000DM003-1ER1
Serial Number: Z4Y10KFN
Firmware Revision: CC45
Fix All Long - Started 10/29/2020 9:53:33 PM
Fix All Long - Pass 10/29/2020 11:58:16 PM
SMART - Started 10/30/2020 9:33:02 AM
SMART - Pass 10/30/2020 9:33:08 AM
Short Drive Self Test - Passed
Long Generic Test - Passed
Event Log showed:
I have a backup planned for tonight. Is it possible to use an Acronis or other kind of snapshot and get around this issue?
Thanks, Nick
- Log in to post comments

Nick, hopefully the CHKDSK you did has fixed the bad block on the drive to allow your planned backup to run successfully tonight.
For snapshot options, please see the ATI 2020 User Guide: Snapshot for backup information on the options offered in the Options > Advanced > Performance settings for your task. (Scroll down the above page).
- Log in to post comments

Hi Steve,
I received the original error again - "File system error is found." I then tried a files & folders backup of D:, which was successful. If the client agrees, that will be our work around.
Thanks, Nick
- Log in to post comments