If the Logical Volume (LV) has been removed or missing and the attach is called, the following error is returned: Interrupted operation detected on this VDI, scan SR first to trigger auto-repair. This is because an operation is ongoing or was not properly completed.
If the VHD is corrupted, vhd-util is unable to read this data and it fails.Įrrors can be caused by logical volumes being manually removed or by LV metadata corruption.Įrrors occur if unable to read the VDI and IO retry fails when collecting VDI information:Ī check for a journal on the VDI occurs and if one exists, we do not attach VDI. The vhd-util scan is used to verify Virtual Disk Images (VDI) information without activating the logical volumes. The lvs command is used to get the list of logical volumes (LV). The errors have been grouped based on the storage activity occurring at the time they were displayed. This article describes the error messages, the reasons for VDI not available error message, extract from the storage management code, and records in the /var/log/SMlog along with possible causes and resolution to the issue. The additional details of “VDI is not available” error are not displayed. So how to find what is used and what is not.“The VDI is not available” message is displayed in XenCenter after attempting to start a Virtual Machine (VM). In my case I have only about 10 used VDI and about 80 show with xe vdi-list.
Label all you used VDI properly to reduce the change of a mistake. When you create an snapshot and delete it the VDI remain in the disk reducing your available space and creating many other problems.įist find out your storage repositories, VM's and VDI's and match what disk you are actually using and what are not used. If you have used Citrix XenServer you will find very quickly that using the XenCenter interface will create more problems than can be avoided by learning the CLI interface.
0 kommentar(er)
