Citrix XenServer Error: SR_BACKEND_FAILURE_65

I’ve been having issues attaching a VDI to a VM from a NetApp snapshot.  Basically a storage level snapshot that happen while the server was live.  I keep getting the error “The attempt to load the VDI failed” via XenCenter when I try and boot the VM.  I would then look at the log file: /var/log/xensource.log.  I would see that the VM was tossing out the error “SR_BACKEND_FAILURE_65” when it tried to boot.

I have been unable to get the VDI to load on any server.  I even contacted Citrix looking for help and they were unable to get the VDI to load as well.  I’ve seen several others on the internet run into this issue without a resolution.   If someone knows of a trick to get these VDIs to load, please leave a comment!

Hope this helps!

Citrix XenServer Error: The SR failed to complete the operation

Yesterday we started to run out of space on one of our storage repositories.  When we tried to move any VDI on that SR via XenCenter, we got the error “The SR failed to complete the operation”.  Which is a pretty generic error, par for xenserver errors.  I even got the same error when trying to do a ‘Rescan’.

I continued to troubleshoot, looking through logs and command outputs.  I finally found something to look into.

Ran the command:
xe sr-param-list uuid=eb943814-a329-5f84-bd42-af1858d56632

Noticed this parameter:
other-config (MRW): dirty: ; auto-scan: false

I looked into this “dirty” param…  It means xenserver isn’t happen with the file names on the SR.   I listed the files on my SR and saw that someone created a manual copy of a VDI called: Copy of f897ebcf-9365-471b-8a30-e81f564c2536.vhd.

I fixed it by:

* Removing file: Copy of f897ebcf-9365-471b-8a30-e81f564c2536.vhd
* Rescanning the SR
* I was then able to move the VDI from one SR to another with out error.

 

Hope this helps with your day:

Citrix XenServer 6.5 Performance Comparison

Noticed this on the Citrix blog today. A nice little performance comparison between ESXi 5.5 and XenServer 6.5. Citrix claims to show a 11-16% performance advantage over VMware.  I’m holding off on upgrading to 6.5 till summer, but can’t wait to run some of my own benchmarks against XenServer 6.2.

Citrix XenServer Upgrade From 6.1 to 6.2

This weekend I’ve updated from 6.1 to 6.2. Here are the steps I took to do the upgrade.

  1. Make sure you have upgraded your licenses to 6.2 (May require login).  They have changed to a per socket structure, for us we have two sockets per server, and was able to upgrade without paying extra.  The upgrade will warning you if you don’t have the 6.2 license, but you can continue on… just make sure you’ve got the new 6.2 license is applied to your license server.
  2. Download the XenServer-6.2.0-install-cd.iso file (May require login)
  3. I uploaded the file to a physical linux web server not part of my Xen pool
  4. Create a directory called ‘xen’ in the root of your web site
  5. Mount the ISO as a loop device:
    sudo mount -o loop XenServer-6.2.0-install-cd.iso xen/
  6. Update XenCenter.msi to the latest version. After updating XenCenter, “About XenCenter” shows my version as “6.2 (build 1377)”
  7. Backup your XenServer Pool, ssh into your pool master and run this command.  Copy into your backups on a file server
    xe pool-dump-database file-name=xenpool.backup.20140510
  8. Disable HA
  9. Shutdown any unneeded VMs, this will decrease the time it takes to preform the upgrade
  10. To preform the upgrade, in XenCenter goto Tools -> Rolling Pool Upgrade
  11. Select your pool
  12. Select ‘Automatic Mode’
  13. Obey the rules of the pre-check
  14. Run the upgrade.  I had a few issues and had to restart the rolling upgrade, which didn’t seem like an issue.  My issues were mostly VMs loosing their VDIs, which can be fixed via this article.

Citrix XenServer Error: Detaching SR – General backend error

After a power outage we ran into some errors after bring everything back up.  When trying to reconnect a CIFS share on our NetApp filer, we got the following errors.

Jan 3, 2014 10:40:10 AM Error: Repairing SR CIFS ISO library On Netapp - Unable to mount the directory specified in device configuration request
Jan 3, 2014 10:40:54 AM Error: Detaching SR 'CIFS ISO library On Netapp' from 'SOME POOL' - General backend error

At first I thought the issue was Xenserver not bring joined to the Active Directory domain. But I was wrong, the issue was the NetApp wasn’t joined to the AD domain. So make sure everyone is on the domain and you may get rid of these errors. For us, the issue was the time on the NetApp was off by 6 minutes and was causing errors when trying to join AD (time needs to be with in sync within 5 minutes).

Citrix XenServer SR Backend Failure Error Codes

SRInUse

The SR device is currently in use.
16

VDIInUse
The VDI is currently in use.
24

LockErr
The lock or unlock request failed.
37

Unimplemented
The requested method is not supported or implemented.
38

SRNotEmpty
The Storage Repository is not empty.
39

ConfigLUNMissing
The request is missing the LUNid parameter.
87

ConfigSCSIid
The SCSIid parameter is missing or incorrect.
107

ISODconfMissingLocation
‘Location’ parameter must be specified in Device Configuration.
220

ISOMustHaveISOExtension
ISO name must have .iso extension.
221

ISOMountFailure
Could not mount the directory specified in Device Configuration.
222

ISOUnmountFailure
Could not unmount the directory specified in Device Configuration.
223

ISOSharenameFailure
Could not locate the ISO sharename on the target, or the access permissions might be incorrect.
224

ISOLocationStringError
Incorrect Location string format. String must be in the format SERVER:PATH for NFS targets, or \\SERVER\PATH for CIFS targets.
225

ISOLocalPath
Invalid local path
226

InvalidArg
Invalid argument
1

BadCharacter
A bad character was detected in the dconf string.
2

InvalidDev
No such device
19

InvalidSecret
No such secret
20

SRScan
The Storage Repository scan failed.
40

SRLog
The Storage Repository log operation failed.
41

SRExists
The Storage Repository already exists.
42

VDIExists
The VDI already exists.
43

SRNoSpace
There is insufficient space.
44

VDIUnavailable
The VDI is not available.
46

SRUnavailable
The Storage Repository is not available.
47

SRUnknownType
Unknown repository type
48

SRBadXML
Malformed XML string
49

LVMCreate
Logical Volume creation error
50

LVMDelete
Logical Volume deletion error
51

LVMMount
Logical Volume mount or activate error
52

LVMUnMount
Logical Volume unmounts or deactivate error
53

LVMWrite
Logical Volume write error
54

LVMPartCreate
Logical Volume partition creation error
55

LVMPartInUse
Logical Volume partition in use
56

LVMFilesystem
Logical Volume file system creation error
57

LVMMaster
Logical Volume request must come from master.
58

LVMResize
Logical Volume resize failed.
59

LVMSize
Logical Volume invalid size
60

FileSRCreate
File Storage Repository creation error
61

FileSRRmDir
File Storage Repository failed to remove directory.
62

FileSRDelete
File Storage Repository deletion error
63

VDIRemove
Failed to remove VDI.
64

VDILoad
Failed to load VDI.
65

VDIType
Invalid VDI type
66

ISCSIDevice
ISCSI device failed to appear.
67

ISCSILogin
ISCSI login failed, verify CHAP credentials.
68

ISCSILogout
ISCSI logout failed.
69

ISCSIInitiator
Failed to set ISCSI initiator.
70

ISCSIDaemon
Failed to start ISCSI daemon.
71

NFSVersion
Required NFS server version unsupported.
72

NFSMount
NFS mount error
73

NFSUnMount
NFS unmount error
74

NFSAttached
NFS mount point already attached.
75

NFSDelete
Failed to remove NFS mount point.
76

NFSTarget
Unable to detect an NFS service on this target.
108

LVMGroupCreate
Logical Volume group creation failed.
77

VDICreate
VDI Creation failed.
78

VDISize
VDI Invalid size
79

VDIDelete
Failed to mark VDI hidden.
80

VDIClone
Failed to clone VDI.
81

VDISnapshot
Failed to snapshot VDI.
82

ISCSIDiscovery
ISCSI discovery failed.
83

ISCSIIQN
ISCSI target and received IQNs differ.
84

ISCSIDetach
ISCSI detach failed.
85

ISCSIQueryDaemon
Failed to query the ISCSI daemon.
86

NFSCreate
NFS Storage Repository creation error
88

ConfigLUNIDMissing
The request is missing the LUNid parameter.
89

ConfigDeviceMissing
The request is missing the device parameter.
90

ConfigDeviceInvalid
The device is not a valid path.
91

VolNotFound
The volume cannot be found.
92

PVSfailed
PVS failed
93

ConfigLocationMissing
The request is missing the location parameter.
94

ConfigTargetMissing
The request is missing the target parameter.
95

ConfigTargetIQNMissing
The request is missing or has an incorrect target IQN parameter.
96

ConfigISCSIIQNMissing
Unable to retrieve the host configuration ISCSI IQN parameter.
97

ConfigLUNSerialMissing
The request is missing the LUN serial number.
98

LVMOneLUN
Only 1 LUN may be used with shared LVM.
99

LVMNoVolume
Cannot find volume
100

ConfigServerPathMissing
The request is missing the serverpath parameter.
101

ConfigServerMissing
The request is missing the server parameter.
102

ConfigServerPathBad
The serverpath argument is not valid.
103

LVMRefCount
Unable to open the refcount file
104

Rootdev
Root system device, cannot be used for virtual machine storage.
105

InvalidIQN
The IQN provided is an invalid format.
106

SnapshotChainTooLong
The snapshot chain is too long.
109

VDIResize
VDI resize failed.
110

APISession
Failed to initialize XMLRPC connection.
150

APILocalhost
Failed to query Local Control Domain.
151

APIPBDQuery
A failure occurred querying the PBD entries.
152

APIFailure
A failure occurred accessing an API object.
153

NAPPTarget
Netapp Target parameter is missing in Dconf string.
120

NAPPUsername
Netapp Username parameter is missing in Dconf string.
121

NAPPPassword
Netapp Password parameter is missing in Dconf string.
122

NAPPAggregate
Netapp Aggregate parameter is missing in Dconf string.
123

NAPPTargetFailed
Failed to connect to Netapp target.
124

NAPPAuthFailed
Authentication credentials incorrect
125

NAPPInsufficientPriv
Authentication credentials have insufficient access privileges.
126

NAPPFVolNum
Maximum number of flexvols reached on target. Unable to allocate the requested resource.
127

NAPPSnapLimit
Maximum number of Snapshots reached on target Volume. Unable to create the snapshot.
128

NAPPSnapNoMem
Insufficient space, unable to create the snapshot.
129

NAPPUnsupportedVersion
Netapp Target version unsupported
130

NAPPTargetIQN
Unable to retrieve target IQN
131

NAPPNoISCSIService
ISCSI service is not running on the Netapp target.
132

NAPPAsisLicense
Failed to enable A-SIS for the SR. Requires valid license on the filer.
133

NAPPAsisError
The filer does not support A-SIS on this aggregate. The license is valid however on some filers A-SIS is limited to smaller aggregates, for example, FAS3020 max supported aggregate is 1 TB. Refer to filer support documentation for details on the model. You must either disable A-SIS support, or re-configure the aggregate to the maximum supported size.
134

NAPPExclActivate
Failed to acquire an exclusive lock on the LUN.
135

DNSError
Incorrect DNS name, unable to resolve.
140

ISCSITarget
Unable to connect to ISCSI service on target
141

ISCSIPort
Incorrect value for ISCSI port must be a number between 1 and 65535.
142

BadRequest
Failed to parse the request.
143

VDIMissing
VDI could not be found.
144

EQLTarget
Equallogic Target parameter is missing in Dconf string.
160

EQLUsername
Equallogic Username parameter is missing in Dconf string.
161

EQLPassword
Equallogic Password parameter is missing in Dconf string.
162

EQLStoragePool
Equallogic StoragePool parameter is missing in Dconf string.
163

EQLConnectfail
Failed to connect to Equallogic Array; maximum SSH CLI sessions reached
164

EQLInvalidSnapReserve
Invalid snap-reserver-percentage value must be an integer indicating the amount of space as a percentage of the VDI size, to reserve for snapshots.
165

EQLInvalidSnapDepletionKey
Invalid snap-depletion value must be one of ‘delete-oldest’ or ‘volume-offline’.
166

EQLVolOutofSpace
Volume out of space, probably because to insufficient snapshot reserve allocation.
167

EQLSnapshotOfSnapshot
Cannot create Snapshot of a Snapshot VDI, operation unsupported.
168

EQLPermDenied
Failed to connect to Equallogic Array, Permission denied;username/password invalid
169

EQLUnsupportedVersion
Equallogic Target version unsupported.
170

EQLTargetPort
Unable to logon to Array. Check IP settings.
171

EQLInvalidStoragePool
Equallogic StoragePool parameter specified in Dconf string is Invalid.
172

EQLInvalidTargetIP
Equallogic Target parameter specified in Dconf string is Invalid, specify the correct Group IP address.
173

EQLInvalidSNMPResp
Invalid SNMP response received for a command line interface command.
174

EQLInvalidVolMetaData
Volume metadata stored in the ‘Description’ field is invalid. This field contains encoded data and is not user editable.
175

EQLInvalidEOFRecv
Invalid EOF response received for a CLI command.
176

LVMProvisionAttach
Volume Group out of space. The SR is over-provisioned, and out of space. Unable to grow the underlying volume to accommodate the virtual size of the disk
180

MetadataError
Error in Metadata volume operation for SR.
181

EIO
General IO error
200

EGAIN
Currently unavailable, try again
201

SMGeneral
General backend error
202

FistPoint
An active FIST point was reached that causes the process to exit abnormally.
203

CSLGConfigServerMissing
The CSLG server name or IP address is missing.
400

CSLGConfigSSIDMissing
The Storage System ID is missing.
401

CSLGConfigPoolIDMissing
The Storage Pool ID is missing.
402

CSLGProtocolCheck
The GSSI operation to the CSLG server failed.
410

CSLGLoadSR
The Storage Repository loading operation failed.
411

CSLGInvalidProtocol
An invalid storage protocol was specified
412

CSLGXMLParse
Unable to parse XML
413

CSLGProbe
Failed to probe Storage Repository.
414

CSLGSnapClone
Snapshot/Clone failed.
416

CSLGAssign
Storage assignment failed.
417

CSLGUnassign
Storage un-assignment failed.
418

CSLGAllocate
Storage allocation failed.
419

CSLGDeallocate
Storage deallocation failed.
420

CSLGHBAQuery
HBA Query failed.
421

CSLGISCSIInit
IQN/ISCSI initialization failed.
422

CSLGDeviceScan
SCSI device scan failed.
423

CSLGServer
Failed to connect to CSLG.
424

CSLGConfigSVIDMissing
The Storage Node ID is missing.
425

CSLGIntroduce
The VDI failed to be introduced to the database.
426

CSLGNotInstalled
The CSLG software does not seem to be installed.
427

CSLGPoolCreate
Failed to create multiple sub-pools from parent pool.
428

CSLGOldXML
Current XML definition is newer version.
429

MultipathdCommsFailure
Failed to communicate with the multipath daemon.

430

 

CSL_Integrated

Error in storage adapter communication

431

CSLGConfigAdapterMissing

The adapter id is missing or unknown

432

CSLGConfigUsernameMissing

The username is missing

433

CSLGConfigPasswordMissing

The password is missing

434

CSLGInvalidSSID

An invalid storage system ID was specified

435

CSLGSysInfo

Failed to collect storage system information

436

CSLGPoolInfo

Failed to collect storage pool information

437

CSLGPoolDelete

Failed to delete storage pool

438

CSLGLunInfo

Failed to collect storage volume information

439

CSLGLunList

Failed to list storage volume

440

CSLGResizeLun

Failed to resize storage volume

441

CSLGTargetPorts

Failed to list storage target ports

442

CSLGPoolList

Failed to list storage pool

443

TapdiskFailed

The tapdisk failed

444

TapdiskAlreadyRunning

The tapdisk is already running

445

CIFSExtendedCharsNotSupported

XenServer does not support extended characters in CIFS paths, usernames, passwords, and file names.

446

IllegalXMLChar

Illegal XML character.

447

Citrix XenServer 6.1 Internal error: File “xapi_xenops.ml”, line 1788, characters 3-9: Assertion failed

Today I rebooted a xen host, everything came back up as I would expect, and after trying to live migrate VMs back onto the host I got this error message.

Internal error: File "xapi_xenops.ml", line 1788, characters 3-9: Assertion failed

I thought it was something wrong with xencenter, but then tried via command line and got this error:

Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=VDI SOME-UUID already attached RW]

 

The message “The VDI is not available” I’ve seen many times before and I knew what to do.

 

 

Citrix XenServer 6.1 – XenServer Tools out of date (version 6.0 installed)

Recently we upgraded our XenServer resource pool to 6.1 because the new feature allowing you to do live migration of VDI’s sounds unreal.  I still get amazed that this stuff works, well most of the time.  Now we are having issues with XenTools reporting to be out of date in XenCenter, I see the message:

XenServer Tools out of date (version 6.0 installed)

Great, I’ll just pop the XenTools CD in, uninstall the old version, and install the new version.  Nope, that does not work.  Instead it makes the issues worst, as you try and reboot the system but XenServer never figures out the server is shutdown and you end up having to do vm-reset-powerstate or even destroy the domain.  Either way this sucks.

Citrix just updated it’s XenServer blog yesterday acknowledging the issues with XenTools is real and they will try and fix their processes.  And they are right, this sort of thing really does hurt your confidence in the system.  And we all know virtualization is built on confidence.

Now here is the real place to get all the info on what needs to happen.  It’s a two part update, first you need to apply hot fix XS61E009 and then XS61E010.  Then you have the fun of updating XenTools.  But lots of work non the less when you have 10s, 100s, 1000s of VMs.

http://support.citrix.com/article/CTX135099
http://support.citrix.com/article/CTX136252
http://support.citrix.com/article/CTX136253

*UPDATE*

If you run in to blue screen on Windows while installing the new XenTools from the XS61E010… I know more issues??  If you can get into safe mode to remove xentools from the machine and reinstall, that may work.  Other wise you can try looking yup your VMs UUID and changing the device ID.  This may work if your VM does not get the correct device ID set during the new xentools install. Use this command:

xe vm-param-set uuid=<vm_uuid> platform:device_id=0001

or

xe vm-param-set uuid=<vm_uuid> platform:device_id=0002

Citrix XenServer Error: VDI is not Available

Error: Starting VM ” – The VDI is not available

So you’re now trying to boot a VM in XenServer but you are getting the error “VDI is not Available”. This means that VM crashed, Xen Host crashed, or something just bad happen. Either way you need your server back.

  1. Find the UUID of the VDI in question.
    xe vdi-list
  2. Note exactly what UUID maps to which drive is on your server.  This is going to remove the VDI from the VM so we can reattach it correctly.  So drive order does matter, you don’t want to switch an OS VDI with a data VDI.
    xe vdi-forget uuid=<VDI UUID we found in step 1>
  3. Open XenCenter and navigate to the SR with your VDI.  Hit rescan
  4. Now goto your VM with issues and attach the VDI via the storage tab
  5. Boot your VM