@ronan-a - I've been lurking on this Forum Subject for too long, and I've finally implemented the scripts across three of my hosts, and also added the "Storage" network modifications explained by @Swen and it is working beautifully. Failover is handled by XCP-ng bonded networking if a switch fails, hosts can reboot without any loss in speed or data.

You may recall several years ago I was interested in seeing CEPH implemented natively, but your LINSTOR implementation is so much simpler to manage. Thanks and keep up the good work.

I've been using XenServer for a couple of years and XenOrchestra for nearly as long. I'm interested to see XCP-ng be the new platform to replace Citrix implementation, and very interested in storage options for hyper-convergence.

@Midget I misunderstood, I thought you were mentioning the linstor error and attempting to troubleshoot that. Reviewing the rest of your thread that is not the case.

You mentioned you attempted to burn down the XOSTOR and rebuild it. Here's the issue, your steps of burning down XOSTOR aren't complete.

Simplest method if you're okay with it, format all drives to no partitions, no data, on all of your XCP-ng hosts and rebuild XCP-ng Hosts from scratch from the ISO. Doing that will allow the ISO to build the storage as expected by XOSTOR.

Advanced method - If that seems too drastic a measure, you'll probably need to review the documentation within the Linstor project to find out how you fully remove the partially removed remnants. It involves deleting volume groups, logical groups, and manually removing some linstor components.

@Midget I believe the linstor manager only runs on one XCP-ng Host at a time. So if you ssh to each of your XCP-ng hosts, and run the command:

linstor resource list

The XCP-ng Host running the linstor manager would display the expected results. The other XCP-ng Hosts will display an error similar to what you saw.

Prior to implementing your fix, did you attempt the command from each XCP-ng host and what were the results?

I'd recommend undoing the 127.0.0.1 change and attempting from each host.

@ronan-a - I've been lurking on this Forum Subject for too long, and I've finally implemented the scripts across three of my hosts, and also added the "Storage" network modifications explained by @Swen and it is working beautifully. Failover is handled by XCP-ng bonded networking if a switch fails, hosts can reboot without any loss in speed or data.

You may recall several years ago I was interested in seeing CEPH implemented natively, but your LINSTOR implementation is so much simpler to manage. Thanks and keep up the good work.

Not sure if this is helpful, but I've had success using https://github.com/rposudnevskiy/RBDSR to connect to CEPH using XCP-ng, maybe worth a look?

Though having CEPH support built in like LVMoiSCSI would be great too, and built into XCP-ng even better.

I've been using XenServer for a couple of years and XenOrchestra for nearly as long. I'm interested to see XCP-ng be the new platform to replace Citrix implementation, and very interested in storage options for hyper-convergence.