Had an error in Macrium Backup as seen in attached image. Have run Macrium many times successfully. Only differences are a new update to Macrium and using a Seagate SSHD (hybrid drive).
I did a defrag and re-ran Macrium with no success. Macrium forums are no help. There was a post with same symptoms but the reply indicated the tech. had replied with an emailed solution. Here is a link to that post.
I have run a Windows backup successfully on the same partition.
Have you tried a clean boot and then de-frag?
Have you tried a third party defrag tool?
Not exactly sure what you mean by 'clean boot'.
I used Windows defrag and JKDefrag. It was an old version. There is a new version I think I'll try that and then try Macrium again.
Funny that Windows backup worked.
OK. I downloaded latest version of JKDefrag now called Mydefrag. Did a boot and tried Macrium. Same error.
if you are using the paid version of Macrium, fill out a support request. I have done that a couple of times and always find their support people extremely helpful.
That's the problem Dick. I'm using the free version. No support.
Originally Posted by Dick-Y
What's really weird about this is the recommendation to run windows defrag, which doesn't defrag the bitmap.
I even tried the sysinternals contig program but it gave an access error, like I wasn't allowed. Was running as the real Administrator acct.
See How to perform a clean boot in Windows for details on performing a clean boot. That just means you'll load as little as possible at boot time.
When I try Contig just to analyze the MFT I get access denied when I use $Bitmap but when I just specify $MFT Contig analyzes both $MFT & $MFT:$Bitmap successfully. Which did you try?
I tried $bitmap. Will go try $MFT.
Originally Posted by JoeP517
Just tried contig -v -s $mft here is the result.
Macrium still wont work. contig says bitmap not fragmented.
BTW thanks for the link on Clean Boot.
Just a wild shot - but how much space is available on the drive you are putting the image on? (I'm also assuming that K: is a separate HD.) A system error code of 8 is not enough memory. So, it could be that you don't have enough space on the destination drive or that the fragmented system bitmap is not on C: but is on K:.
There was lots of space on the drive when I first tried this. I even defragged the drive and tried again. No luck. Based on when the error occurs I'm fairly certain that it's referring to the source because of the part of the process at which it fails. And Windows image had no issues.
Originally Posted by RaggedyMan
Downloaded Perfect Disk Trial. Ran defrag and boot defrag.
Macrium still gives the same error.
I had a different kind of problem recently with my W7 SP1 Home Premium system. After trying different helpful suggestions, and things I came up with myself . . . I still had the problem, and I had invested days in trying to fix the problem.
I finally "bit the bullet" and did a clean re-install. No more problem.
I also benefited in doing this by creating a "gold standard" image of my clean system, with my programs installed, and my tweaks applied. I have saved this image on my hard-drive that I use for imaging; and created that same 'gold standard" image on an external drive that I also use for imaging.
With that saved "gold standard" image I should never have to do a clean reinstall again (knock wood).
Maybe you should think of doing the same clean reinstall . . .
see next post. Sorry about double post.
Sorry Dick but that ain't gonna happen.
I'm old school. I like to know what caused the problem. Need to know the root cause.
I've uninstalled Macrium 5.2.6465 and installed 5.2.6437. Still get same error.
Also can image other drives with all versions.
Looks like some issue with the Hybrid drive. It's the only thing I can think of that has changed. I only wish I could be certain that the bitmap isn't actually fragmented.
Another possibility may be the method used to move my system from my 1 TB WD Black to the 2 TB Seagate SSHD. I use BING as a Boot and Partition manager. I used their Copywipe program to copy from the 1 TB drive to the 2 TB drive. I kept the same partition sizes and later expanded the partition using BING.
BTW I did a clean boot and tried. Same result.
Restore a previous image that does not include the "new update".