Macrium Reflect Clone Failed Read Failed 13 Permission Denied

	Message
Tim David	Tim David posted 14 March 2018 3:27 PM Respond
New Member Grouping: Forum Members Posts: 13, Visits: fourteen	I am trying to clone a hard drive and it gets approximately 3% into the chore and fails with "Read failure - 13; Permissions Denied - 32".  Does anyone have some ideas I can try? Cheers.
	Reply Like 0
jphughan	jphughan posted 14 March 2018 iii:46 PM ANSWER
Macrium Evangelist Group: Forum Members Posts: 11K, Visits: 69K	+ x I am trying to clone a hard drive and it gets approximately 3% into the task and fails with "Read failure - xiii; Permissions Denied - 32".  Does anyone have some ideas I tin try? Give thanks you. If memory serves, permissions denied can be caused by interference from third-political party anti-virus if y'all're running whatsoever.  You lot can try disabling that, or if that doesn't work (some anti-virus solutions don't allow themselves to be completely disabled even when they say they are), then if this is just a one-off clone in order to migrate onto a new drive, it might be easier to just perform the clone from the Rescue Media surround since that of form won't take anti-virus running.  If that doesn't solve the issue, you could as well run CHKDSK with the /R switch against whatever segmentation Reflect was working on when that error occurred, but that can take quite a long time if the partition is big.  Also note that if Reflect was working on a partitioning that does not accept a bulldoze letter assigned by default, yous'll need to temporarily assign that partition a drive letter of the alphabet using the congenital-in diskpart tool in guild to target information technology with CHKDSK. Edited 14 March 2018 3:48 PM past jphughan
	Reply Like 0
Tim David	Tim David posted fourteen March 2018 6:26 PM ANSWER
New Member Group: Forum Members Posts: 13, Visits: fourteen	+ ten + ten I am trying to clone a hard bulldoze and it gets approximately 3% into the job and fails with "Read failure - 13; Permissions Denied - 32".  Does anyone have some ideas I can effort? Thank you. If retention serves, permissions denied can be caused by interference from third-party anti-virus if you're running whatsoever.  You can endeavor disabling that, or if that doesn't work (some anti-virus solutions don't permit themselves to be completely disabled even when they say they are), then if this is just a one-off clone in lodge to drift onto a new drive, it might be easier to just perform the clone from the Rescue Media environment since that of course won't take anti-virus running.  If that doesn't solve the upshot, you could besides run CHKDSK with the /R switch against whatsoever partition Reflect was working on when that error occurred, but that tin accept quite a long time if the sectionalisation is large.  Also note that if Reverberate was working on a partition that does not accept a bulldoze alphabetic character assigned past default, you'll need to temporarily assign that partition a bulldoze letter using the built-in diskpart tool in order to target information technology with CHKDSK. Cheers very much.  I'll try the anti-virus solution and see if that works.
	Reply Like 0
Tim David	Tim David posted 15 March 2018 12:45 PM Reply
New Member Group: Forum Members Posts: 13, Visits: 14	+ x + ten I am trying to clone a difficult drive and it gets approximately three% into the job and fails with "Read failure - 13; Permissions Denied - 32".  Does anyone have some ideas I can try? Thank you. If memory serves, permissions denied can be caused by interference from third-party anti-virus if y'all're running whatever.  You can effort disabling that, or if that doesn't work (some anti-virus solutions don't allow themselves to be completely disabled even when they say they are), then if this is just a one-off clone in society to migrate onto a new bulldoze, it might be easier to only perform the clone from the Rescue Media environment since that of grade won't take anti-virus running.  If that doesn't solve the issue, you could as well run CHKDSK with the /R switch against any partitioning Reflect was working on when that error occurred, but that can take quite a long time if the sectionalisation is big.  Also note that if Reflect was working on a partition that does not have a drive letter assigned past default, you'll demand to temporarily assign that division a drive letter using the built-in diskpart tool in gild to target it with CHKDSK. Hi, I tried the Rescue Media method, considering I couldn't disable my anti virus.  The failure occurred at the same signal (iii%) for the same two reasons.  Read fail xiii and Permissions Denied 32.  I have a feeling it may be a physically damaged drive at this point.  The bulldoze is full deejay encrypted with Symantec Endpoint Encryption version 8.  I have previously had 100% success with cloning drives like this one using sector past sector cloning.  This is the merely i I have not been able to clone.  Give thanks yous for your assistance.  If you have any other ideas, please don't hesitate to throw them my way
	Answer Like 0
jphughan	jphughan posted 15 March 2018 1:21 PM Respond
Macrium Evangelist Group: Forum Members Posts: 11K, Visits: 69K	Are you using the latest version of Reverberate, and is your Rescue Media using the latest version of Reflect besides?  Version seven.i.2801, released dorsum in tardily Dec, included a gear up specifically for cloning/imaging partitions encrypted with that Symantec production.  Sorry if that's an obvious question, merely sometimes it turns out users are however using an old version of Reflect, and even if they've updated, sometimes they didn't update their Rescue environment.  The Reverberate version is shown in the championship bar along the height of the application window.  If you're running the latest version within "existent" Windows but not in the Rescue environment, pace through the Create Rescue Media wizard and click the Rebuild push button at the last step and then Next to update those files, or you may see an automated prompt to practice this, in which case click Continue and and so Adjacent. If that'southward non it, if you've been trying to perform a sector-by-sector clone while the sectionalisation is completely locked, would cloning the division while it is unlocked (not permanently decrypted, just unlocked) and then re-enabling encryption on the destination later on be an selection? Edited 17 March 2018 ii:59 PM by jphughan
	Reply Similar 0
Tim David	Tim David posted 17 March 2018 two:38 PM ANSWER
New Member Group: Forum Members Posts: thirteen, Visits: xiv	+ 10 Are you using the latest version of Reverberate, and is your Rescue Media using the latest version of Reflect as well?  Version 7.1.2801, released dorsum in late December, included a fix specifically for cloning/imaging partitions encrypted with that Symantec product.  Deplorable if that'south an obvious question, but sometimes it turns out users are still using an old version of Reflect, and fifty-fifty if they've updated.  The Reflect version is shown in the title bar forth the peak of the application window.  If you lot're running the latest version within "real" Windows but not in the Rescue environment, stride through the Create Rescue Media magician and click the Rebuild push button at the final pace so Side by side to update those files, or you may see an automated prompt to do this, in which case click Keep and so Next. If that's not it, if y'all've been trying to perform a sector-by-sector clone while the partition is completely locked, would cloning the partition while it is unlocked (not permanently decrypted, just unlocked) and then re-enabling encryption on the destination afterward be an option? I checked my version and information technology's 7.1 build 2917.  Glad yous thought to have me bank check.  The problem with doing the clone with the segmentation unlocked is that I tin't unlock it. The disk is declining to boot properly (the symantec pre-boot surroundings loads, Windows 7 begins to start, and then it blue screens, and immediate reboots the machine. There isn't even time to see what the blue screen says, it happens so fast.  Our field services people take the ability to decrypt the drives, merely in contempo incidents they have failed to become the decrypt to work, and have irreparably damaged the drive so badly that fifty-fifty a forensic team from NCIS was unable to recover the data.  My intent was to simply make a clone of the disk, and and so permit field services effort to decrypt, knowing that we had a fill-in copy of the deejay that we could give to a forensics squad to work on.  It appears that I won't be able to create that bit of insurance. So we may simply be stuck with rolling the dice. And I am non at all comfortable with that.  I am because asking my leadership to submit the bulldoze to NCIS instead of allowing field services to foul information technology.  Thank yous all for being so determined to observe me a solution.  You were able to assist me in the by, and really, I may have been the customer that caused y'all to come up with that Symantec set
	Reply Similar 0
jphughan	jphughan posted 17 March 2018 3:04 PM ANSWER
Macrium Evangelist Grouping: Forum Members Posts: 11K, Visits: 69K	I just realized I didn't finish a judgement in the original version of that previous post. I meant to say that even if people have updated, sometimes they didn't update their Rescue Media files, but it sounds like you've already checked that since that's the only environment you're working with at the moment. This is a long shot, but have you lot tried manually choosing Forensic Mode rather than the default intelligent sector copy? I'm betting Reverberate is already doing that anyway if the partition is locked, but it tin can't hurt to effort. Otherwise, Macrium may accept some ideas for you either here or if you submit a support ticket, which I would definitely do in your position if you lot don't hear back here since I can completely understand your reluctance to just roll the dice here. Good luck!
	Reply Like 0
SolihullRog	SolihullRog posted 5 August 2020 3:19 PM ANSWER
New Member Group: Forum Members Posts: 7, Visits: 29	SOLVED I know this is an old thread, but I just encountered it and solved it. I found two that my Macrium backup file had some sort of abuse.  It failed the validation test by Macrium rescue disc. Hope that helps.
	Reply Similar 0

powersafricastred.blogspot.com

Source: https://forum.macrium.com/22053/Clone-failing-with-error-13-and-error-32