| Author |
 Topic  |
|
|
Mr.Dave
Starting Member
USA
3 Posts |
 Posted - May 20 2010 : 22:32:51
|
I get this message when I try to create a full image backup of my C: partition:
XML Validation: Error - '<disk>' '1' '<partition>' 3' is not valid-
What does this mean and is there anything I can do to fix it?
The partition was created by backing up C: from my old hard drive to a backup drive, then restoring that image from my backup drive to a new hard drive. The new drive boots just fine, I've been using it for 2 days now, but find my backups are all failing. This is true also for the other partitions on the drive (an extended partition split into 4 logical partitions). I'm using the same XML definition files as before, and even tried editing the file for backup of C: to re-select the drive and partition, but got the same error message.
Using Macrium Reflect version 4.2, build 2525. Windows Vista SP2, Avira antivirus, Nvidia graphics, Intel quad-core CPU.
Thanks for any help you can offer! |
|
|
M.Castaldo
Moderator
United Kingdom
546 Posts |
Posted - May 21 2010 : 00:28:21
|
Hi,
Can you please send your xml file to support @ macrium.com so that we can have a look at it.
Regards,
Martin - Macrium Support |
 |
|
|
Mr.Dave
Starting Member
USA
3 Posts |
Posted - May 21 2010 : 03:15:42
|
Update: I sent copies of XML files to Support as requested. I discovered the XML files contain a "disk id" value, based on the disk used when creating the XML files. When you try to back up from a DIFFERENT disk, even though the partition name and number and disk number are all the same (and in my case the contents as well!) the disk ID is different so the XML file won't run, backup fails. I'm manually replacing the disk id value in all my XML files, but it also works to simply delete the old XML file and create a new one. Ten times!
Thanks, Martin & Macrium Support for your quick response, looks like I figured this one out on my own while writing my reply back to you! |
|
|
|
M.Castaldo
Moderator
United Kingdom
546 Posts |
Posted - May 21 2010 : 08:31:52
|
Hi Dave,
I thought that this was the issue, I'm glad that you sorted this out :)
Thanks,
Martin - Macrium Support |
|
|
|
mel150
New Member
Mexico
12 Posts |
Posted - September 09 2010 : 15:28:19
|
| Hi, I'm having the same issue, where do I find the XML file to edit? Thanks! |
|
|
|
Nick
Moderator
United Kingdom
6303 Posts |
Posted - September 09 2010 : 16:41:29
|
Hi
The XML files are listed in the 'XML Definition Files' tab view:
Kind Regards
Nick - Macrium Support
|
|
|
|
Zardoz2293
New Member
USA
45 Posts |
Posted - March 12 2012 : 21:35:49
|
I just experienced this concern too. Although it isn't that hard to make correct the XML file, my primary concern is why the ability to have Reflect prompt you to update the XML when it discovers the validation error. It's been over 18 months since this has been reported. In my environment I'll be experiencing this frequently.
My thoughts is Reflect needs to prompt the end-user a different disk exists and does the end-user want to add this disk to the available list for this backup. Obviously the XML needs to be updated to support multiple valid disks and adding the drive id to a node/list. If the end-user responds 'yes' the XML is updated, otherwise a 'no' results in no change and the backup can't be performed (effectively as it is now). This way when any of the prior disks are reintroduced the backup can be performed without end-user intervention.
I understand that critical errors are always top priority and there is a workaround for this, but do we have an estimated time on when an enhancement will exist?
What are your thoughts?
---
Reflect Pro - v5.0.4286 (64-Bit) | Windows 7 Ultimate SP1 (64-Bit) | Asus Sabertooth X58, i7-980X @4.3GHz, 24GB @PC3-14400 |
|
|
|
Nick
Moderator
United Kingdom
6303 Posts |
Posted - March 13 2012 : 08:53:30
|
Hi
Thanks for your post.
The error indicates that you attempting to image a disk that is not attached to your system. This can be that the disk is not physically attached or that the disk ID and/or partition layout has changed since the backup definition was created.
This situation should be a rare occurrence and prompting to edit the xml during a backup is not the correct action. The cause of the problem should be investigated and the xml file edited if necessary.
Kind Regards
Nick - Macrium Support
|
|
|
|
Mr.Dave
Starting Member
USA
3 Posts |
Posted - March 14 2012 : 02:51:37
|
| I don't see why this would be a "rare" situation. Any time a drive fails, it seems you would recover your latest backup to a new drive. When you try to run a backup from the new drive, all the XML scripts will fail. Why should I need to edit, or recreate, all of my XML scripts? I like the suggestion from Zardoz2293. Let Reflect fix the scripts for me, once I tell it I'm now running from a different hard drive. Or, simply warn me that the hard drive is not the one Reflect expects, ask my permission to continue, and then fix the scripts. Simple fix to a frustrating safety feature (developer view) or flaw (user view). |
|
|
|
Nick
Moderator
United Kingdom
6303 Posts |
Posted - March 14 2012 : 13:13:31
|
Hi
Thanks for getting back.
quote:
I don't see why this would be a "rare" situation. Any time a drive fails, it seems you would recover your latest backup to a new drive. When you try to run a backup from the new drive, all the XML scripts will fail.
Disk failure is still a rare occurrence. Please note that when an image is restored, so is the Disk ID and the partition information, even to a different disk. XML files use the Disk ID and partition number, and as this information is not changed, the XML files will still be valid.
If your Disk ID's are not consistent then this is not normal.
When scheduling a disk image there should be no blocking user interaction as this may happen when no one is logged on to the PC. It is better that a failure email is sent so that the condition can be notified and corrected rather than a unanswered message that might not be seen. When not scheduling, the status of the xml file can be seen in the view directly beneath the xml file list and you can correct the error before running.
If the DiskID and/or partition layout has changed, this cannot safely be 'corrected' in the xml file automatically.
A possibility is to prompt to edit the xml file and/or to attach the correct disk when initiating a manual image if the Disk ID cannot be located.
Kind Regards
Nick - Macrium Support
|
|
|
| |
Topic |
|
RSS Feed
KB
XML Validation: Error disk 1 partition 3 not valid
Forum Locked
