Backup Fails - File System Corrupt... but it's not.
So one week my backup just started to fail due to Acronis saying there was a file system error...
"File system error is found. Consider checking the disk using Check Disk Utility".
Things I've done so far...
- Ran chkdsk /r on both C drive (source drive), D drive (destination drive)
- Used DiskPart to assign drive letters to all hidden partitions on the C drive, then ran chkdsk /r on all of those partitions.
- Installed Acronis True Image 2021 Beta
- Removed Acronis True Image completely and reinstalled
- Deleted the backup completely from D drive and from Acronis, created a brand new one.
- Turned off all antivirus programs and any programs that were not crucial
The backup has got to 99% complete once, then gives me the error right before completing. Other time is just randomly gives the error.
After the error, it looks like it tries to restart the backup again with a loop of the same result.
I have the latest BIOS installed, all settings completely stock (no overclocking).
The main drive is a Samsung 970 Evo, I do not see any advanced drive testing options in Samsung Magician.
The computer works fine with zero issues. I'm at a loss here.
Is there any advanced logging somewhere to know which drive or partition, or to be able to pinpoint the problem?
Thanks for the help!
I'm using Acronis True Image 2020, Build 25700
I would download the drive manufacturer's utility and use that to check the drive - hopefully, it will not be limited by the partition layout.
Ian
IanL-S wrote:I would download the drive manufacturer's utility and use that to check the drive - hopefully, it will not be limited by the partition layout.
Ian
I've downloaded Samsung Magician. Under "Diagnostic Scan" it shows "The selected drive does not support this feature" for both Samsung drives I have.
Crystal Disk Info shows both drives are in good health.
Also, Acronis cloud backs up without issue.
It could be that the problem is with the destination drive, not the drive being backed-up. Consistent with being able to backup to the cloud. Is the local backup drive also a Samsung 970 Evo - I ask as you mention that you have two of them.
Do not know how I missed your mentioning that you had tried Samsung Magician. Possibly too early on a cold winter's morning. Yes, for some reason diagnostics are only supported for newest drives - it is supported on the 970 Evo Plus but not 960 Evo or the 850 Evo. Possibly an older version may have that functionality.
I note you are using ATI 2021 Beta. It is not an issue that I can recall seeing with the beta. Would you pleas go to the first post in the thread, an edit it to change the topic by adding ATI 2021 Beta so Ekaterina can move it to the Beta Forum.
Ian
Please collect an Acronis System Report zip file and share a link to this via a cloud share service such as OneDrive, Google Drive, Dropbox etc, then we can look in more detail at the various logs for the backup giving this error message.
Note: if you do not wish to share a link in these public forums, then send me a private message with the link.
KB 58820: Acronis True Image: Collecting System Report
Note 2: In the zip file for the system report, open the disks.txt file in Notepad and check if any of the partitions are showing an Error indicator.
IanL-S wrote:It could be that the problem is with the destination drive, not the drive being backed-up. Consistent with being able to backup to the cloud. Is the local backup drive also a Samsung 970 Evo - I ask as you mention that you have two of them.
Do not know how I missed your mentioning that you had tried Samsung Magician. Possibly too early on a cold winter's morning. Yes, for some reason diagnostics are only supported for newest drives - it is supported on the 970 Evo Plus but not 960 Evo or the 850 Evo. Possibly an older version may have that functionality.
I note you are using ATI 2021 Beta. It is not an issue that I can recall seeing with the beta. Would you pleas go to the first post in the thread, an edit it to change the topic by adding ATI 2021 Beta so Ekaterina can move it to the Beta Forum.
Ian
The destination drive is a Samsung 850 EVO. I briefly installed ATI 2021 to see if it would fix the issue and it did not. So I reverted back to ATI 2020.
Steve Smith wrote:Please collect an Acronis System Report zip file and share a link to this via a cloud share service such as OneDrive, Google Drive, Dropbox etc, then we can look in more detail at the various logs for the backup giving this error message.
Note: if you do not wish to share a link in these public forums, then send me a private message with the link.
KB 58820: Acronis True Image: Collecting System Report
Note 2: In the zip file for the system report, open the disks.txt file in Notepad and check if any of the partitions are showing an Error indicator.
I have PMd the dropbox link to the file. Looking at the disk report, if I'm reading it correctly, it shows an "e" on the C drive of the 970 NVMe drive.
However, the C drive passed chkdsk without issue:
Level Date and Time Source Event ID Task Category
Information 7/15/2020 4:48:49 PM Chkdsk 26226 None "Chkdsk was executed in scan mode on a volume snapshot.Checking file system on C:
Stage 1: Examining basic file system structure ...
1498880 file records processed.
File verification completed.
Phase duration (File record verification): 7.66 seconds.
9452 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 3.60 milliseconds.Stage 2: Examining file name linkage ...
1889 reparse records processed.
1646922 index entries processed.
Index verification completed.
Phase duration (Index verification): 16.80 seconds.Phase duration (Orphan reconnection): 1.28 seconds.
Phase duration (Orphan recovery to lost and found): 12.52 milliseconds.
1889 reparse records processed.
Phase duration (Reparse point and Object ID verification): 17.20 milliseconds.Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 15.88 milliseconds.
74022 data files processed.
Phase duration (Data attribute verification): 1.48 milliseconds.
CHKDSK is verifying Usn Journal...
32479536 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 98.18 milliseconds.Windows has scanned the file system and found no problems.
No further action is required.1952307564 KB total disk space.
1166324768 KB in 961861 files.
493484 KB in 74023 indexes.
1634216 KB in use by the system.
65536 KB occupied by the log file.
783855096 KB available on disk.4096 bytes in each allocation unit.
488076891 total allocation units on disk.
195963774 allocation units available on disk.
Total duration: 25.92 seconds (25924 ms).----------------------------------------------------------------------
Stage 1: Examining basic file system structure ...
Stage 2: Examining file name linkage ...
Stage 3: Examining security descriptors ...
"
It looks like last night, after Acronis retried and failed with chkdsk error multiple times, it successfully completed a backup... even though I did nothing more on the computer.
Thanks for the system report. The disks.txt report confirms that there is a file system error for partition 2-4 (C: OS partition) as shown below:
2- d(1) GPT 1.8T NVME 0-0-0 NVMe Samsung SSD 970 2B2Q MBR ------ GPTpri -----v -1 ---- 499M 499M 485M NTFS 27 Windows RE H Recovery... --c--V -2 ---- 99M 99M 69M FAT32 EF EFI ........... --c--V MSresr -----v -4 --DC 1.8T 1.8T 832G NTFS 07 NTFS, HPFS ........... --e--V -5 ---- 562M 562M 84M NTFS 27 Windows RE H ........... --c--V 1.1M unallc ------ GPTbck ------ ----------------------------------- Partition 2-4: file system FS: NTFS File System Error 0x7001c: Run list is corrupted. | line: 0x89d94b01b483dcdb | file: c:\bs_hudson\workspace\123\core\resizer\ntfs\fs_ntfs_check.cpp:507 | function: resizer::NTFSProcessor::ReadControlStructures | line: 0x89d94b01b483dcdb, c:\bs_hudson\workspace\123\core\resizer\ntfs\fs_ntfs_check.cpp:507, resizer::NTFSProcessor::ReadControlStructures | $module: system_report_vs_25700
Please see KB 14260: Operation with Acronis Product Fails with "Run list corrupted" or "MFT bitmap corrupted" which recommends running CHKDSK C: /R
Steve Smith wrote:Thanks for the system report. The disks.txt report confirms that there is a file system error for partition 2-4 (C: OS partition) as shown below:
2- d(1) GPT 1.8T NVME 0-0-0 NVMe Samsung SSD 970 2B2Q MBR ------ GPTpri -----v -1 ---- 499M 499M 485M NTFS 27 Windows RE H Recovery... --c--V -2 ---- 99M 99M 69M FAT32 EF EFI ........... --c--V MSresr -----v -4 --DC 1.8T 1.8T 832G NTFS 07 NTFS, HPFS ........... --e--V -5 ---- 562M 562M 84M NTFS 27 Windows RE H ........... --c--V 1.1M unallc ------ GPTbck ------ ----------------------------------- Partition 2-4: file system FS: NTFS File System Error 0x7001c: Run list is corrupted. | line: 0x89d94b01b483dcdb | file: c:\bs_hudson\workspace\123\core\resizer\ntfs\fs_ntfs_check.cpp:507 | function: resizer::NTFSProcessor::ReadControlStructures | line: 0x89d94b01b483dcdb, c:\bs_hudson\workspace\123\core\resizer\ntfs\fs_ntfs_check.cpp:507, resizer::NTFSProcessor::ReadControlStructures | $module: system_report_vs_25700Please see KB 14260: Operation with Acronis Product Fails with "Run list corrupted" or "MFT bitmap corrupted" which recommends running CHKDSK C: /R
I ran CHKDSK C: /R and posted results above as it shows everything was fine, but would still receive the error.
Please try running SFC /SCANNOW from an Administrator level prompt to see if that helps?
All the hits I can find for the Run list is corrupted error give the same recommendation of using CHKDSK /R (from an Administrator prompt).
Have you tried doing a Full Diagnostic Scan of the Samsung 970 Evo SSD with Magician - it should support that drive?
The only other suggestion is to open a Support Ticket direct with Acronis Support to ask them for advice on how to resolve this type of file system error from a SSD?
Steve Smith wrote:Please try running SFC /SCANNOW from an Administrator level prompt to see if that helps?
All the hits I can find for the Run list is corrupted error give the same recommendation of using CHKDSK /R (from an Administrator prompt).
Have you tried doing a Full Diagnostic Scan of the Samsung 970 Evo SSD with Magician - it should support that drive?
The only other suggestion is to open a Support Ticket direct with Acronis Support to ask them for advice on how to resolve this type of file system error from a SSD?
I got unlucky here. Looks like 970 Evo and 850 Evo are not supported in Magician for drive testing for whatever reason, but 970 Evo Plus and 860 Evo are.
Backup still fails with same error. chkdsk /r for c drive was run from admin and no errors found. Ill try opening a ticket. Thanks for all the help!
I would recommend that you open an admin command prompt and run chkdsk /f Reason is that the /r option is of no use on SSD's for one and, your error indicates a filesystem error not a disk error so think of it this way, the /r option infers /f but is primarily used to correct disk errors.
If that proves unsuccessful I would recommend again using an admin command prompt, SFC /scannow
If these both fail to fix the issue I think your only option would be to format the drive anew and then restore your most recent backup to the drive.
Enchantech wrote:I would recommend that you open an admin command prompt and run chkdsk /f Reason is that the /r option is of no use on SSD's for one and, your error indicates a filesystem error not a disk error so think of it this way, the /r option infers /f but is primarily used to correct disk errors.
If that proves unsuccessful I would recommend again using an admin command prompt, SFC /scannow
If these both fail to fix the issue I think your only option would be to format the drive anew and then restore your most recent backup to the drive.
I ran a SFC /scannow and had already ran a chkdsk /f before I did the chkdsk /r. For good measure, I ran the chkdsk /f again. It stalled at 100% during reboot forever. After resetting, it looks like it ran and worked on the next reboot.
I ended up doing a Windows Repair (in place install of Windows on the existing system). I then performed an Acronis backup and it was successful. I ran another Acronis System Report, checked the disks.txt again, and no "e" listed there, so I imagine the issue is "resolved" now.
The weird thing is every chkdsk, scan, etc showed zero errors/issues. I never installed or did anything I believe would have corrupted the NTFS file system or system files. Either way, appears to be working now. Thanks for everyone's help on this weird issue. I'll post back if I experience any issues in the next couple weeks from the automated backups. THanks.
Glad you were able to resolve the issue. I would say that the error existed in the MFT. Such errors are hard to fix using conventional tools such as SFC and chkdsk. I had not considered an in place upgrade working so glad to add that to my knowledge base. Thanks for posting.
I have the exact same HDD and having the exact same problem. However only "ignore bad sectors" works for me and I didn't try cloud backup as I need local but guess I can try.
I reinstalled Win 10, ran chkdsk /f and /r and also ran SFC /scannow, Nothing works except for me to "ignore bad sectors" which I don;t want to do since there's an error.
Anyone have any ideas?
It is time to run the drive manufacturers utility to check the drive. The can often fix issues that Windows utilities cannot. Get the best backup you can before doing so. I would do a separate Files&Folders backup of your user files; hopefully they will not have the bad sector issue - use the full path name when doing so.
As stated above in this thread there is no option to fix or scan this drive w/ Samsung Magician or I would. The only option is CHkDSK /f /r but that doesn't fix this problem or report any errors. I reinstalled win 10, ran those etc. but it won't get past 40GB.
I just got this HDD on Oct 28, 2019 can;t be going bad already.
Sorry I missed the earlier post - I remember the discussion now: another seniors moment. I managed to find a build that hopefully will work with your drive; you can download it here. It is build 5.3.1.2010 09-04-19.
Ian
Hi Ian, thanks for the build. It says drive is not supported, only options I see is System compatabilty and Benchmark which the other tool has. Think was the diagnostics which seems to be missing on here. Not sure if you can fix that?
The exact drive is Samsung 970 EVO SSD 2TB - M.2 NVMe Interface Internal Solid State Drive with V-NAND Technology (MZ-V7E2T0BW) https://www.amazon.com/gp/product/B07C8Y31G1/
I did upload the AcronisSystemReport.zip if you can help with that?
https://drive.google.com/file/d/1sZmv77qBE2SUsmHaarTojhIsWHCFVkr9/view?…
Ed, what actual drive do you have here? Your initial post said a HDD but then you mention Samsung Magician which only works for certain recent Samsung SSD drives?
See my earlier post in this topic here for reviewing the disks.txt report from an Acronis System Report zip file. This should confirm that Acronis is detecting an error condition on the drive and if you look further into the disk report as shown in my post here, then it will tell you what type of error condition is happening?
You can also post a copy of the disks.txt file to this topic using the File Upload option.
Hi Steve,
I have a Samsung SSD sorry I wasn't clear as old habbits die hard (always saying HDD). I will have a look at your instructions, I did upload the disks.txt if you want a look at it.
I see there is an error but I have tried everything, not sure what the error is or how I can fix it? I got this SSD in Oct. 28, 2019 not even a year old. Should I do a backup, ignore bad sectors (that works) and contact Samsung? It should be under Warranty.
Partition 1-3: file system
FS: NTFS
File System Error 0x70018: MFT bitmap is corrupted.
| line: 0x89d94b01b483dc9c
| file: c:\jenkins_agent\workspace\ati-main-win\598\core\resizer\ntfs\fs_ntfs_check.cpp:444
| function: resizer::NTFSProcessor::ReadControlStructures
| line: 0x89d94b01b483dc9c, c:\jenkins_agent\workspace\ati-main-win\598\core\resizer\ntfs\fs_ntfs_check.cpp:444, resizer::NTFSProcessor::ReadControlStructures
| $module: system_report_vs_30480
Ed, thanks for confirming the issue here.
CHKDSK /F should fix this type of MFT Bitmap corrupt error but wonder if starting this from within Windows might be a reason why it hasn't fixed it, i.e. if Windows Fast Start is enabled?
I would suggest booting from a Windows 10 install DVD or USB stick and going into the Recovery or Repair options to get to a Command prompt window, then doing the CHKDSK from there after you confirm that you have found the correct drive letter.
This is where I find the MVP Custom PE rescue media to be very handy, as it includes a file explorer to find the drive letters for my partitions, and also a Command prompt option to allow doing this type of operation fully outside of Windows.
You do still need to do a full Shutdown of Windows before using either of the above options and to do this, press & hold down a Shift key while clicking on Shutdown in Windows - you should see the u in shutdown become underlined, i.e. Shutdown to reflect the change.
There is a link in my signature to the MVP Custom PE builder tool if you would like to try it.
Hopefully, the bad sectors are coming from the corrupt MFT bitmap rather than a hardware issue with the SSD, but you won't be able to tell until that issue is fixed first.
Ed, did you have any success with the version of Samsung Magician that I posted a link to in #18?
Thanks Steve I appreciate the help. I am going to download and try the MVP Custom PE Builder tool. I'll let you know how I make out.
Hi Steve, I was able to boot pre-win and ran chkdsk /f didn’t seem to do much, then I ran chkdsk /f /r that found a bunch of corrupt files. I also ran sfc scannow but nothing. I rebooted and still get the error. So I tried it one last time and ran chkdsk /f /r and it still found and supposedly repaired the same exact corrupt files.
I finally just decided to do a backup w/ "ignore bad sectors" and submitted an RMA request w/ Samsung as this SSD is defective. Thanks for your help, my only concern is this is my main PC and no spare SSD ATM so I hope things don’t get worse.
Ed, sorry that the errors don't want to be fixed for the SSD. I hope that Samsung process the RMA quickly for you - I am also using an EVO 970 Plus SSD (only 500GB) in my laptop and normally expect this make of drives to be good for many years service!
My SSD is a NVMe M.2 card type drive, so I do still have the original drive to use in an emergency but that is only 128GB!
Steve. This PC came w/ a Samsung 256GB (not sure what model) it worked fine for over 2 years. It was so small so I updated to this 2TB last oct. Now a few weeks ago it started acting up. Samsung seems to warranty these for 5 years so they know they are usually very good. It looks like I got a bad one :(
I can use the old 256 as emergency. I hope this remains OK until new one gets here.
Ed/ImpetuousRacer, I had a similar issue with a SanDisk SSD. I used HDSentinal Pro (see https://www.hdsentinel.com/hard_disk_sentinel_professional.php) to test the SSD. HDS offers four levels of test of which some will destroy the data, obviously, you don't want to use those tests unless you don't care about the data. In the app you can pick the type of test you want to run and it will be VERY obvious if the test will or will not destroy the data, just pick the one that will NOT destroy the data.
BTW I run HDS at boot time and it has been a lifesaver for me.
In my test I picked the option that would not destroy the data, but move data from bad sectors to good sectors. This can take SEVERAL hours depending on how difficult it is for HDS to move and confirm the data move is successful.
In my case after running HDS I still had issues with the SSD and opened a case with SanDisk and finally got RMA approval. I'm still waiting for the replacement SSD.
FYI just because any application reports good health on a SSD or HD does not mean that the device is issue free. The scope of which is well beyond my skill level. Janos at HDS can explain or possibly one of the Acronis MVPs.
HDS will report the level of health and give you an estimate in days as to how much time you have to replace the device. NOTE this is just an estimate. Due to weird things that can go wrong the actual remaining time could be much shorter. I've used the app for about 10 years and never encountered the issue where a device unexpectantly failed. Currently, on my desktop I have 11 drive. Of which HDS reports 10 at 100% health and my SSD boot drive at 75% health and estimates I have 614 days remaining.
I think ive cracked this ! i had the same trouble as the original poster with file system error stopping at 99% complete and id given up with it following all the advice here and nothing worked , i was changing display cables on my monitors and my pc was going a bit mental trying to figure out the display and i had to start a few times . this caused some loss of data or a reset of something because when i reverted back to the cables that was in the display ports i had originally an acronis pop up notification alerted me that i had to give permission for 2 files to access my external disk that i use for backup purposes and when i allowed these two files to have permission my data backed up without trouble , so i guess when updating or installing acronis software the permissions for acronis to allow access isnt resetting for some reason . its only by chance i came across it.
hope this helps acronis to resolve the problem that some users experience.
I've got the same issue (Run List is Corrupt and "file error" message when attempting backup), ran sfc /scannow, ran chkdsk /r and /f, even did a full windows repair (installs OS system files over itself), and nothing is working. The drive and everything seems to run without issue, so I've got no clue what to make of this.
Dear Daniel Hybiak,
Besides ideas offered in this topic we can also offer to install the latest version of the product: Acronis Cyber Protect Home Office (formerly Acronis True Image) - Integrated Backup and Anti Malware Protection