Macrium Reflect Backup Failures

Not Myself said:

There is a fair amount of information in the log files, none of which is meaningful to me; if it might be for others, I can see about posting it here.

I was wondering about that - could you post the end of the Macrium log file, say the last 20 or 30 entries before it failed?

So sticking with the theory that these reparse points with the unknown targets are the issue.

Not Myself said:

Code:

 * Reparse Point/Junctions Found (Most likely legitimate)!
     * C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll => <Unknown Target> [File]
     * C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.14393.0_none_f05abb1521a8c58e\bcdeditai.dll => <Unknown Target> [File]
     * C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.14393.0_none_f05abb1521a8c58e\ConfigureIEOptionalComponentsAI.dll => <Unknown Target> [File]
etc. etc.

I wonder if fsutil may be able to help with the reparse points.

I would navigate in File Explorer to the first folder (C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd) and using Option 7 in the tutorial to open an elavated command prompt.

Then run the fsutil command for the first file in the list.

Code:

fsutil reparsepoint query C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll

What does it say?

Another tool which might help is Junction, from Microsoft's Sysinternals

A similar enquiry to the above with fsutil would be to download Junction, unzip it to, for instance, c:\sysinternals
Then run

Code:

c:\sysinternals\junction.exe C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll

... and post back what it says.

But do this first though:

simrick said:

I am thinking, before we do anything else, you could boot from the Macrium Rescue Media, and image and verify your entire hard drive to an external drive. That will work, since it will be totally free of the operating system in that manner. Then proceed with next steps.

simrick said:

Here is a tut on how to read the results of a chkdsk. It would be good if you could post the results here (a screenshot or two would be fine).
Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums



Depending on what your results were, we might want to run this again.

This is getting (or, more accurately, already is) complicated, along with the rest of everything. Yesterday, for example, I received a package, which contained a new front panel for my computer; what it was supposed to contain was a new USB module for the front panel, as the tech who handled my call, after some serious testing, decided that the fault was a hardware one. When I called back, the tech who answered the call was quite amused; a lower-weight package, presumably containing the proper part, was loaded on the truck for FedEx delivery just over an hour ago.

Anyway, on the subject, here is a screen shot; notice that Chkdsk does not have any logs in the top window, quite unlike the tutorial's images:

DavidY said:

I was wondering about that - could you post the end of the Macrium log file, say the last 20 or 30 entries before it failed?

I started using Macrium 06Aug2016, to replace AOMEI, which had started to give me no-longer remembered problems; that was somewhat ironic, as I had installed AOMEI on my previous computer when Macrium gave me problems. Backupper was transferred from the old to the new machine, so I continued to use it.

Thus, I have good logs for eleven days. You ask for "the end of the log file": What do you mean by that?

It has been many years since I last studied mathematics, so I don't know if posting what it is that you want would be a form of "log-arithms".

Not Myself said:

Thus, I have good logs for eleven days. You ask for "the end of the log file": What do you mean by that?

Ah maybe I wasn't totally clear as it's not obvious how you access a file.

I was after the vss.log from one of the failed attempts- something like the picture although in my case it gets a green tick because it succeeded

Come to think of it, if you had a log from an earlier occasion when it worked, that would be a useful comparator to see as well.

DavidY said:

Ah maybe I wasn't totally clear as it's not obvious how you access a file.

I was after the vss.log from one of the failed attempts- something like the picture although in my case it gets a green tick because it succeeded

Come to think of it, if you had a log from an earlier occasion when it worked, that would be a useful comparator to see as well.

First is VSS_Short, failed: Second is VSS_Long, good; Second, VSS_Long,failed (Forum software was somewhat confused, just as am I, failing to upload one file, putting them in different order);

Not Myself said:

I started using Macrium 06Aug2016, to replace AOMEI, which had started to give me no-longer remembered problems; that was somewhat ironic, as I had installed AOMEI on my previous computer when Macrium gave me problems. Backupper was transferred from the old to the new machine, so I continued to use it.

Interesting... because the log file contains this error (or something like it - I didn't type all of it in):

Code:

com call "m_pVSSObject->AddToSnapshotSet" failed
HRESULT=0x8004230f
VSS_E_UNEXPECTED_PROVIDER_ERROR

And when I searched for the last error on Macrium's website, it took me here:
http://knowledgebase.macrium.com/dis...party+software

Which is basically saying that, if it's the same scenario, something is left behind by some other backup software (AOMEI being a candidate) which stops VSS working. Although I do have AOMEI on my machine at the moment and it does seem to coexist OK with Macrium.

So the question would be, what do you have at this registry key? And is it the same as in that Macrium article:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers

Editing the registry is a dangerous business so I'd definitely think about doing that backup from bootable rescue media if you haven't already?