When I run an image backup of my Win8.1 install using MR v6 Home build 499, I get the following in the Image Options tab under Imaging Summary:
Backup Definition File: C:\Users\<username>\2015-03-05\<fn>-00-00.mrimg
XML Validation:  Error - "<disk>" "2" "<partition>" 2" is not valid-

The "XML Validation" line is in red

I have four drives in my desktop.  How to I find out which drive that MR considers "disk 2"?

One of the drives contains Linux filesystem partitions because I'm running some Linux distros on the desktop.  Is that the drive?

I actually tried a test just after I upgraded from MR v5 Pro to MR v6 Home and was able to backup and restore all the Linux filesystem partitions.  So, MR can read those partitions without problems.

Reflect's main user interface displays all of your drives and partitions in order and it should show you a disk number and ID for each drive. Select the tabs [Backup] and [Create A Backup].  You might want to post a screenshot for additional info on the issue that you're seeing.


Regards, Richard V. ("Arvy")

OK, this makes even less sense...   You can see in the screenshot that MR is complaining about disk 2, partition 2. As seen in the other screenshot, disk 2, partition 2 is the Win8.1 partition -- the very partition that I'm doing the image backup on.



How can MR complain about the partition being invalid but yet, then perform a backup of that same partition -- without further problems?

Richard: You're right.  Your comment about backup definition files caused me to do further investigation and, as it turns out the pathame and filename of the Backup definition file in the error message is incorrect!  The error message says C:\Users\<username>\2015-03-05\<fn>-00-00.mrimg ... but that is not a definition file, that is an image file!  The definition files are stored in C:\Users\<username>\Documents\Reflect and are of the format "My Backup[(nn)].xml" -- because they are xml files.

So, I deleted the previous backup definition files, reran the backup and this time, the Backup Definition File name in the Imaging Summary section is correct and no errors were reports.

Thanks very much for your help.

You're welcome, Mark.  Glad it worked out and wasn't an actual "invalid partition" issue.  If you'd like to mark my earlier response as "the answer" it might be helpful to others searching this forum in the future.

Regards, Richard V. ("Arvy")

OK, done