Macrium Reflect – Backup aborted! – Unable to read from disk – Error Code 23 – D

Topic

New Reply

I have been using Macrium Workstation for the last 1.5 years for my backups. On last backup got the error message – Backup aborted! – Unable to read from disk – Error Code 23 – Data error (cyclic redundancy check). I asked there support for help and got the following response.

The message: Backup aborted! Unable to read from disk – Error Code 23 – Data error (cyclic redundancy check) is a strong indication that your disk has bad sectors and permanently damaged and if those sectors are in use by the file system, then it’s likely that the data is damaged and unrecoverable. This can signify that your disk is becoming to the end of its life.

In the meantime, you have a chance to patch up the issue with a chkdsk C: /r /f (Change drive letter if applicable). We recommend that you replace the drive as soon as possible and restore a recent image.

I ran chkdsk C: /r /f and at the end it said Scanning and repairing dive (C : 100% complete). Running CHKDSK on C: (OS drive) resulted in the operation getting stuck on 100% for 6 hours.  The only thing I could do is manual reboot.

I tried doing another backup with Macrium and I got the same error message.

I have a Puget Serenity System that is less than 2 years old. I am running Windows 10 Pro version 21H2 and is up to date through August for updates. My primary C Drive is a Samsung 970 EVO 1TB M.2 SSD.

I ran numerous other software programs to check the health of C drive and they said it was healthy. I also ran Samsung’s Magician software that said the health of C drive was good.

I would appreciate any suggestions short of replacing the drive.

I also have Acronis Cyber Protect Home Office that still allows me to backup.

Thanks……….Mark

 

Reply | Quote

Replies

In an elevated Command Prompt (Run as Administrator) run:

DISM /online /cleanup-image /RestoreHealth
sfc /scannow

That may repair any corrupted files. It does not repair the SSD.

Reply | Quote

I would definitely backup any important files ASAP even if just by explorer copy and paste. Could it be that the backup drive is the one causing the error? Have you checked it? Although the 6-hr mark seems long, I’ve had drives take days with a thorough scan, especially if there were issues. After getting a backup you could start with what PKCano suggested then run thorough scans with the mfr utility. If they come back good blank the drive and restore an image and backups.

Reply | Quote

Both PKCano and cyberSAR are spot-on with their suggestions.

Additionally, since you’ve been using Macrium for 1.5 years, if you have to replace your C boot drive (and it sounds like you should) I’d assume you likely have several previous but recent healthy Macrium backup images to fall back on.

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

Modern disks are self checking and correcting (ECC). If they report errors to the OS then they are seriously unwell.
Run the manufacturers diagnostic utility to see what, if anything, can be done.

cheers, Paul

Reply | Quote

@drmark –

I’m curious. When you say ‘backup’ do you mean an image backup or a file and folder backup?

Reply | Quote

Image backup

Reply | Quote

I am out of town at the moment but I will try everyone’s suggestions……..thanks

Reply | Quote

Hello everyone, I had a hard drive that stubbornly wouldn’t clone or image, giving me “Error 0 – Read failed – 23 – Data error (cyclic redundancy check)”. I tried everything suggested in this and other forums to no avail. Windows disk checking, CHKDSK /R, DISM /online /cleanup-image /restorehealth, sfc /scannow, turning off the Verify File System options in various places, the “Forensic Sector Copy” under Advanced Options when cloning, the “Ignore bad sectors when creating images” option under Other Tasks -> Edit Defaults and Settings -> Advanced Settings -> Advanced Backup Settings … none of it worked.

I visited the Macrium forum and found this post which solved my problem with a post from Matt92:

https://forum.macrium.com/55961/Reflect-Home-Error-9-Read-Failed-23?PageIndex=2

Matt92 seemed to have had a similar problem that I did (mine was slightly different), and he seemed to have tried all the same stuff I did. However, he used a third party disk repair tool, Hard Disk Sentinel Pro, to further identify and correct some bad sectors that CHKDSK /R wouldn’t correct.

It seemed unbelievable to me that CHKDSK would fail to repair sectors that were still repairable, but I too used a third party disk repair tool, and thereafter I was able to clone the drive without the dreaded Error 0 – Read failed – 23 – Data error (cyclic redundancy check) bug.

I wanted to post my corroborating evidence on the Macrium Forum, but I don’t have a Supported version of their product that would allow me to post to the Forum. So I found this page in a Google Search result and figured I’d pass along my success story. Hopefully it helps someone else!

4 users thanked author for this post.

wavy, SueW, satrow, PKCano

Reply | Quote

By ignoring bad sectors you are potentially losing data.

Hard disks are self correcting and should never report bad sectors. Any hard disk CRC errors are a major sign of trouble and I would be replacing that disk / cables immediately, rather than risking my data.

Buy yourself a new year present and replace that disk.

cheers, Paul

1 user thanked author for this post.

windbg

Reply | Quote

Hard disks self-eliminate damaged sectors only by marking the damaged blocks as bad and setting a pointer to an alt. in the Reserved area for future use but they can’t fully recover damaged data – it’s effectively lost to the user.

Similar with CHKDSK, it ‘recovers’ and saves fragments that are mostly incomplete and unusable.

If I wanted to recover data from a damaged drive (depending on my knowledge of the history/description of sounds/power application/visual and sniff checks, etc.), I would consider running HDS Pro or a similar tool to ‘fix’ the data before attempting to clone/recover the drive again.

2 users thanked author for this post.

wavy, windbg

Reply | Quote

Data loss will happen if the disk reports an error, but if the data is recovered internally (Error Control and Correction) then no data is lost.
https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/collateral/white-paper/white-paper-the-application-of-ecc-dsp-to-flash-memory.pdf

cheers, Paul

Reply | Quote

Haven’t read it (yet) but the link appears to refer specifically to flash memory.

Reply | Quote

Spinning rust uses the same technique.
https://datarecovery.com/rd/what-are-hard-drive-error-correction-codes-eccs/

cheers, Paul

Reply | Quote