Macrium reflect ошибка 9 read failed 23

Message



Matt92

Matt92

Matt92

posted 26 December 2021 4:33 PM

HOT



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members

Posts: 11,
Visits: 32

I keep getting «Backup aborted! Unable to read from disk — Error Code 23 — Data error (cyclic redundancy check)» whenever I perform a clone.

I’ve done a CHKDSK /R /F three times on my «C:» drive and it finds no errors.

Please don’t tell me my disk has bad sectors and is permanently damaged and close the topic there.
The drive is only 3.5 months old and I want to diagnose with concrete proof what is causing it.

Here is some partition information about my C drive.
The «unallocated» storage at the end of my drive is used for the «Samsung Magician Over Provisioning».
Yes, I have two «Samsung 980 EVO Plus 2 TB» drives. The plan was to use Reflect to backup to the secondary SSD from my main C disk in incremental backups.
I have however a 10 TB HDD which I also tried to backup to, but that fails as well. As mentioned below however, «Acronis TrueImage» works fine on either.

I have tried running a clone via the rescue media (so Windows does not even boot and it uses the Linux based Macrium rescue system) and even that fails leading me to believe there is something else going on with the Reflect software. I used to use Reflect on my Windows 7 machine and it would work fine each and every time (so long as I didn’t use the system and I just let the backup run).

Anyway, some information about my current machine is I am running Windows 10 (with the latest update as of 27 December 2021). I’m using UEFI as the BIOS and a «Samsung 980 EVO Plus NVMe M.2 SSD 2TB» drive.
I have tried disabling the «Verify File System» option and that fails too. I have also tried just doing a «Disc Image» (not a clone), but even that fails.

I am starting to believe there is some sort of bug in the Reflect code which fails on the «Samsung 980 EVO Plus» series due to the internal controller doing something regarding the nature of the SSD.

If you need more information, just let me know as Reflect is the best backup software I’ve ever used and I’d like to keep using it and support your company.
I should note that «Acronis TrueImage» works fine and I’ve been using it for the past month, but it has a few annoyances and I’d prefer Reflect.
Either way, my system can be imaged because if TrueImage works each and every time using the «Volume Shadow Copy Service» then I don’t see why Reflect cannot.

I’d really like to get this resolved no matter what it takes.

Thanks.

Edited
28 December 2021 8:23 PM by
Matt92


Reply


Like
0



JK

JK

JK

posted 26 December 2021 5:58 PM



JK

Macrium Hero

Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)

Group: Forum Members

Posts: 1.5K,
Visits: 5.8K

Matt, welcome to the other side.  I left ATI almost one year ago; there are other users on this forum with more expertise than me who will be able to sort out your problem.

In the meantime, maybe you can clarify a few things.  You talk about doing «cloning» (and you have posted in the cloning forum), but you also say that your plan is to use incremental backups (which is not possible with cloning, as far as I know).  So perhaps you can clarify what you are trying to achieve.

In addition, you have mentioned the error message encountered, but it would be helpful if you post a copy of the log file from one of the failed cloning jobs.  If you are using a paid copy of Reflect, your license code will be shown at the bottom of your log files — please delete this info before posting the log.

                                


Reply


Like
0



Matt92

Matt92

Matt92

posted 26 December 2021 6:05 PM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members

Posts: 11,
Visits: 32

Matt, welcome to the other side.  I left ATI almost one year ago; there are other users on this forum with more expertise than me who will be able to sort out your problem.

In the meantime, maybe you can clarify a few things.  You talk about doing «cloning» (and you have posted in the cloning forum), but you also say that your plan is to use incremental backups (which is not possible with cloning, as far as I know).  So perhaps you can clarify what you are trying to achieve.

In addition, you have mentioned the error message encountered, but it would be helpful if you post a copy of the log file from one of the failed cloning jobs.  If you are using a paid copy of Reflect, your license code will be shown at the bottom of your log files — please delete this info before posting the log.

Basically I’m happy with either method of the backup, but preferably I’d like to do incremental backups.
I have checked the logs and I see some confidential metadata contained within it so I don’t feel comfortable posting it publicly. Can I send it as a PM to you? 

Edited
26 December 2021 6:06 PM by
Matt92


Reply


Like
0



JK

JK

JK

posted 26 December 2021 6:29 PM



JK

Macrium Hero

Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)

Group: Forum Members

Posts: 1.5K,
Visits: 5.8K

It would be better if you edit to redact anything confidential, and then post it here.  It would be forum users other than me who would know better what to look for in the logs (unless it is something obvious).

Since your goal is to do incremental backups, I would recommend that you start by attempting a full image backup of all contents of your first Samsung 970 disk, and then post the redacted log.

By the way, the partition layout on your system disk looks odd for a UEFI boot system — the MSR is missing and the Recovery partition is in the wrong location.  But since this is a presumably a bootable system, it may not be a big deal.  Something to keep in mind, though, in case it is playing some role in the problem.

                                


Reply


Like
0



Matt92

Matt92

Matt92

posted 26 December 2021 11:00 PM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members

Posts: 11,
Visits: 32

Sure, I will do a full image backup of all contents of my primary «Samsung 980» disk and then post the redacted log. I am just running a backup with «Acronis TrueImage» currently, so when it’s done I’ll attempt the full image Reflect backup and share the log.

Edited
28 December 2021 8:24 PM by
Matt92


Reply


Like
0



jphughan

jphughan

jphughan

posted 27 December 2021 1:28 PM



jphughan

Macrium Evangelist

Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)Macrium Evangelist (21K reputation)

Group: Forum Members

Posts: 14K,
Visits: 81K

Just as a data point, I have a Samsung 970 Evo Plus and have no issues running Reflect for daily image backups. Are you sure the error you’re seeing occurs when backing up the C partition and not one of the hidden partitions? You may be running CHKDSK /R against the wrong partition. The log might help determine that. Copy/pasting the text of the log, removing your license key from the end and any other data you wish, would be helpful.

Edited
27 December 2021 1:29 PM by
jphughan


Reply


Like
0



Seekforever

Seekforever

Seekforever

posted 27 December 2021 3:33 PM



Seekforever

Guru

Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)Guru (1.5K reputation)

Group: Forum Members

Posts: 991,
Visits: 22K

«The drive is only 3.5 months old.»
This has little, if anything, to do with the drive has or has not failed. Electronics stuff can fail with or without warning at anytime but the most likely times are when it is quite new which is the «infant  mortality» zone and when it is quite old which is in the «old and worn-out» zone. Most reliable times are in-between those 2 zones.
Incidentally, my new computer’s power supply failed at the 4 month time — I’m waiting for the warranty replacement right now.


Reply


Like
0



dbminter

dbminter

dbminter

posted 27 December 2021 9:14 PM



dbminter

Macrium Evangelist

Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)Macrium Evangelist (7.2K reputation)

Group: Forum Members

Posts: 4.5K,
Visits: 48K

I’ve had optical disc drives die within 2 months after purchase and I’ve had one that lasted 2.5 years, where optical disc drives generally last about 7 months before needing replacing.  So, there’s no real rhyme or reason to why electronics die early or last well beyond their expected life span.


Reply


Like
0



Matt92

Matt92

Matt92

posted 28 December 2021 2:47 AM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members

Posts: 11,
Visits: 32

Log is attached.

Attachments



346D377971F8A0BF-00-00.html

(2 views,
25.00 KB)


Reply


Like
0



JK

JK

JK

posted 28 December 2021 3:32 AM



JK

Macrium Hero

Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)Macrium Hero (2.3K reputation)

Group: Forum Members

Posts: 1.5K,
Visits: 5.8K

This Macrium blog posts allows for the possibility that a disk may have bad sectors that are not fixed by chkdsk /r, and therefore can only be imaged if the option to ignore bad sectors is enabled:

  1. Select Other tasks > Edit defaults > Advanced.
  2. Select Ignore bad sectors.
  3. Click OK.

Alternatively, if you create the image from the Reflect Rescue Environment, then the option to ignore bad sectors is always enabled.

Thus, I would suggest repeating the imaging attempt with the above option enabled.  If the Error 23 problem was in fact caused by bad sectors on the C: drive, then this will show up in the log.  If the log does not show bad clusters, then the problem lies elsewhere.

@jphughan may have other suggestions (and I would defer to his advice, if it differs from my ownb).

                                


Reply


Like
0

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
Status
Not open for further replies.

Jmusic88


  • #1

I am having trouble cloning using Macrium Reflect. The first try I got Error 9 (Read failed), and then second try I got Error 23 (cyclic redundancy check). Both failed at 64%.

Anyone had these issues before or know how to fix it for a successful clone?

EDIT: I did select «Ignore bad sectors when creating images» in the advanced settings.

View: https://imgur.com/a/yZuhZw0View: https://imgur.com/a/IaFIiM5

Thank you in advance.

Jmusic88


  • Jmusic88

    Jmusic88

Hi all. Thanks for the help but Macrium was not the best program to clone for me. I used easeus todo backup. Easeus todo worked flawlessly, it did not give me any errors whatsoever.

I did run chkdsk though after Macrium and prior to Easeus so I wouldn’t know if Macrium would of worked the 3rd try. I just did not want to waste writing operations on my SSD that were not needed. Macrium however was the only program I found that you could choose which partition to exclude which was nice. But my workaround was to clone the whole disk since I had no choice, then delete the partition and use MiniTool Partition Wizard to merge non-adjacent partition. I was lucky enough that even though my SSD was smaller than my HDD, my occupying data was…

richiestang_78



Mar 3, 2015


5,965


690


37,990


  • #2

Both those errors are read errors. Is the drive you are trying got copy from damaged or corrupt? This is what it sounds like to me.

Jmusic88


  • #3

Both those errors are read errors. Is the drive you are trying got copy from damaged or corrupt? This is what it sounds like to me.

I am not sure perhaps? I did pause my esnet32 anti virus as well when I tried my 2nd attempt, but in my 2nd attempt another error appeared (error 23)

Jmusic88


  • #4

Both those errors are read errors. Is the drive you are trying got copy from damaged or corrupt? This is what it sounds like to me.

During a SMART health check, its at 99% with 1 raw value at current pending sector count. Maybe that’s what it is? But I don’t know how to fix it.

popatim



Dec 2, 2009


38,874


970


135,890


  • #5

This can take several hours, plan accordingly.

Run CMD as Administrator (right click on CMD then select Run as Admin)
In the CMD window — type in chkdsk X: /r & hit enter

  • replace X: with the actual letter of the drive you want to test
  • if the drive is an SSD then use /f instead of /r

Checkdisk will now check the drive for errors and bad sectors and you will see the progress in the CMD window — unless this is the boot drive.

If this is your boot drive, it will ask if you want to run this on the next restart — select yes and restart the PC when you are ready.
Unless you sit and watch the progress fullscreen, you will need to check the results using Event Viewer.

Here is a guide:
https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

Last edited:

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #6

Cloning with a bad source drive is an exercise in futility.
Even if it completes, what data got skipped?

Cloning is great when conditions are perfect. Here, they are clearly NOT perfect.

Jmusic88


  • #7

This can take several hours, plan accordingly.

Run CMD as Administrator (right click on CMD then select Run as Admin)
In the CMD window — type in chkdsk X: /r & hit enter

  • replace X: with the actual letter of the drive you want to test
  • if the drive is an SSD the use

/f instead of /r

Checkdisk will now check the drive for errors and bad sectors and you will see the progress in the CMD window — unless this is the boot drive.

If this is your boot drive, it will ask if you want to run this on the next restart — select yes and restart the PC when you are ready.
Unless you sit and watch the progress fullscreen, you will need to check the results using Event Viewer.

Here is a guide:
https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

I will give that a try tomorrow thank you!

Jmusic88


  • #8

Cloning with a bad source drive is an exercise in futility.
Even if it completes, what data got skipped?

Cloning is great when conditions are perfect. Here, they are clearly NOT perfect.

I did successfully clone my HDD using easeus todo. The only thing is I can’t deselect partition so it clones the whole thing. I then tried to delete my data partition and merge it but couldn’t because it’s not an adjacent partition. I then used aeomi partition assistant to merge non adjacent partitions and it ruined my windows copy on my SDD lol. So I’ll clean it up and try again using macrium reflect tomrorow with the suggestion above.

Last edited:

Jmusic88


  • #9

Hi all. Thanks for the help but Macrium was not the best program to clone for me. I used easeus todo backup. Easeus todo worked flawlessly, it did not give me any errors whatsoever.

I did run chkdsk though after Macrium and prior to Easeus so I wouldn’t know if Macrium would of worked the 3rd try. I just did not want to waste writing operations on my SSD that were not needed. Macrium however was the only program I found that you could choose which partition to exclude which was nice. But my workaround was to clone the whole disk since I had no choice, then delete the partition and use MiniTool Partition Wizard to merge non-adjacent partition. I was lucky enough that even though my SSD was smaller than my HDD, my occupying data was substantially less than my SSD.

MiniTool Partition was the only program that was free without limitation on the merging and it literally took me 2 minutes. I tried AEOMIS Partition Assistant trial Pro, but it requires you to go to either Windows PE Environment or PreOS Environment, eitherway AEOMIS completely ruined my windows copy to the point I was unable to recover. I followed their step by step instruction as well.

Again thank you for the help.

Status
Not open for further replies.

Similar threads

ex_bubblehead

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions

Macrium Reflect error 9 is a common clone failed error code. What should you do if you are plagued by this annoying issue during the cloning process using Macrium Reflect? In this post, MiniTool shows you details on this problem including some effective solutions. Besides, its cloning software is recommended.

Macrium Reflect Clone Failed Error 9

Macrium Reflect is a professional backup utility for the Windows operating system that can be used to create disk images using Microsoft Volume Shadow Copy Service. Besides, it allows you to back up whole partitions or individual files & folders and clone a hard drive to another hard disk without reinstalling the operating system.

Although it is excellent and powerful, you may encounter some errors. According to users, Macrium Reflect error code 9 often appears, letting you frustrated. To be specific, during the cloning process (usually, the progress is done 95%+), a message appears on the computer screen saying (one of the followings):

  • Unknown error. – Error code = 9
  • Cloned failed – error 9
  • Cloned failed – error 9 – Read failed – 23 – Data error (cyclic redundancy check)

In addition to clone failed error 9, sometimes you run into other issues when cloning a hard drive, for example, Macrium Reflect clone failed error 0, error 8, read failed 13 broken pipe, etc.

Macrium Reflect error code 9

Why Macrium Reflect clone failed with an error code 0, 8, 9, or 13? There are some common reasons:

  1. The cable between the disk and the PC is not properly connected.
  2. Your hard drive has bad blocks.
  3. Antivirus software is enabled and blocks cloning.
  4. File system errors exist in your source or target disk.

When confronted with Macrium Reflect error 9/8/0/13, the urgent thing should be looking for solutions to fix this clone failed error. By analyzing the reasons, you can know what you should do. Now, let’s move to the next part to find some effective workarounds.

Related post: Look! Top 5 Solutions to Macrium Reflect Clone Failed Error

Troubleshooting Tips in Case of Macrium Reflect Error 9

Check the Connection

A bad cable can disrupt the process of cloning the hard drive, USB drive, SD card, etc. Macrium Reflect error 9 read failed 23 may be triggered by the connection issue between the drive and the computer.

Go to open the computer case to check if the connection is proper. If there is dust on the connector, clear it. Or, you can try a new cable to connect the device to your PC since the cable is easy to get corrupted. Then, start cloning again. If the connection is correct, move to the other fixes below.

Check Bad Sectors on Your Hard Drive

Bad sectors refer to the sectors that cannot be accessed by any software due to permanent damage. If your hard disk (either source drive or target drive) has some bad sectors, Macrium Reflect will fail to perform the cloning process with clone failed error 9/0/8/13.

To know if there are bad sectors on your hard drive, you can perform a check. To do this thing, we recommend using the professional partition manager – MiniTool Partition Wizard. It allows you to manage your disks and partitions, perform disk cloning & system migration, convert a disk, convert a file system, test a disk, etc. Just get its free edition by tapping on the following button to perform a disk test to see if bad sectors exist.

MiniTool Partition Wizard FreeClick to Download100%Clean & Safe

Step 1: Launch MiniTool Partition Wizard to its main interface.

Step 2: Right-click on the hard drive and choose Surface Test.

Step 3: Tap on Start Now to start the check. If there are bad sectors, this partition manager can mark the blocks in red.

MiniTool Partition Wizard surface test

If bad sectors are detected, go to run CHKDSK to mark these sectors to skip them in normal operations.

Step 1: Type Win + R, enter cmd, and press Ctrl + Shift + Enter to open Command Prompt with admin rights. If prompted by the UAC window, click Yes.

Step 2: Type chkdsk c: /r /f and press Enter. Replace c with your drive letter. This command can help scan the drive, repair all the disk errors, and shield bad sectors or corruption it finds.

After that, try to clone your hard drive using Macrium Reflect and see if the clone failed error 9/0/8/13 disappears.

Clean Your Hard Drive

A corrupted file system on the destination hard drive can trigger Macrium Reflect error code 9 or Macrium Reflect error 0/8/13. Usually, the corruption is induced by logical errors and you can try to run the clean command to clean the structure of your destination disk to fix the clone issue.

Tips:

Before cleaning your hard drive, make sure there is no important data saved on the target disk. Or else, data loss will happen. To keep data safe, you can run the professional PC backup software – MiniTool ShadowMaker to back up files.

MiniTool ShadowMaker TrialClick to Download100%Clean & Safe

To do this, follow the steps below:

Step 1: Open Command Prompt as an administrator.

Step 2: In the CMD window, execute the following commands one by one. Remember to press Enter after each one.

diskpart

list disk

select disk n (n means the disk number of the target hard drive)

clean all (this command cleans all the data and disk structure)

clean hard drive

After that, re-clone your hard drive to the target disk to check if Macrium Reflect error code 0/8/9/13 is fixed.

Disable Antivirus Software

An antivirus program is helpful to block your PC from viruses and malware attacks with real-time protection. But sometimes it can mistake Macrium Reflect for malware and prevent it from working properly. As a result, the cloning process is blocked and you encounter Macrium Reflect error 9, Macrium Reflect error 8, or 0. To get rid of this issue, you need to disable your antivirus software.

In Windows 11/10, the built-in program is Windows Security, also known as Windows Defender. To fix Macrium error 9, follow the steps below to disable this tool:

Step 1: In Windows 11/10, click the search icon, type Windows Security, and click the app to open.

Step 2: Tap on Virus & threat protection > Manage settings under Virus & threat protection settings.

Step 3: Disable Real-time protection by switching the option to Off.

disable Windows Defender

Tips:

In addition to this way, you can try other ways to disable Windows Defender and go to this previous post — [Solution] How to Disable Windows Defender Antivirus on Win10/11 to know details.

If you use third-party antivirus software, the way to disable it is different based on the different vendors. Find steps online and do this task. After the operation, try to clone your hard drive again and see if Macrium Reflect error 9 is removed.

Create Image Backup Instead of Cloning

If all of the fixes above cannot do the trick to solve the Macrium Reflect clone failed error 9/8/0, you need to switch your approach. To back up your hard drive, you can choose to make a disk image backup instead of cloning it.

A disk image refers to making a backup copy of the hard drive. During the process, all the contents are compressed and saved to an image file that can be stored to an external hard drive, USB drive, network, etc. In case of computer accidents, you can use the image file to perform a recovery.

While disk cloning means completely copying the contents of a hard drive to another hard drive and you can directly access data on the target disk. To know more information about image backup and cloning, you can refer to our previous post – Clone VS Image: What’s the Difference? Get the Answer Now.

To avoid encountering cloned failed error 9/8/0/13, go to create a disk image backup. Go to launch Macrium Reflect, choose the target disk and click Image this disk. Then, finish the rest operations by following the instructions on the screen.

image your disk Macrium Reflect

Clone Hard Drive Using MiniTool ShadowMaker – Alternative to Macrium Reflect

If you are not lucky and fail to fix the Macrium Reflect clone failed error 9 read failed 23 or Macrium Reflect cloned failed error 0/8/13, or you don’t want to spend much time troubleshooting this issue, you can try an alternative to Macrium Reflect to clone your hard drive.

According to reports, Macrium Reflect always throws an error code in numerous cases when you run it for disk cloning whereas other software like MiniTool ShadowMaker or MiniTool Partition Wizard can do the work properly.

MiniTool ShadowMaker is a professional and free Windows backup software that enables you to create image backups for the operating system, disks, partitions, and files & folders. Besides, it offers a feature called Clone Disk that helps easily clone your hard drive to another disk, clone a USB drive, clone an SD card, clone HDD to SSD, etc.

Now, tap on the following download button to get the installer of MiniTool ShadowMaker, and then double-click on the file to finish the installation. Next, start cloning your hard disk.

MiniTool ShadowMaker TrialClick to Download100%Clean & Safe

Step 1: After connecting your target disk to the PC, launch MiniTool ShadowMaker and then click Keep Trial to go on.

Step 2: Click on the Tools tab from the left pane and then choose Clone Disk in the new window.

MiniTool ShadowMaker clone disk

Step 3: You need to choose a source disk and target disk, and then click Start to begin the cloning process.

Step 4: Wait some time and the cloning operation will complete successfully.

After that, you can open the computer case, remove the source disk and put the target disk into the original place. Then, boot the PC from the cloned disk and Windows can run properly.

Tips:

Sometimes you may run into the issue of cloned disk not booting. The reasons behind this issue are various and you can fix easily it. Go to our previous post — What If Cloned Drive/SSD Won’t Boot Windows 11/10/8/7? Fix It to find reasons and solutions.

Further Reading: MiniTool Partition Wizard for Disk Cloning

In addition to MiniTool ShadowMaker, you can run another alternative to Macrium Reflect – MiniTool Partition Wizard to clone your hard drive without encountering clone failed error 0/8/9. This cloning software offers two options for disk cloning.

One is Migrate OS to SSD/HD Wizard which enables you to migrate the entire system disk or only transfer the operating system to an SSD/HD. Another one is Copy Disk which helps you clone the system disk or data disk to another hard disk. Get this tool and choose one feature to start cloning.

MiniTool Partition Wizard DemoClick to Download100%Clean & Safe

MiniTool Partition Wizard clone disk

Bottom Line

Now you come to the end of this post. From this guide, you know how to fix the Macrium Reflect clone failed error 9/8/0/13 in multiple ways. If you are bothered by this annoying issue, follow the given fixes to get rid of the trouble.

To clone a hard drive to another disk with ease, we recommend using MiniTool software – MiniTool ShadowMaker or MiniTool Partition Wizard without using Macrium Reflect. This tool always throws an error code when cloning your disk and troubleshooting issues is troublesome and time-consuming.

Besides, if you have any ideas on MiniTool software or find useful fixes for Macrium Reflect error 9, remember to tell us. You can leave a comment in the following part and we will reply to you soon.

Message


Matt92

Matt92

Matt92

posted 26 December 2021 4:33 PM

HOT



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members
Posts: 11,
Visits: 32

I keep getting «Backup aborted! Unable to read from disk — Error Code 23 — Data error (cyclic redundancy check)» whenever I perform a clone.

I’ve done a CHKDSK /R /F three times on my «C:» drive and it finds no errors.

Please don’t tell me my disk has bad sectors and is permanently damaged and close the topic there.
The drive is only 3.5 months old and I want to diagnose with concrete proof what is causing it.

Here is some partition information about my C drive.
The «unallocated» storage at the end of my drive is used for the «Samsung Magician Over Provisioning».
Yes, I have two «Samsung 980 EVO Plus 2 TB» drives. The plan was to use Reflect to backup to the secondary SSD from my main C disk in incremental backups.
I have however a 10 TB HDD which I also tried to backup to, but that fails as well. As mentioned below however, «Acronis TrueImage» works fine on either.

I have tried running a clone via the rescue media (so Windows does not even boot and it uses the Linux based Macrium rescue system) and even that fails leading me to believe there is something else going on with the Reflect software. I used to use Reflect on my Windows 7 machine and it would work fine each and every time (so long as I didn’t use the system and I just let the backup run).

Anyway, some information about my current machine is I am running Windows 10 (with the latest update as of 27 December 2021). I’m using UEFI as the BIOS and a «Samsung 980 EVO Plus NVMe M.2 SSD 2TB» drive.
I have tried disabling the «Verify File System» option and that fails too. I have also tried just doing a «Disc Image» (not a clone), but even that fails.

I am starting to believe there is some sort of bug in the Reflect code which fails on the «Samsung 980 EVO Plus» series due to the internal controller doing something regarding the nature of the SSD.

If you need more information, just let me know as Reflect is the best backup software I’ve ever used and I’d like to keep using it and support your company.
I should note that «Acronis TrueImage» works fine and I’ve been using it for the past month, but it has a few annoyances and I’d prefer Reflect.
Either way, my system can be imaged because if TrueImage works each and every time using the «Volume Shadow Copy Service» then I don’t see why Reflect cannot.

I’d really like to get this resolved no matter what it takes.

Thanks.

Edited
28 December 2021 8:23 PM by
Matt92


Reply


Like
0


JK

JK

JK

posted 26 December 2021 5:58 PM



JK

Macrium Hero

Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)

Group: Forum Members
Posts: 1.3K,
Visits: 5.2K

Matt, welcome to the other side.  I left ATI almost one year ago; there are other users on this forum with more expertise than me who will be able to sort out your problem.

In the meantime, maybe you can clarify a few things.  You talk about doing «cloning» (and you have posted in the cloning forum), but you also say that your plan is to use incremental backups (which is not possible with cloning, as far as I know).  So perhaps you can clarify what you are trying to achieve.

In addition, you have mentioned the error message encountered, but it would be helpful if you post a copy of the log file from one of the failed cloning jobs.  If you are using a paid copy of Reflect, your license code will be shown at the bottom of your log files — please delete this info before posting the log.


Reply


Like
0


Matt92

Matt92

Matt92

posted 26 December 2021 6:05 PM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members
Posts: 11,
Visits: 32

Matt, welcome to the other side.  I left ATI almost one year ago; there are other users on this forum with more expertise than me who will be able to sort out your problem.

In the meantime, maybe you can clarify a few things.  You talk about doing «cloning» (and you have posted in the cloning forum), but you also say that your plan is to use incremental backups (which is not possible with cloning, as far as I know).  So perhaps you can clarify what you are trying to achieve.

In addition, you have mentioned the error message encountered, but it would be helpful if you post a copy of the log file from one of the failed cloning jobs.  If you are using a paid copy of Reflect, your license code will be shown at the bottom of your log files — please delete this info before posting the log.

Basically I’m happy with either method of the backup, but preferably I’d like to do incremental backups.
I have checked the logs and I see some confidential metadata contained within it so I don’t feel comfortable posting it publicly. Can I send it as a PM to you? 

Edited
26 December 2021 6:06 PM by
Matt92


Reply


Like
0


JK

JK

JK

posted 26 December 2021 6:29 PM



JK

Macrium Hero

Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)

Group: Forum Members
Posts: 1.3K,
Visits: 5.2K

It would be better if you edit to redact anything confidential, and then post it here.  It would be forum users other than me who would know better what to look for in the logs (unless it is something obvious).

Since your goal is to do incremental backups, I would recommend that you start by attempting a full image backup of all contents of your first Samsung 970 disk, and then post the redacted log.

By the way, the partition layout on your system disk looks odd for a UEFI boot system — the MSR is missing and the Recovery partition is in the wrong location.  But since this is a presumably a bootable system, it may not be a big deal.  Something to keep in mind, though, in case it is playing some role in the problem.


Reply


Like
0


Matt92

Matt92

Matt92

posted 26 December 2021 11:00 PM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members
Posts: 11,
Visits: 32

Sure, I will do a full image backup of all contents of my primary «Samsung 980» disk and then post the redacted log. I am just running a backup with «Acronis TrueImage» currently, so when it’s done I’ll attempt the full image Reflect backup and share the log.

Edited
28 December 2021 8:24 PM by
Matt92


Reply


Like
0


jphughan

jphughan

jphughan

posted 27 December 2021 1:28 PM



jphughan

Macrium Evangelist

Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)Macrium Evangelist (20K reputation)

Group: Forum Members
Posts: 13K,
Visits: 78K

Just as a data point, I have a Samsung 970 Evo Plus and have no issues running Reflect for daily image backups. Are you sure the error you’re seeing occurs when backing up the C partition and not one of the hidden partitions? You may be running CHKDSK /R against the wrong partition. The log might help determine that. Copy/pasting the text of the log, removing your license key from the end and any other data you wish, would be helpful.

Edited
27 December 2021 1:29 PM by
jphughan


Reply


Like
0


Seekforever

Seekforever

Seekforever

posted 27 December 2021 3:33 PM



Seekforever

Guru

Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)

Group: Forum Members
Posts: 899,
Visits: 20K

«The drive is only 3.5 months old.»
This has little, if anything, to do with the drive has or has not failed. Electronics stuff can fail with or without warning at anytime but the most likely times are when it is quite new which is the «infant  mortality» zone and when it is quite old which is in the «old and worn-out» zone. Most reliable times are in-between those 2 zones.
Incidentally, my new computer’s power supply failed at the 4 month time — I’m waiting for the warranty replacement right now.


Reply


Like
0


dbminter

dbminter

dbminter

posted 27 December 2021 9:14 PM



dbminter

Macrium Evangelist

Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)Macrium Evangelist (6.9K reputation)

Group: Forum Members
Posts: 4.3K,
Visits: 44K

I’ve had optical disc drives die within 2 months after purchase and I’ve had one that lasted 2.5 years, where optical disc drives generally last about 7 months before needing replacing.  So, there’s no real rhyme or reason to why electronics die early or last well beyond their expected life span.


Reply


Like
0


Matt92

Matt92

Matt92

posted 28 December 2021 2:47 AM



Matt92

New Member

New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)New Member (25 reputation)

Group: Forum Members
Posts: 11,
Visits: 32

Log is attached.

Attachments



346D377971F8A0BF-00-00.html

(2 views,
25.00 KB)


Reply


Like
0


JK

JK

JK

posted 28 December 2021 3:32 AM



JK

Macrium Hero

Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)Macrium Hero (2K reputation)

Group: Forum Members
Posts: 1.3K,
Visits: 5.2K

This Macrium blog posts allows for the possibility that a disk may have bad sectors that are not fixed by chkdsk /r, and therefore can only be imaged if the option to ignore bad sectors is enabled:

  1. Select Other tasks > Edit defaults > Advanced.
  2. Select Ignore bad sectors.
  3. Click OK.

Alternatively, if you create the image from the Reflect Rescue Environment, then the option to ignore bad sectors is always enabled.

Thus, I would suggest repeating the imaging attempt with the above option enabled.  If the Error 23 problem was in fact caused by bad sectors on the C: drive, then this will show up in the log.  If the log does not show bad clusters, then the problem lies elsewhere.

@jphughan may have other suggestions (and I would defer to his advice, if it differs from my ownb).


Reply


Like
0

Clone failed error 9 is an application error message displayed by the Macrium Reflect software when an error or fault occurs during the cloning of a disk. Reflect is a disk backup, cloning, and imaging software available for individual users to download and use for free. Disk cloning is the process of ultimately creating an exact one-to-one copy of the disk. This could be seen as the RAID 1 configuration in which an exact mirror copy of the disk is saved as Redundant Data. Macrium Reflect is an excellent tool for disk management and can easily clone disks, but sometimes problems like clone failed error 9 can come up.

Reflect is a free-to-download disk management tool used by many users throughout the world for backing up, cloning, or imaging disks. The software is free to use for individual home users, and it is licensable for business and server enterprise purposes. The program can face some issues during the cloning process, such as the corruption of data, file system issues, etc., leading to clone failed error 9.

Message box after downloading Macruim Reflect 8 installer

Message box after downloading Macruim Reflect 8 installer

Download the Macruim Reflect Free from its official website https://www.macrium.com/reflectfree?mo#. Head to the download page and Tick the purpose of your download, enter your email to signup, and begin the download. You could also download the Macrium Reflect home edition for 30 days free trial, which provides some advance and rich features.

Macrium Reflect Download Agent

Macrium Reflect Download Agent

Reason for Clone failed error 9

Errors can show up for many potential reasons. Each error message represents a different cause for the error. In the case of clone failed error, the primary reason is the failure of the CRC (Cyclic Redundancy Check) checksum of the data stored in the disk in the form of files. CRC is an algorithm used to test the integrity of the data or file. If the CRC test fails, that means the data is corrupted or altered somehow.

There could be many reasons for the failure of the CRC test of a file or any data. The most probable explanation is the presence of malware on the system that is slowly corrupting the disk’s file system. Other causes are also possible such as the harmful physical condition of the disk, etc. In such scenarios, users are more likely to experience messages like clone failed error 9.

Fixing Xtools XToolkit Installation Error

Solutions for clone failed error 9

There are quite a few ways that a user can try to rectify clone failed error 9. The following are the most reliable solutions that the users can employ.

Running an SFC scan

System File Check(SFC) is a system utility program that can deal with most of the problems caused by corrupt files. It scans the system’s corrupt files and restores them automatically. Follow the given steps to run an SFC scan. It requires administrator privileges to execute.

  • Right click on the start menu.
  • click on Windows PowerShell (Admin).
  • Type sfc /scannow in the shell and hit enter.

Depending on your system and the number of issues found, the process would take time to complete.

running an sfc scan to resolve clone failed error 9

Running an SFC scan

Disable Antivirus software

Antivirus softwares continuously scans the system in the background to prevent it from threats and vulnerabilities. If Macrium reflect or Antivirus software are accessing the same portion of the disk simultaneously, chances are there might be some conflict regarding the access of the portion of the disk, which ultimately can lead to a clone failed error 9. Or sometimes, The antivirus won’t allow the cloning program to interact with the disk’s file system due to security concerns.

Therefore it is recommended that the users disable the Antivirus software while the Cloning process is being carried out, especially if the user is continuously receiving failure error 9. Different antivirus has different procedures to disable their default background operation temporarily. Disable your antivirus accordingly.

Run Disk Cleanup

Running the disk cleanup utility can help the user get rid of the clone failed error 9 as the utility program cleans the disk appropriately and removes any corrupt temporary files. Follow the given steps to run the disk cleanup utility on your target disk (the disk you are trying to clone).

  • Open start menu.
  • Type disk cleanup in the search bar.
  • Open the Disk Cleanup program.
  • Select the drive you want to clean.
  • Let the process finish.
  • Clean the temporary files as suggested.
  • Click on OK.

Disk Cleanup

Disk Cleanup

Disk cleanup diskpart

Disk cleanup can also be performed using the Windows Diskpart utility. Follow the given steps to clean the disk using the command-line diskpart utility.

  • Press Windows key + R.
  • Enter cmd in the search box and hit enter.
  • In the shell type diskpart and hit enter.
  • Diskpart utilty would open in a different window.
  • Type list disk in the shell to list the attatched disk.
  • type select disk X ( your disk number).
  • type clean and hit enter.

Microsoft Diskpart

Run a chkdsk scan

Chkdsk is short for Check disk. It is a command-line utility used to check, recover, and repair disks from any sort of damage. Administrator privileges are required to run this utility. Follow the given steps to eradicate clone failed error 9 using chkdsk.

  • Right Click on the start menu.
  • Open Windows PowerShell (Admin).
  • Enter ‘chkdsk /f /r‘ in the shell and hit enter.
  • Reboot your system when finished.

/f stands for a fix. It fixes the issues found during the scanning. /r stands for restore. It tries to restore the data.

Avoid Bad sectors

Another way to avoid the clone failed error 9 is to ignore the bad sectors of the disk that are causing the problem. This could be done within the reflect application settings themselves. Follow the given procedures to ignore bad sectors.

  • Open the Macrium relflect application.
  • Go to Advanced option in the upper menu.
  • On the left side, Open Advanced Backup Options.
  • Tick the checkbox that says Ignore bad sectors when creating images.
  • Click OK.

The Ultimate Guide to Fixing Wabbajack Failed Unknown Error

FAQs on Clone Failed Error 9

What is the complete form of RAID?

It stands for Redundant Array of Independent Disks. It is a data storage technology scheme.

Differentiate between disk cloning and backup?

Backing up data means copying the data to another disk to restore it if the original data is lost. Cloning is when you have to change the disk itself but copy the exact data and file system in the new disk. For example, upgrading from an HDD to SSD, you don’t want to change the data, but you could change the drive after cloning.

What do you mean by disk imaging?

It means cloning the entire disk into another disk but in archived and compressed form.

Conclusion

Macrium Reflect is a disk data management software used by users worldwide. Due to some data corruption and other reasons, users could face errors like clone failed error 9 during the cloning process of a disk. In this article, we provide you with many easy ways to employ yourself to get rid of this error.

Trending Now

  • Fixing Xtools XToolkit Installation Error

    Fixing Xtools XToolkit Installation Error

    March 3, 2023

  • Troubleshoot DeepMotion Preview Not Working: Tips and Tricks

    Troubleshoot DeepMotion Preview Not Working: Tips and Tricks

    by Dharam Nath JhaMarch 3, 2023

  • Getting Virtwifi has No Internet Access? Here’s What to Do!

    Getting Virtwifi has No Internet Access? Here’s What to Do!

    by Dharam Nath JhaFebruary 16, 2023

  • The Ultimate Guide to Fixing Wabbajack Failed Unknown Error

    The Ultimate Guide to Fixing Wabbajack Failed Unknown Error

    by Dharam Nath JhaFebruary 16, 2023

Macrium Reflect is a backup tool for Microsoft Windows. Many users have encountered an error while cloning their HDD to an SSD or a new HDD. This error states “Clone failed – Error 9” and it prevents you to clone your drive. The “macrium reflect error 9″ can be solved easily by going through the solutions explained in this article.

macrium reflect error 9 while cloning the drive

Error Message

What causes the error 9 in Macrium Reflect?

There are different reasons that cause the macrium reflect error 9 in different situations. Some of the most common reasons are listed below:

  • Improper cable connection might cause this issue.
  • Bad Sectors in the storage device can cause this error.
  • Your antivirus software might be blocking some of the features.
  • This error might occur if the disk has a file system error.

Pre tips:

The error 9 might be encountered by anyone anytime. In most of the cases, the physical connection between both of the drives is loose, that is why you see this error. So if this error pops up on your screen, make sure you have connected the drive properly. If it doesn’t help, try to replace the connecting cable because the cable might get damaged easily if it is used excessively.

What to do if you get the “Macrium Reflect Error 9” on backup?

Solution 1: Disable or Uninstall Third-party Antivirus Softwares

If the error 9 appears, the reason might be that antivirus is blocking some features of the system. Third-party antiviruses are good to some extent but sometimes they create a problem by blocking some features of the system. So to resolve this error, turn-off your third party antiviruses and reboot the system to check if this problem is resolved.

Solution 2: Clean the Target Disk to Resolve macrium reflect error 9

If you still encounter the macrium reflect error 9, run a disk cleanup of the destination disk. Follow the steps below to carry this task out.

  1. Click the search button in the taskbar. Type and open Diskpart.
    Type diskpart in Search bar
    Diskpart
  2. Write the following commands one by one and hit enter to execute them. (Note that X represents the Number of your Target drive)
  3. list disk
    select disk X
    clean

    Cleanup the disk to get rid of macrium reflect error 9

    Disk cleanup
  4. Restart your computer and check if the issue is resolved.

Solution 3: Run CHKDSK Utility for terminating macrium reflect error 9

Running the CHKDSK utility has been reported as the most efficient solution to error 9. Follow the steps given below to perform this task.

  1. Click the search button in the taskbar and type Command Prompt.
  2. Right-click on it and click Run as administrator.
    Right click on cmd and choose first option to resolve macrium reflect error 9
    Clicking on “Run as Administrator”
  3. Enter the following command and hit enter to execute it. (Note that X represents the letter of your source drive)
  4.  chkdsk X: /f /r

    Run chkdsk to solve macrium reflect error 9 issue

    Running chkdsk
  5. Restart your PC and see if the error occurs again.

Solution 4: Create Image instead of Cloning

If you still can’t get rid of the error 9, try to make a disk image with Macrium Reflect. Follow the steps below to create this image and check if the error is resolved.

  1. Open Macrium and wait while it populates all the drives connected.
  2. Now select the drive which you want to image.
    Select the drive
    Select disk
  3. Near the bottom bar, click Image this disk.
    Click on the option Image this disk
    Image this disk
  4. Now click the browse button and select aa location to create this image.
  5. Select OK, then select Next and then select None when it asks to choose a template.
  6. Now press Finish.
    Click finish to terminate macrium reflect error 9
    Finishing up

Solution 5: Ignore Bad Sectors

If macrium reflect error 9 appears on the screen while you are creating the image, try to ignore the bad sectors to resolve this issue. Follow the steps given below:

  1. Open Macrium.
  2. At the top of the screen, click on Advanced.
    Click on the Advanced option
    Advanced
  3. Now on the left pane, click on Advanced Backup Options.
    Click on Advanced Backup Options to get rid of macrium reflect error 9
    Advanced Backup Options
  4. Now check the box parallel to Ignore bad sectors when creating images.
    Ignore bad sectors so that macrium reflect error 9 could be resolved
    Ignore bad sectors when creating images
  5. Now press OK.

Solution 6: Use EaseUS

If none of the solutions explained above works, try to use another third-party software to carry your task out.

  1. Download EaseUS from your favorite browser.
  2. Install the tool by following the on-screen instructions and launch it.
    Start the EaseUS tool
    Launch the tool
  3. Select the partition that you want to clone.
    Select the partition that you want to clone
    Select the partition
  4. Now select the destination disk to save your clone.
  5. Click Proceed.
    Click proceed to terminate macrium reflect error 9
    Proceed

If you need further assistance, contact here.

Photo of Alan Adams

Alan is a hardcore tech enthusiast that lives and breathes tech. When he is not indulged in playing the latest video games, he helps users with technical problems that they might run into. Alan is a Computer Science Graduate with a Masters in Data Science.

You are trying to clone or backup a drive using the Macruim Reflect tool, but you encountered an error Clone Failed – Error 9 that prevents you from cloning your drive.

Sounds familiar, right?

There is no need to worry about it if you are in such a situation.

As a tech expert and enthusiast, I researched and tested solutions to solve Macruim Reflect errors during cloning or backup. Here, you will learn some of the best practical solutions to solve your Macruim Reflect clone failed error 9.

Are you looking for the right and effective solution to your problem?

Sit tight, keep reading and precisely follow the instructions to solve your problem within a few minutes.

Let’s get started.fix-macrium-reflect-error-9

Follow our guide on how to Fix the Teredo Error on Xbox

Reasons for Macrium Reflect Error 9 Issue

The Macrium Reflect clone error 9 occurs during the cloning or backup because of the improper cable connection setup, damage or faulty cable connection, conflicting third-party antivirus software, corrupted disk file system, or bad storage sectors. To solve the problem, fix these issues.

The Macrium Reflect clone failed error issue 9 might happen at any time. A variety of factors might cause the failure of a Macrium Reflect.

This section will discuss some of the common potential reasons preventing cloning or backup your drive.

Here are some common reasons for the Macrium Reflect error 9:

Connectivity Issue

One of the most typical causes of the Macrium Reflects clone failed error on your Windows system is a problem with connectivity.

During the drive cloning or backup process, faulty or damaged connectivity issues also cause the clone failed error. To resolve your problem, you must first check and correct your connection.

Read more on how to Fix Square Enix Error code i2501 FFXIV

Corrupted Disk Files System

The corrupted disk files system is one of the most prevalent causes of your Windows system’s Macrium Reflects clone failed error. If the disk files get corrupted, your drive may become incompatible.

To fix the Macrium Reflects clone failed error on your Windows PC, you’ll need to repair or format your disk or drive.

Conflict Antivirus Applications

Another possible cause of the Macrium Reflects clone failed error on your Windows PC is a third-party antivirus program.

When antivirus software conflicts with Macrium Reflects tool, it might cause the Macrium Reflects drive clone failed error. Disabling or uninstalling the antivirus application can fix the error issue.

Storage Bad Sectors

If you have bad sectors on your drive, you could get a Macrium Reflect clone failed error on your Windows computer.

To solve the Macrium Reflects drive clone failed error on your Windows PC, ignore the bad sectors of the disk that are causing the problem when cloning the drive.

Check our latest post on how to Fix Minecraft Not Update Error

Macrium Reflect is a backup tool for Windows users that helps to clone and backup drives easily and quickly from one disk to another.

But, some Macrium Reflect users reported that they got the clone failed error message while trying to clone or backup a drive.

Are you annoyed and frustrated about your terrible situation and looking for the best solutions?

Don’t worry. This section will describe the most effective and proven solutions to the Macrium Reflect clone failed error.

To solve the error issue, keep reading and follow the instructions step by step.

Also read, how to Fix Friends Network Unreachable Error on Steam

Here are the steps to fix Macrium Reflect error 9:

1. Run CHKDSK Tool

CHKDSK tool is a helpful feature to scan and solve the drive or disk error issue on Windows system computers.

Using the CHKDSK program, you can check and repair the drive issues that create the Macrium Reflect clone failed error during the drive cloning or backup.

Here are the steps to run the CHKDSK tool:

Check our exclusive tutorial on How to fix blue screen on Windows 11

2. Clean your Drive

Cleaning your error source disk may help you solve your specific error problem on your Windows computer.

So, to solve your Macrium Reflect clone failed error 9, you can try to run a disk cleanup on your targeted disk.

Here are the steps to clean your disk:

Check out our separate post to change power mode on Windows 11

3. Uninstall Third-party Antivirus Application

Antivirus application is another cause of Macrium Reflect clone failed error during the drive cloning or backup.

Using a third-party antivirus application on your system might conflict with the different system programs, creating various error issues. For the same reason, when your antivirus application conflict with the Macrium Reflect tool, it can generate an error issue.

So, to solve the problem, you need to disable or uninstall the third-party antivirus software to solve the issue.

Here are the steps to uninstall the antivirus application: 

  1. Open the Start menu and click on the Settings icon under the pinned apps to open Windows Settings. Or, windows-11-settings
  2. Press the Windows Key + I on your keyboard to open the Windows Settings App. Windows-system-settings
  3. Select the Apps tab on the left side settings menu panel.
  4. Select the Apps & features right side screen. apps-features-option-at-the-to
  5. Scroll down and find your installed antivirus application.
  6. Click on the three-dot menu and select the Uninstall button.
  7. Click on the Uninstall button to confirm to uninstall the app.bitdefende-antivirus-uninstall
  8. Wait some time to complete the process.
  9. Retry to clone or backup your drive to see whether your problem is solved or not. If not, follow the next solution.

Follow our guide to Fix update error 8024402F on Windows 11

4. Create Image Instead of Cloning

If the previous solution does not solve your problem, try using Macrium Reflect to create a disk image. Many users can resolve the Macrium Reflect error issue by using this method.

Here are the steps to create an image instead of cloning:

  • Open your Macrium Reflect
  • Select the drive or disk that you want to create an image.
  • Click Image this disk link at the bottom of the window.
  • Click the browse
  • Select a location to start the image you want.
  • Click on the OK
  • Select Next to go forward.
  • Choose None as a template.
  • Click on the Finish button to end the image-creating process.

5. Ignore the Bad Sectors

You can ignore the bad sectors when creating the images to solve your Macrium Reflect clone failed error 9. To do this, you need to enable the options on the Macrium Reflect application.

Here are the steps to enable the ignore the bad sectors option:

  • Open your Macrium Reflect
  • Click on the Advanced option at the top of the menu bar.
  • Click on the Advanced Backup Options on the left-side pane.
  • Check the Ignore the bad sectors when creating the images box to enable the option.
  • Click on the OK button to apply the changes.

Check out the easiest way to Fix Netflix Error Code NW-1-19

Final Thoughts

The Macrium Reflect clone failed error issue might happen at any time. After analyzing the problem, I discovered some possible reasons for the Macrium Reflect clone error.

Here I discuss the possible reasons for the Macrium Reflect clone failed error issue. I also demonstrate the best proven and practical methods to fix your Macrium Reflect clone failed error issue on your Windows computer.

You can successfully solve your problem quickly by applying these proven and tested methods. If you find a solution, please let me know which strategy worked for you.

I hope this article is beneficial for you. If you’re interested in learning more about similar topics, you can also browse other posts.

How to fix Macrium Reflect Error 9 during backup

Macrium Reflect is image based backup utility for Microsoft Windows. The tool is easy to use and offers a solid performance; however, recently many users encountered an error while trying to clone their drive. The error reads “Clone failed – Error 9” and it prevents you from cloning your drive.

The error 9 in Macrium Reflect can appear for a number of reasons. These include improper cable connection, conflict with your antivirus software, file system error, etc. In this post, we look at different methods to solve this issue. So let’s get started!

How to fix Macrium Reflect Error 9 during backup

Are you receiving the error 9 in Macrium Reflect? Don’t worry. Here are some effective ways to get rid of this issue in no time.

  1. Check your connection
  2. Disable third-party antivirus software
  3. Clean the Target Disk
  4. Run CHKDSK Utility
  5. Ignore Bad Sectors
  6. Create Image instead of Cloning

Fix 1 – Check your connections

If you encounter the error 9, the first thing to do is check the physical connection between both the drives. In most cases, the drive is not connected properly causing the problem. Also, try to replace the connecting cable because the cable might be damaged easily if used excessively.

Fix 2 – Disable third-party antivirus software

Antivirus software aims to protect your computer from malware and cyber threats, but sometimes, it can block some features of the system. This can lead to error 9 in Macrium Reflect. To fix this error, you should turn off your third-party antivirus and reboot the system to see if it helps.

Fix 3 – Clean the Target Disk

If the error continues to occur, you can run a disk cleanup of the destination disk to fix the issue. Here is how to proceed:

1) Type “diskpart” in the Windows search bar and click to open it.

2) Click Yes if you’re prompted for permission.

3) Input the following commands one by one and hit Enter on each:

list disk
select disk X
clean

Note: The X in the above commands represents the number of your Target drive.

Macrium Reflect Error 9 (Fix #3)

4) When the process is finishes, restart your computer and check if the issue has been resolved.

Fix 4 – Run CHKDSK Utility

Running the CHKDSK utility has fixed the macrium reflect error 9 for many users. Follow the steps below to carry this task out:

1) Type “cmd” in the Windows search bar, then right-click on the Command Prompt result and select Run as administrator.

2) Click Yes if you’re prompted for permission.

3) In the Command Prompt window, input the following command and hit Enter to execute it:

chkdsk X: /f /r

Note: The X in the above commands represents the number of your Target drive.

Run CHKDSK Utility

4) Restart your computer and check to see if you still encounter the error.

Fix 5 – Create Image instead of Cloning

You can try making a disk image with Macrium Reflect to avoid the error 9. Here’s how to do it:

1) Open Macrium and wait for it to populate all the drives connected.

2) Select the drive you want to create an image of.

3) Click Image this disk…

4) Select a location to create this image, then click OK > Next.

5) Select None when it asks to choose a template.

6) Finally, hit the Finish button.

Fix 6 – Ignore Bad Sectors

If you receive the error 9 while creating the image, try to ignore the bad sectors to fix this issue.

1) Open Macrium and click on Advanced in the top menu.

2) On the left pane, click on Advanced Backup Options.

3) Check the box for Ignore bad sectors when creating images.

4) Click OK to save the changes.


We hope this post helped you fix the error 9 in Macrium Reflect. If not, you can tell us your concern in the comments below, and we’ll do what we can to help.

READ NEXT

  • [2020 FIX] GeForce Experience Error Code 0x0001
  • Fixed: Digital TV Tuner Device Registration Application Issue

Как исправить ошибку «Ошибка клонирования Macrium» - Направляющие

Как исправить ошибку «Ошибка клонирования Macrium» — Направляющие

Содержание

  • Что вызывает ошибку «Macrium Reflect Clone failed»?
  • Как исправить ошибку «Отражение клона Macrium не удалось»?

Macrium Reflect — это программа для создания образов дисков и резервного копирования для Microsoft Windows, которая создает резервные копии и образы с помощью службы Microsoft Volume Shadow Copy Service. Он выполняет резервное копирование и репликацию (клонирование) целых разделов на другой накопитель одним нажатием кнопки.

Сообщение об ошибке «Не удалось отразить клон Macrium”- очень распространенная ошибка, которая возникает, в частности, при клонировании жесткого диска на твердотельный накопитель. Причины этого сообщения об ошибке очень разнообразны и варьируются от проблем с антивирусом до поврежденных секторов на диске.

Что вызывает ошибку «Macrium Reflect Clone failed»?

Как упоминалось ранее, это сообщение об ошибке может появиться по разным причинам. Некоторые из них перечислены ниже:

  • В связь между приводом и компьютером не правильно. Плохой соединительный кабель может нарушить процесс клонирования устройства хранения.
  • На запоминающем устройстве есть плохие сектора. Программное обеспечение обычно возвращает сообщение об ошибке, когда обнаруживает поврежденные сектора во время клонирования.
  • В антивирус программное обеспечение не позволяет Macrium клонировать диск. Это очень распространенная практика, когда антивирусное программное обеспечение блокирует любую попытку доступа к диску в течение продолжительных периодов времени.

Пользователи, столкнувшиеся с этой проблемой, сообщают, что они получают различные сообщения об ошибках, такие как «доступ запрещен» или «невозможно сопоставить раздел». Это сообщение об ошибке обычно также сопровождается цифрами ошибки, такими как «ошибка 9», «ошибка 0» и т. Д. В редких случаях, если разрешения установлены неправильно, может появиться сообщение «чтение не выполнено 13, разрешение отклонено 32» или « write failed 22 invalid argument ‘вместе с исходной строкой ошибки.

Перечисленные ниже решения направлены на все эти проблемы. Убедитесь, что у вас есть активное подключение к Интернету и вы вошли в систему как администратор.

Проверьте диск на наличие плохих секторов

Плохой сектор — это сектор на запоминающем устройстве, который недоступен для любого программного обеспечения из-за необратимого повреждения. Плохие секторы постоянно присутствуют на устройстве хранения. Чтобы противостоять этому, операционная система помечает эти сектора, чтобы они могли пропустить их при обычных операциях. Если у вас есть поврежденные сектора, вы должны запустить утилиту «chkdsk», чтобы убедиться, что они не нарушают процесс клонирования.

  1. Нажмите Windows + S, введите «командная строка»В диалоговом окне щелкните приложение правой кнопкой мыши и выберите«Запустить от имени администратора”.
  2. В командной строке с повышенными привилегиями выполните следующую команду:

chkdsk / r

  1. Если вам будет предложено проверить после перезагрузки, нажмите «y» и перезагрузите компьютер. После перезапуска chkdsk уже будет запланирован операционной системой, и будет выполнено сканирование. Наберитесь терпения и позвольте процессу.
  2. После того, как утилита просканировала и удалила поврежденные сектора из обычного доступа, попробуйте снова клонировать устройство хранения.

Очистить целевой диск

Если на целевом диске повреждена файловая система, Macrium не сможет клонировать ее. Поврежденные файловые системы тоже не редкость и обычно возникают из-за логических ошибок. Мы можем использовать утилиту diskpart, чтобы очистить структуру целевого диска и посмотреть, решит ли это проблему.

  1. Нажмите Windows + R, введите «командная строка»В диалоговом окне щелкните приложение правой кнопкой мыши и выберите«Запустить от имени администратора”.
  2. В командной строке выполните следующие команды одну за другой по порядку.

diskpart list disk select disk [номер целевого диска] очистить все

  1. После восстановления файловой структуры перезагрузите компьютер, убедитесь, что оба диска подключены правильно, и попробуйте клонировать снова.

Попробуйте отключить антивирус

Как упоминалось ранее, антивирусное программное обеспечение блокирует доступ к любой программе, которую они считают подозрительной в заражении компьютерной системы. Если процесс клонирования заблокирован антивирусом, вы можете получить сообщение об ошибке «Доступ запрещен» вместе с кодом ошибки.

Чтобы противостоять этой ситуации, вы можете отключи свой антивирус ПО полностью, а затем повторите попытку клонирования. Если на вашем рабочем столе установлено несколько антивирусных программ, сделайте то же самое для всех. Как только вы будете абсолютно уверены, что никакой антивирус не контролирует ваш компьютер, попробуйте снова запустить процесс клонирования.

Создать образ вместо клонирования

Если у вас возникли проблемы с клонированием нашего жесткого диска, вы можете попробовать создать его образ. Между этими двумя процессами есть небольшие различия. Клонирование диска — это процедура копирования всего содержимого одного диска на другой, которая включает в себя всю информацию, необходимую для загрузки операционной системы с диска. Он создает индивидуальную копию жесткого диска, и эти жесткие диски могут быть заменены друг на друга также после процесса клонирования.

Создание образа диска — это процесс создания резервной копии содержимого жесткого диска. Образ диска — это тип файлов хранилища, который содержит все данные и информацию, необходимую для загрузки операционной системы. Однако образ диска должен быть применяется для того, чтобы жесткий диск работал.

Здесь мы опишем процедуру создания образа вашего диска вместо клонирования.

  1. Откройте Macrium и дайте ему заполнить все подключенные диски. затем выберите диск который ты хочешь образ и нажмите Изображение этого диска присутствует внизу.

  1. Теперь щелкните кнопка просмотра и выберите расположение где вы хотите создать изображение. Нажмите хорошо когда вы выбрали место.

  1. Выбрать далее. Теперь вы можете выбрать шаблон для своей резервной копии. Если вы не знаете, что это, нажмите Никто.

  1. Нажмите финиш и начнется создание вашего образа. Терпеливо дождитесь завершения процесса.

Игнорировать плохие сектора

Если вы получаете такое же сообщение об ошибке при создании образа, вы можете попробовать игнорировать поврежденные секторы при создании образа. Обычно, следуя решению 1, все сбойные секторы удаляются из логической памяти. Но если есть какие-то проблемы, которые все еще вызывают проблемы, это может решить проблему.

  1. открыто Макриум и нажмите на Продвинутый из верхней части экрана.
  2. Сейчас чек коробка Игнорировать плохие сектора при создании образов.

  1. Нажмите хорошо для сохранения изменений и выхода. Теперь попробуйте снова создать изображение.

Проверьте подключение привода

Прежде чем вы начнете использовать сторонние альтернативы, вам следует проверить правильность физического соединения между обоими вашими дисками. Если вы подключаете SSD через порт USB, попробуйте подключить его к материнской плате и повторите попытку клонирования.

Измените соединение SATA для жесткого диска и, если возможно, попробуйте заменить кабель. Кабели можно легко повредить, и из-за них процесс клонирования может быть нарушен. Как только вы убедитесь, что обе, целевой и целевой диски подключены правильно, продолжайте процесс клонирования.

Попробуйте сторонние альтернативы

Если все вышеперечисленные методы не работают для вас, вы можете рассмотреть возможность использования другого альтернативного программного обеспечения. Согласно нашему исследованию, было множество случаев, когда Macrium выдавал ошибку, в то время как другое программное обеспечение, такое как AOMEI отлично справился со своей работой.

Для информации пользователя мы рекомендуем программное обеспечение AOMEI. Вы можете скачать программный модуль с официального сайта и попробовать клонировать с него свой диск.

Примечание: Appuals не имеет отношения к какому-либо программному обеспечению. Все рекомендованное программное обеспечение предназначено исключительно для информации читателя.

[SOLVED] Error 9 and error 23 when cloning using Macrium Reflect


  • Thread starter

    blane1257


  • Start date

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

  • #1

I’m trying to clone my hard drive to a new SSD but I keep getting the errors. I tried enabling ignore bad sectors in advanced settings and running chkdsk, I don’t really know what else to do.

USAFRet


  • USAFRet

    USAFRet

Sorry, but no.
Imaging in Macrium is not «just copies the files». It attempts to read all (actually most) of the data. NOT just discreet «files».

Yes, Cloning is different than Imaging.
But it is not a simple file copy function.

In any case, it is attempting to read from or through portions of the platter that are failed/failing. And trying again and again and again.
And telling you exactly why, with Error 9 and Error 32.

Hence, the extensive time it says it will take.

You might try changing from Intelligent Sector Copy (default) to Forensic Copy.
That might force through the failed portions of this drive.

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #2

Error 9 is «read failed».
If the source disk is faulty, cloning is not a good way forward. The drive is too far gone.

Unless of course, this is a police investigation and you’re trying to do some deep forensics.

  • #3

the source disk is my boot disk and I don’t want to reinstall windows or anything like that

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #4

the source disk is my boot disk and I don’t want to reinstall windows or anything like that

At this point, you don’t seem to have a choice.

Cloning can be great, in optimal conditions. This is not optimal.
Your source drive is failing. Too far gone to read all the way through.

  • #5

okay, I’m imaging my disk now, but the ETA has been sticking at 3000-4000 hours, which really doesn’t seem right.. both drives are plugged straight into my motherboard via SATA, but even if i was copying from an external USB 2.0 drive I don’t think it should take more than ~8 hours, definitely not a few months

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #6

okay, I’m imaging my disk now, but the ETA has been sticking at 3000-4000 hours, which really doesn’t seem right.. both drives are plugged straight into my motherboard via SATA, but even if i was copying from an external USB 2.0 drive I don’t think it should take more than ~8 hours, definitely not a few months

It is telling you «3000-4000 hours», because it is attempting to read the failed sectors again and again and again. And failing to do so.

This is too far gone to clone or image.

  • #7

the disk boots, it reads and writes just fine, and the progress bar is moving forward, just very slowly

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #8

the disk boots, it reads and writes just fine, and the progress bar is moving forward, just very slowly

And yet imaging and cloning fails.
The failed sectors are in other parts of the platters.

  • #9

in case youre somehow unaware, imaging won’t even attempt to copy failed sectors because it doesn’t make an exact copy, it just copies the files.

please work with me a little here, you’ve been very dismissive from the start

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #10

Sorry, but no.
Imaging in Macrium is not «just copies the files». It attempts to read all (actually most) of the data. NOT just discreet «files».

Yes, Cloning is different than Imaging.
But it is not a simple file copy function.

In any case, it is attempting to read from or through portions of the platter that are failed/failing. And trying again and again and again.
And telling you exactly why, with Error 9 and Error 32.

Hence, the extensive time it says it will take.

You might try changing from Intelligent Sector Copy (default) to Forensic Copy.
That might force through the failed portions of this drive.

  • #11

thanks for suggesting a course of action, I’ll try that when I get back to my PC.

what has me going is that when cloning it would encounter the errors and just fail, but when imaging, theres no error readout and it doesn’t stop imaging, and theres also no point when it transitions from making progress quickly to suddenly slowing down, its just as slow right from the start — so it really seems like an issue to do with data transmission speeds, but I don’t think even the slowests SATA disks out there would take 5 whole months to read ~400gb of data

USAFRet



Mar 16, 2013


166,443


15,511


184,590


  • #12

It’s not transmission speed, it is inability to read and try try again speed.
That amount of data should take no more than an hour or so.

drtweak



Sep 17, 2012


6,331


62


38,640


  • #13

In my experience, and I have been using Macrium for quite a few years now. at least 6 or 7, if a drive any any bad sectors or too many reallocated sector counts it will almost always fail. Now if by chance there is no data for it to read where the bad sector is then you might get lucky.

Cloning and Imaging both are the same the only difference is the target area. The source is the same and what it has to read is exactly the same.

You need something more like R-Studio. That is what I use for drives with bad sectors. Only thing is you have to do a 1:1 copy which means you have to clone it to a drive of the same exact size or larger. Once it is cloned over to a good drive you can then use macrium to clone it to a different drive if the new target drive is smaller. if it is the same size or larger you don’t need to use macrium.

Also this whole Slow thing is NOT a data speed issue. That hard drive is trying to read and read and read and it can’t. Macrium doesn’t know how to properly skip bad sectors.

  • #14

thank you, I’ll try R-studio, the target drive is the same size so no hassle there.

I knew it wasn’t a data speed issue, I was just kindof sharing my line of thoughts, I guess I didn’t make it very clear that I was dismissing that as being the problem

  • #15

I tried R-drive with limited success, it seemed like R-drive was fighting windows for resources so I tried clonezilla in rescue mode, which I think would have worked but around the 18-20 hour mark, just a couple hours before it should finish, it would reset the progress back to 0, and there were also some GUI glitches so I probably just had a defective or corrupt version of clonezilla or something like that, but windows was starting to act up a bit and be a little glitchy so I decided it would probably be best to start fresh and just install windows onto the SSD.



Sep 22, 2010


8,981


644


36,390


  • #16

Ddrescue and HDDSuperClone both understand how to clone a drive with bad heads or media. They are the DIY tools recommended by data recovery professionals.

CHKDSK is a very bad tool to run against a failing drive. It is data destructive in such cases.

SkyNetRising



Jan 4, 2016


28,019


3,232


111,640


  • #17

I tried R-drive with limited success

Can you show SMART data for your failing drive? Use HDtune health.
(upload to imgur.com and post link)

  • #18

I’ve given up cloning my disk and already installed windows on the new disk

Similar threads

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions

Понравилась статья? Поделить с друзьями:
  • M2shared cpp ошибка вов
  • Macrium reflect код ошибки 9
  • Love exe move or die ошибка
  • M2535dn ошибка f375
  • Mach3 ошибка 9991