Full error message : "Backup aborted! - Write operation failed - The system cannot find the file specified". However, this happens when trying to do a full image. There's no file to find, right ? Since Macrium is supposed to make a fresh full image right from the start ? So what does this error message mean ?

What especially annoys me, is I repeatedly met this failure in the past. I thought it might be because of a defective, old system disk, which kept throwing a bad sector at the beginning. So I replaced it with a brand new SSD. And now I get this again ?

I found this forum post about a slightly different error mesage :

https://knowledgebase.macrium.com/display/KNOW/Error+Code+2+-+The+system+cannot+find+the+file+specified

So I applied the recommended solution :

vssadmin Resize ShadowStorage /For=c: /On=c: /Maxsize=10%

Imaging fails again. It stops right at the start, after analyzing volumes. Macrium says "closing VSS" and stops the process.

EDIT : differential and incremental fail as well. Incremental has the same error message. Differential has "Backup aborted ! Error reading image file".

Can someone help me, please ?

Write operations would mean an issue with your destination disk.  What kind of disk are you backing up to?  Can you see the disk in file explorer or the Macrium user interface?

The fact that Reflect is calling out a write operation failure with this error means that Reflect lost connectivity to the destination, even if only briefly.  I believe I've seen problematic USB cables, USB ports, network cables, network switches/routers reported as underlying causes of this error here.  Note that even if those items perform normally otherwise, a backup operation generates a lot more traffic than most people's average load, so it can surface problems that might otherwise not arise.

+x

 

capair45 - 9 September 2020 11:10 PM

Write operations would mean an issue with your destination disk.  What kind of disk are you backing up to?  Can you see the disk in file explorer or the Macrium user interface?

Sorry for being late in answering.

It's an external, mechanical 2,5", which I put myself in an enclosure. I'm alternating between 2 similar disks, but one is in a USB 2.0 enclosure, the other one in a USB 3.0 enclosure. I don't know which it was generating the error, but this happens to me regularly.

Yes, I can see the destination disk in my file explorer.

+x

 

jphughan - 10 September 2020 12:24 AM

The fact that Reflect is calling out a write operation failure with this error means that Reflect lost connectivity to the destination, even if only briefly.  I believe I've seen problematic USB cables, USB ports, network cables, network switches/routers reported as underlying causes of this error here.  Note that even if those items perform normally otherwise, a backup operation generates a lot more traffic than most people's average load, so it can surface problems that might otherwise not arise.

Sorry for being late in answering. I did not get an email alert, although I'm subscribed to this thread.

Yes, this might be a cause, although I've changed many things since this first happened to me : enclosure, cable...

+x

 

Clairvaux - 28 September 2020 7:50 PM

+x

 

capair45 - 9 September 2020 11:10 PM

Write operations would mean an issue with your destination disk.  What kind of disk are you backing up to?  Can you see the disk in file explorer or the Macrium user interface?

Sorry for being late in answering.

It's an external, mechanical 2,5", which I put myself in an enclosure. I'm alternating between 2 similar disks, but one is in a USB 2.0 enclosure, the other one in a USB 3.0 enclosure. I don't know which it was generating the error, but this happens to me regularly.

Yes, I can see the destination disk in my file explorer.

Are you connecting your external HD directly to the computer (no USB hub)?  Try a new/different cable that you know is good using a different USB port.  Also, you might try running chkdsk x: /r on the external drive (x is the letter of your external drive).