Macrium Reflect: Backup aborted! Write operation failed - A device whi

Hi
A couple of times in recent month I've been backing up my husband's PC and at the end of a backup Macrium throws a wobbly and tells me the process has failed with a write error. The full error message which appears in bold red text is as follows:
Backup failed! - Write operation failed - A device which does not exist was specified
Problem is the device DOES exist with plenty enough space on the drive. That is the first thing I do, i.e. make sure there is enough space and create the folder into which the backup is to be placed.
His PC is home built by myself and uses a Ryzen 7 5800X together with a GTX1660 SUPER GPU. The current error occurred whilst backing up from a Samsung 970 EVO Plus 500GB NVMe M.2 module to a space of around 550GB on a 4TB WD MyBook. Currently I am using Macrium Reflect Free as this does everything I/we want at present and it is up to date. His total backup takes around 365GB comprising four files plus driver backup.
When this error appeared I had already taken one backup of Windows 10 with no problems. I then started a backup of a different drive which had just about completed when Macrium came up with this error. The first thing I checked was the space available and yes as expected that was fine. I have since done a CHKDSK /F on the drive and no problems were found. This morning (Sunday 24th Oct) I have taken another two backups with no problems.
So my question is: does anyone have any idea what may be causing this problem. I guess I've been using Macrium for my own backups for years and never had any problems. Suddenly, now I'm backing up my husband's PC, I'm starting to have problems. If anyone has any suggestions as to what the problem may be I would appreciate any help that can be offered as I am at a loss. I should add that the first time this happened I tried the backup a second time and it went straight through with no problems.
Tracey

TraceyW hello and welcome to tenforums ,

I would suggest running HD Sentinel app to check drive health for all drives involved, just to rule that out.

Did you run "chkdsk" on both the drives being backed up and the drive where backups are saved?

Hi All

Many thanks for all the replies. I said in my post that it had failed twice since I've been backing up my husband's PC. I've just done a check of the log and in fact it has failed six times, three of those times in one backup session. I've got quite a few old 1TB hard drives skulling around in a drawer so I'm considering setting them up in a dual desktop docking station I have and transferring all the data on the MyBook in four goes then doing whatever is necessary to 'refresh' the MyBook. I shall of course then have to transfer the lot back again and have another go. I do take the point though that we could have a failing hard drive in our possession.

I don't call myself a beginner in computing or using Windows. However, neither am I what would call an expert either. I AM way beyond beginner level though. Whatever, I still feel I have to ask this question: could it be anything to do with Windows being a bit iffy as he's had several new mobos since Windows was last installed on his PC? He hates reinstalling everything and he doesn't really know how to look after his PC as he should.

Tracey

PS I should add that, like myself, my husband is using Windows 10 Pro 21H1.

Run SFC Command in Windows 10

Run sfc and dism to check for Windows system issues. I'd chkdsk all his drives too.

Hi All

I did a backup of all files/folders on my husband's MyBook and then formatted it. Only a quick format though so nothing on the tracks was touched just the MFT wiped. I started copying everything back and it was all going fine - until the same thing happened. I got a message saying the destination drive did not exist. As a result I decided to bite the bullet and get another 4TB external hard drive and all being well this will arrive tomorrow.

Tracey