Unable to create XOSTOR volume

SuperDuckGuy

Hi everyone,

I am attempting to create an XOSTOR volume on a newly created pool as part of a demonstration environment for evaluating a migration from VMware vSphere to XCP-ng. However, I have been unable to successfully create the XOSTOR volume. I have attached the relevant error log for reference.

All hosts in the pool are identical Dell R730 systems, fully patched, each equipped with fifteen 1TB drives connected through a Dell HBA330 controller. The only difference between the four hosts is the amount of installed RAM. Running fully patched XOA trial.

This is my first time attempting to create an XOSTOR volume, and the error message returned does not provide much detail beyond stating “unknown error from the peer.” I would appreciate any guidance on what might be causing this issue.

Thank you in advance. Looking forward to rolling this out!

2026-03-05T18_46_22.149Z - XO.txt

AtaxyaNetwork

@SuperDuckGuy Hi !

Are you on XOA trial and/or air gap environment ?
I remember seeing the -32000 error a while ago, but I don't remember why

SuperDuckGuy

@AtaxyaNetwork Hello! I am on an XOA trial with no airgapping.

SuperDuckGuy

Hello, following up on this. Can anyone help decipher what the issue is? I'm stuck on this trial deployment until I can get the storage configured. Thanks!

alcoralcor

Hello,
I'm new to xcp-ng but it seems I have the same issue.
I have done some tests to resolve this (but failed) and if I remember, when i look at /var/log/audit.log in the first host of my cluster, I saw this error :

... [ failure: repodata/repomd.xml from xcp-ng-linstor: [Errno 256] No more mirrors to try. https://repo.vates.tech/xcp-ng/8/8.3/linstor/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for xcp-ng-linstor ...

but installing manually xcp-ng-linstor with yum does not solve the issue.

PS : In your case, it seems you want more than 7 disks in your xostor and I think you need between 3 and 7 disks.

SuperDuckGuy

@alcoralcor Thanks for the info. I thought maybe I was using too many disks, so I've tried creating disk groups of 3-4 drives with the same issue.

poddingue

AtaxyaNetwork's instinct feels right to me, so I'd start there: XOSTOR has to install its LINSTOR/DRBD packages on each host from the XCP-ng repo, and alcoralcor's repodata failure in audit.log suggests that step is failing.
As far as I know, -32000 back in XO is often just the generic wrapper around a host-side install problem like that.
On a trial, it's worth double-checking each host in the pool can actually reach updates.xcp-ng.org (no proxy or firewall in the way) and that the XOSTOR prerequisites in the docs are met before creating the volume: https://docs.xcp-ng.org/xostor/.
If the hosts can reach the repo but it still fails, this is likely a @Team-Storage issue.
I'm out of my depth on XOSTOR internals, though, so take this as a starting point rather than a diagnosis.

SuperDuckGuy

@poddingue Hi there and thanks for the info. I forgot to update this post. The issue in the end turned out to be something broken on the backend Xen Orchestra licensing for XOSTOR. Support was able to fix it.

poddingue

Thanks for coming back to close it out. That's useful to know.
So I was plenty wrong, as it was the XOSTOR licensing backend rather than the repo side I guessed at; those -32000 errors really don't give much away.
For anyone landing here later: sounds like -32000 on XOSTOR creation can come from either end, a licensing/entitlement issue that support sorts, or a host not reaching the package repo, so both are worth checking. @alcoralcor, did support get yours sorted too, or is yours still the repodata / repo-reachability one?
Glad you're unblocked either way.