Cloning keeps failing on the faulty drive. Is there an option to tell Reflect to continue the cloning anyway? If not, what’s the best way to get the good parts onto a new drive?
In the absence of more detailed error information it seems most likely that you're dealing with some bad sectors on the failing drive. If so, rather than repeating unsuccessful attempts to clone it directly, I'd suggest following the steps in this KB article to create a backup image so that you will at least have a fallback that can be restored to the replacement drive. You may need to assign 'drive letters' to some of the source drive's 'unlettered' partitions in order to run chkdsk /r on all of them. If that doesn't work, you can then tell Reflect to ignore any bad sectors as that KB article explains.
Correct; still this error: Clone failed - Read failed - 13 - Permission denied - 32 Thank you for the pointer to that KB article; I will try an image instead of cloning on my next visit.
You're welcome and good luck. Following the procedure recommended in that KB article is the most likely solution. However, I'll offer one additional suggestion. If you've been trying to run the operation within your regular Windows working environment, try booting with your Reflect rescue media and create and restore the backup image to the replacement drive within that WinPE recovery environment instead. Doing it that way would eliminate any VSS involvement and some other possible problem sources such as "live AV" interference.
I already did the cloning using the WinPE image (as well as in the live OS) (and also had already run chkdsk d: /r), but we'll see (earliest next week) what happens when I'll try imaging instead.
I have many products used for personal and work (macrium reflect/acronis true image/acronis disk director/drive snapshot/shadow protect spx.. had a drive in work recently that was booting, (had some ancient bespoke software that no one knew how reinstall) it was working but really really slow (bad sectors) and it couldn't backup or clone using anything.. a quick google brought me to "EaseUS Todo Backup Free" - it had an option to skip bad sectors when cloning... drive successfully cloned in about 7 hours, booted fine on the new drive and its still working/booting/doing its job. i was shocked after having all these so called brilliant backup/clone tools that nothing could do it but some freebie stuff id never heard of could do it fine. https://www.easeus.com/todo-backup-resource/how-to-clone-a-drive-with-bad-sectors.html
@kC_: Thanks for mentioning that! I have purchased Acronis & Macrium software in the past, but might try this free EaseUS tool if those fail.
what are the consequences when skipping bad sectors? I can imagine if I just need to access some data on a failed or failing drive, then anything I can get is better than nothing. On the other hand could you actually rely on such a cloned drive afterwards or are you cloning something incomplete with some relevant info in those bad sectors missing, thus causing potentially other problems?
IMO it's the later. If I had image with potentially incomplete data, I would only use it to restore specific files and would not use it to restore whole system image.
Perhaps this is what is meant (half way down the page) https://knowledgebase.macrium.com/display/KNOW/Imaging disks with bad sectors
Yes, that is exactly what I meant to suggest in my reply: I pointed to the current Reflect v7 KB article rather than the v6 article, but they both say the same thing. In fact, if booted to Reflect's WinPE "rescue" environment as also suggested, I seem to recall that its backup imaging process ignores bad sectors by default, but cloning doesn't.
The KB article shows how to do it when running Reflect in the regular Windows working environment. There is no equivalent user selectable option for changing the default behaviour when running in the WinPE "rescue" environment ... or at least none that I've ever seen. Considering the occasional fallibility of my "old geezer" memory, I thought I should look for authoritative confirmation of my recollection about that default rescue environment behaviour and found it in this forum item posted by Nick Sills, Macrium's founder and senior honcho.
Yup. Personally, I'm waiting to see how well it will get along with the Win10 Fall Creators Update and its new feature list, especially its Controlled Folder Access and other security architecture updates. I suspect we may see an even longer list of "Various bug fixes and changes to improve Macrium Reflect" at that point.
This one's a "biggie" (i.e., a full re-installation, not just a patch) which means that, once again, you'll need to reselect the installation options that you want and deselect those that your don't want in the dialog box. http://virtech.org/temp/installopt.jpg
Ok, they seem to have done it again! I did this update and have 2 big issues! I am running 64 bit Windows 10 PRO and I can restart after this update, but NOT start after a shutdown power off. If I power on again, my BIOS comes up and when it tries to boot windows, it says no signal and has a black screen. Windows will not even try to load. I remember this same thing when they first started V7 and some of us had a dll issue they did not put into Windows. If I press power off on my desktop and restart all is OK. It is also OK if I boot from my Rescue media and then quit...it will load Windows OK...so what dll do I need to add back now and where? Also, I do backups to a SATA III drive I put into a SATA to SATA drive bay. When done I tell it to unmount the drive as it is OK in BIOS. Now it says it is in use and I can nor remove it! This used to work in 2619. The last time this happened it was mrcbt.sys that was not put into windows...let me explore. OH, the unable to unmount drive issue is also on the Mactium forum by someone else and he has proven it is this new Update...something I already knew!
Yes, there do appear to be some serious problems with this v7.1.2638 "bugfix" release and Macrium has been made aware of them as you also know having commented about them yourself in another user's thread in Macrium's own forum. Consider yourself lucky. It could have been much worse. Start-up problems with kernel mode drivers for device class filter services can make booting completely impossible, even in safe mode. Since you are able to boot your system into Windows, you could use the Control Panel "Programs and Features" to uninstall those "CBT" and "MIG" filter components temporarily if you wish while awaiting Macrium's next v7.1 "bugfix" for this v7.1 "bugfix". It's getting to be something like a tradition.
Thankfully I have stayed on V6 free (on secondary machine). I was waiting for the bugs to settle down, but now I think I'll definitely stick with V6. Hope the wheels aren't coming off at Paramount Software. Primary machine is also still paid V6.
