Macrium Reflect Code Error 21

joantonio98

New Member
Joined
Nov 1, 2024
Messages
1
Hello guys, I have a problem with the Macrium Reflect. I want to clone my SSD to a new large SSD but I always obtain this error code: "Clone failed-Error 0-Unable to match partition - Drive 1, Start Sector 3997900800-Cluster Run Error. Cluster Run short- Error code=21. Please run 'chkdsk :/r'


I checked many tutorials and read some forums but no one works and I don't know If I doing well. I know the problem is related with FAT32, so I change the volumen name of that because it didn't have a name, but after a rebooting my laptop the variable I setted dissapear and still unnamed the FAT 32. So if you guys have a solution I'll gladly with you.

Best Regards,
Clone_english.webp
clone_english_2.webp
clone_english_3.webp
 


Solution
It looks like you're experiencing a frustrating issue with Macrium Reflect related to error code 21 while trying to clone your SSD. Let’s break down the situation and explore some potential solutions.

Error Explanation​

The error message "Clone failed - Error 0 - Unable to match partition - Drive 1, Start Sector 3997900800 - Cluster Run Error. Cluster Run short - Error code=21" typically indicates that there's a problem with how the source and destination drives are aligned or formatted.

Image Analysis Insights​

The images you attached show log entries from the cloning operation:
  • First Image: Details about the source and destination disks are provided, which include a GPT formatted source disk and an MBR formatted...
It looks like you're experiencing a frustrating issue with Macrium Reflect related to error code 21 while trying to clone your SSD. Let’s break down the situation and explore some potential solutions.

Error Explanation​

The error message "Clone failed - Error 0 - Unable to match partition - Drive 1, Start Sector 3997900800 - Cluster Run Error. Cluster Run short - Error code=21" typically indicates that there's a problem with how the source and destination drives are aligned or formatted.

Image Analysis Insights​

The images you attached show log entries from the cloning operation:
  • First Image: Details about the source and destination disks are provided, which include a GPT formatted source disk and an MBR formatted destination. This mismatch could be a reason for the errors.
  • Second Image: It illustrates the software's operation attempting to copy a FAT32 partition (ESP).
  • Third Image: It reiterates the error about cloning failure, urging a disk check with chkdsk /r.

Suggested Solutions​

  1. Check Disk Healthy:
    • Run chkdsk /r on both the source and target drives. This command will identify and fix file system issues on the disk that might be causing the cloning to fail.
  2. Align Disk Formats:
    • Ensure that both the source and destination disks are using the same partitioning style (either both GPT or both MBR). You can use Windows Disk Management or third-party tools to convert your disks as needed. Keep in mind that converting between MBR and GPT will require data backup as it often leads to data loss.
  3. Update Macrium Reflect:
    • Make sure that you are using the latest version of Macrium Reflect. Updates often include bug fixes and improved compatibility with different drive types and formats.
  4. Repartition:
    • If you're still facing issues, consider backing up any essential data and reformatting the destination drive, removing all existing partitions. This way, you can start the cloning process anew with a clean slate.
  5. Review Fat32 Configuration:
    • You mentioned an issue with the FAT32 volume name disappearing. Ensure that the disk is properly configured, and use Disk Management to format it if necessary.

Additional Considerations​

  • Trial Mode: The second image indicated that you are currently using a trial mode of Macrium Reflect. Make sure to consider potential limitations in the trial, as some features might be restricted.
  • Backup Important Data: Always ensure that important data is backed up before making significant changes to disk configurations or attempting cloning processes.
If you've tried these solutions and are still encountering issues, please share any further details or symptoms that may help us troubleshoot the problem more effectively. Best of luck, and feel free to reach out with more questions or updates!
 


Solution
Back
Top