Error doing macrium reflect backup

Page 2 of 2 FirstFirst 12

  1. Posts : 1,529
    windows 10 PRO
    Thread Starter

    Backed up to different HDD and stil failed sentinel quick check says all ok running dskchk c: / scan
      My Computer

  2. Posts : 43,182
    Win 10 Pro (22H2) (2nd PC is 22H2)

    Ok, suggests a source disk or hardware issue... does it occur when imaging only 1 particular partition?
      My Computers

  3. Posts : 1,529
    windows 10 PRO
    Thread Starter

    Will try backing just one partition of the C drive……going to try acronis backup see if I get an error, will also see if MR able to help thanks

    - - - Updated - - -

    Did a backup of the 2 small partitions on C drive and was ok

    - - - Updated - - -

    Any further thoughts please checked all internal cables don't know what else to try

    - - - Updated - - -

    Any further thoughts please checked all internal cables don't know what else to try
      My Computer

  4. Posts : 43,182
    Win 10 Pro (22H2) (2nd PC is 22H2)

    You mentioned 2 partitions are ok. Which does it fail on?

    From MR's forum:
    If your file system has non-contiguous cluster runs (unused gaps between clusters), then any bad sectors in the gaps will be missed by chkdsk (it will report no problems) but will cause the backup read to fail. Basically, there's a future problem with your disk and file system that's causing a backup error now. If there really are bad sectors then Macrium should have thrown an 'Error 23 - CRC Error' not '1117 - The request could not be performed because of an I/O device error', so it's possible that the disk isn't physically failing with bad sectors. Saying that, it clearly isn't possible to satisfy the block read when creating an image and the normal response would be to get a new disk and restore the most recent image.

    If you can manage to create an image using PE then you just might get a different outcome because VSS isn't involved and therefore there'll be a slightly different number of clusters included in the image. It really depends where the block is located that can't be read.
    b. Once you know which partition generates the error when being imaged:
    from MR's forum:
    Error Code 1117 IO error - Knowledgebase 8.0 - Macrium Reflect Knowledgebase
    Error code 1117 is generated by Windows operating system and is always caused by Input / Output (I/O) throughput issues with either the disk or the controller that it is attached to.

    To resolve this error check the partition for possible errors.

    Run an elevated MS-DOS command prompt

    At the command prompt type:
    chkdsk <volume drive letter> /r /f
    Note: A 'Read' error is generated by the image source disk and a 'Write' error is generated by the backup target disk.
    Please use the appropriate drive letter in the chkdsk command.

    If you receive the message Would you like to schedule this volume to be checked the next time your system restarts?
    Press 'Y' followed by Enter
    Your entire file system will be checked for errors. This may take some time to complete.
      My Computers


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:19.
Find Us

Windows 10 Forums