Support for Windows Products
Support for Windows Products
How To Fix Error In Metadata Volume Operation For Sr
If you have Error In Metadata Volume Operation For Sr then we strongly recommend that you download and run this (Error In Metadata Volume Operation For Sr) repair tool.
Symptoms & Summary
Error In Metadata Volume Operation For Sr and other critical errors can occur when your Windows operating system becomes corrupted. Opening programs will be slower and response times will lag. When you have multiple applications running, you may experience crashes and freezes. There can be numerous causes of this error including excessive startup entries, registry errors, hardware/RAM decline, fragmented files, unnecessary or redundant program installations and so on.
In order to fix your error, it is recommended that you download the 'Error In Metadata Volume Operation For Sr Repair Tool'. This is an advanced optimization tool that can repair all the problems that are slowing your computer down. You will also dramatically improve the speed of your machine when you address all the problems just mentioned.
Recommended: In order to repair your system and Error In Metadata Volume Operation For Sr, download and run Reimage. This repair tool will locate, identify, and fix thousands of Windows errors. Your computer should also run faster and smoother after using this software.
File Size 746 KB
Compatible Windows XP, Vista, 7 (32/64 bit), 8 (32/64 bit), 8.1 (32/64 bit) Windows 10 (32/64 bit)
Graham I've recently come across an issue whereby performing an upgrade from XenServer 5.6 to XenServer 6 has caused the metadata on an SR to become corrupt. The cause of the problem, believe it or not, is special characters, things like ‘-‘, which often go in server names. First thing to check, as with anything storage is the SMlog, under /var/logs. You will probably see something which looks like the following: Error code: SR_BACKEND_FAILURE_181 Error parameters: , Error in Metadata volume operation for SR. opterr=VDI delete operation failed http://discussions.citrix.com/topic/295713-error-in-metadata-volume-operation-for-sr/ for parameters: /dev/VG_XenStorage-427796a3-6891-dcb7-681f-cc7c5463ea0a/MGT, 7b496cd3-9d9c-4cb4-b510-4613e65e7141. Error: not well-formed (invalid token): line 1, column 99,  2011-11-27 08:05:10.977985 Raising exception [181, Error in Metadata volume operation for SR. [opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-511f729e-0f0e-a679-9b8e-4d7ed28f6537/MGT, 65f8e675-9416-4909-8cd1-b7d75af06762. Error: not well-formed (invalid token): line 1, column 65]]  2011-11-27 08:05:10.978109 lock: released /var/lock/sm/511f729e-0f0e-a679-9b8e-4d7ed28f6537/sr  2011-11-27 08:05:10.979583 ***** sr_scan: EXCEPTION SR.SROSError, Error in Metadata volume operation for http://mike-graham.co.uk/blog/2013/06/07/error-scanning-sr-error-in-metadata-volume-operation-for-sr-following-an-upgrade-from-xenserver-5-6/ SR. [opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-511f729e-0f0e-a679-9b8e-4d7ed28f6537/MGT, 65f8e675-9416-4909-8cd1-b7d75af06762. Error: not well-formed (invalid token): line 1, column 65] If you have upgraded to XenServer 6, you require patch http://support.citrix.com/article/CTX135411 If you have upgraded to XenServer 6.0.2 you require patch http://support.citrix.com/article/CTX135623 This issue has not been reported on XenServer 6.1. If like me, you already have this patch installed, yet still have the issue, the problem is a corruption of the MGT VDI on the affected SR, which holds the metadata. This VDI requires rebuilding, which sounds quite scary, but actually isn't. Citrix has a support article regarding this (http://support.citrix.com/article/CTX131660) however it doesn't really detail the solution correctly, and is far too complex, and involves unplugging storage which really isn't necessary! To rebuild your MGT volume, which can be done on a live production system, during operating hours, follow the steps below. Firstly run the following command to rename the existing MGT VDI on the affected SR lvrename /dev/VG_Xenstorage-
This can cause issues that look like metadata corruption resulting in the inability to migrate error in VMs or edit storage. For example: [[emailprotected] ~]# xe vdi-destroy uuid=6c2cd848-ac0e-441c-9cd6-9865fca7fe8b Error code: SR_BACKEND_FAILURE_181 Error error in metadata parameters: , Error in Metadata volume operation for SR. [opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-3ae1df17-06ee-7202-eb92-72c266134e16/MGT, 6c2cd848-ac0e-441c-9cd6-9865fca7fe8b. Error: Failed to write file with params [3, 0, 512, 512]. Error: 5], Removing stale VDIs To fix this, you need to remove those VDIs from the SR after first deleting the logical volume: Get the LV ID (last number shown above) and find it’s location in /dev: [[emailprotected]