Macrium Image Backup Fails, due to CRC error first, now MFT errors

W-10 - Build 1903 ---

I must get an image backup, to replace the old 1 TB with errors, with my new 500GB WD SSD. I'm trying to use "Macrium 7.x Free", to back up to a known good USB. (I did an image to that USB from my other PC, = NP). i suspect that Window updates may have failed because of the CRC error that keeps being reported every few days.

Windows Event log does show 47 bad block errors, during all my PC us and backup attempts overnight. I can't read / tell which blocks, or if it is the same error.

Macrum's logged VSS error -->> After it told me the backup failed due to Error code 6 -- CRC Error, this was in the first attempted Image backup VSS log: NOTE: Windows Event Viewer has hundreds of this specific file error, over weeks (at least).

Windows Events*****************************Date: 2/16/2021 2:13:40 AM
Type: Error Event: 455
Source: ESENTsvchost (88624,R,98) TILEREPOSITORYS-1-5-18:
Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

-- The 2ndBackup VSS log also failed with the same "Error Code 6". But, this time the log didn't show anything after normal VSS snapshot errata.

The drive has been throwing a CRC Errors on C: periodically. After searching, I ran Chkdsk C: /r /f after reviewing this thread for "Macrium Error Code 6".

Although I haven't looked extensively at Windows logs, I suspect that Chkdsk ran OK, since it was booted when it finally finished, hours later. But now, the backup still fails, and now it shows an "MFT bad error" instead of a CRC Error. The 3rd Macrium VSS Log shows nothing, other than the snapshot it took.

---

So, I decided it was a great place to stop, and ask for help, before I can't even boot and I corrupt the drive.

• Six months ago, i ran Crystal Disk, and couldn't see any significant problems, no "grown defects", or sectors mapped out, (at least by the drive).
• I can run Chkdsk C: /R as Macrium suggested when it reported the MFT error before shutting down the backup. But, seems I should check to status of boot, BCD, etc. before I do more. That link above, had a post that suggested that I should have Macrium verify "Boot status / partitions". I couldn't find anything in Macruim... Where is it??
• After advice from you guys, I thought I'd start with MiniTool Partition repair, since I had licenses to it a few years ago

Let me know what i should do next. I won't start fixing anything until I hear from someone.

In my experience often times CRC errors are related to failing data cables. You might try pulling and then attaching the data cable on this drive on both ends to see if that helps at all or just swap the cable for another one.

Hi there
VSS can errors sometimes occur if you are imaging to a smaller drive too. The stand alone recovery media won't pull in VSS so you can probably avoid errors from that source.

Before you give up try booting the stand alone version of Macrium to see if you get any further.

Another possibility of rescuing data is to boot up any live linux distro - ensure package ntfs-3g is installed on it (that's the one that gives read/write for NTFS (i.e Windows) files - it usually is by default these days) and then either by using the file explorer (these are pretty well all like the standard Windows file explorer) and copy as much data as you can or failing that simply copy the data partition you are interested in rescuing as follows

dd if=<source partition> of=<target partition or even file> bs=2048M status=progress.

(Note you don't need to format or mount any of the devices to use the command - just plug the devices into your machine).

partitions will be in the form of /dev/sdx which you can see via using lsblk command.

You might be able to recover some data that way but it does seem your HDD is due for a one way trip to the Tip !!!

Cheers
jimbo

Hi

I had this problem when imaging a drive when migrating to win 10.

First check if something as simple as the cable.

Otherwise follow the Macrium suggestion which is to run chkdsk /r on the drive, then retry the backup, if you do it enough times it should finish the backup.

As a last resort there is an option in Macrium to ignore the CRC errors and finish the backup, but be aware when doing that you will have a corrupt backup. The default behaviour is for good reason, its to give peace of mind the backup is of good quality.

Hard disk case: communication errors

Consider backing up files using copy and paste.

Other confirmatory tests can be ran or replace the drive since there are so many bad sectors:

Sea Tools long generic test:
How to use SeaTools for Windows | Seagate Support US

HD Sentinel: (free or trial)
Hard Disk Sentinel - HDD health and temperature monitoring

Crucial System Scanner