Robert in CA wrote:
If I'm understanding you correctly the disk id's do not match up
C: drive is (000369E9) and the E: drive is (000E9230) so I would
need instructions to change the XML file.

https://postimg.cc/tnCkssyL


I had the thought of doing a test to see if the older Mrimgs we
haven't checked if they also have the have the XML error but
before doing so I saw our last Mrimg we did after I downloaded
an important update and it doesn't have the XML error.

https://postimg.cc/SnQ86BMp


Robert


You're probably backing up the first disk, containing
System and Windows. The identifier applies to the whole
disk, so the Macrium XML file would look like this. Partition 1
is "System" and Partition 2 is "Windows".

image_entry id="1"
!-- disk is the 1 based index of the disk to be imaged --
!-- id is the disk signature and is ... ... --
disk id="000369E9"1/disk
!-- partition is the 1 based index of the partition on the disk --
partition1/partition
/image_entry

image_entry id="2"
disk id="000369E9"1/disk
partition2/partition
/image_entry

E: is probably part of the backup drive, so "000E9230" won't be in the
sources section of the XML file.

*******

Each backup you make, records the DiskID it found. Even if the XML
file has the wrong value, the MRIMG file will have the "as recorded"
value, ensuring during restoration, that the Disk ID will
end up the same as it was during the backup.

Somewhere along the way, you changed drives and don't
remember doing that.

This problem does not materially affect what's been done,
so there is no reason for hair loss here. If you restore an
MRIMG, if tries to put things back as recorded in the MRIMG.
And when the backups are made, Macrium faithfully records
what is on the disk, even if it doesn't match the XML file.

Fixing up the XML file now, is for consistency and to cause
the error to buzz off. A Macrium backup run today, will
show the same metadata as one made yesterday.

Macrium does as much consistency checking as it can,
before the backup operation starts. Once it starts making
a backup, the software is convinced the backup has
sufficient integrity to be useful. It knows it is backing
up SATA Port 1, even though the identifier didn't match.
If a matching identifier had been found on any other
port in the machine, that's the one that would have got
backed up. The algorithm is, back up the "Disk ID" one
if you can find a match, otherwise, use the port number
and grab that drive, as the closest matching identifier.
If there was no drive on Port 1, the Disk ID didn't match,
Macrium would stop and present some red error text.

Paul