ATI 2020 File System Error Found - Build 25700
I have two backup sets for my laptop. One is the OS and Apps partitions which backs up without issue; full and incremental. The other is the Data and Media partitions on two separate disks which fails constantly with 'File System Error is Found. Consider checking disk using Check Disk Utility.'
I have run 'chkdsk {drive letter}: /r' on both disks and no errors are detected.
The odd thing is that the initial backup of those partitions completed successfully and a .tibx file was created of the full backup. All attempts at incremental backups now produce the error.
I removed all other backups for those partitions and let ATI 2020 create a new set, which it did, but it now fails every time.
Any ideas for getting beyond this since no file system errors are detected by chkdsk?
Lynn, if ATI is reporting file system errors, then there will be errors on one or more of your disk drived but impossible to say which with just the information provided so far.
Please create an Acronis System Report and share it with us via a cloud service such as Google Drive, OneDrive, Dropbox etc. You can send me a link via a private message if you prefer not to put a link in the forum.
I assume this error is the same that I can getting (see screenshot). The error message I get is:
File system error is found. Consider checking the disk using Check Disk Utility. [Edit connection settings] [Check for a solution]
The error message would be vastly improved if it actually clarifies whether "the disk" refers to the disk being backed up or the disk that the backup is writing to. This should be a simple text change for one. Better still would be to clarify which actual disk has the problem (ID, partition, drive letter, share path etc.)
PS: I'm running latest ATI 2020 Update 4 Build 38530.
Checking my C: drive showed no errors (see capture2.png)
Chris, the log for your backup task may offer more information on which disk is reporting the error, plus if you are backing up your C: drive, then you will also be including other hidden / system partitions in that backup where those partitions do not have drive letters allocated and are not checked by CHKDSK unless you are able to give those partitions a drive letter then run CHKDSK specifically to them.
There is a new MVP Assistant log viewer tool that has now been made available by Acronis via the Community Tools page..
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 backups from earlier versions using .tib files) then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox 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 Memory and Storage Tool (GUI)
- 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
- Crucial disks: Crucial Storage Executive
Thanks Steve for your reply. Thanks too for info on the new MVP Assistant log viewer tool. I've downloaded it an it is truly an excellent tool. Log files, Guidelines, Configuration. Brilliant! This will really be useful in future..
I've identified the cause of my issue to the fact that I have a small (30GB) BitLocker partition which I hold some SQL Server databases and backups (encrypted data at rest) which is only unlocked when I click on the D: drive and enter the password. Whilst it is locked, the backup fails (even through I've added D:\ in the list of exclusions). I don't actually require this partition to back backed up.
It's a shame TI2020 can't be a bit clearer on this as I'm sure it would be hard to check partitions for being locked right from the start of the backup run and report the issue in a clearer way.
Chris, for your backup task, click on the Source panel and deselect your encrypted D: partition from the source selection. You cannot have it selected in the source then exclude it in the exclusions settings!
Steve Smith wrote:Chris, for your backup task, click on the Source panel and deselect your encrypted D: partition from the source selection.
I tried this but I can't actually "click on the Source Panel" - The left side is just the name of the computer so I guess I selected the "Backup Entire PC" option when I created the backup set and now I can't go in and individually select partitions. I think the only way to do this would be to recreate the backup set again
Steve Smith wrote:[If] You cannot have it selected in the source then exclude it in the exclusions settings!
That's what I did (added D: as an exclusion) but it still fails if the BitLocker partition is locked. I guess it's failing to access it at the partition level rather than "folder/file level" which is where Exclusions come in.
For the time being, I'm just going choose to unlock the BitLocker partition when a backup is running so it can complete without error. If that becomes too much of a hassle, I'll have to create a new backup set using the "Disks and partitions" option.
Thanks