jcdick1

@poddingue

Okay, we're back here. I was told I have a hung CIFS mount that no longer exists, so a host needs to reboot to clear it, and faulty XOSTOR resources. But I can't reboot the host until I can move VMs off. Is there any indication of how to repair the faulty XOSTOR resources so I can move the VMs and reboot the host?

Thanks for taking a look.

@Danp

I'm US Central time, so I'll open the tunnel around 2:00am tomorrow. Who do I send the code to?

Thanks!

@Danp

I have my XOA registered, so let me know how I go about getting you into it.

@Danp

New VMs just hang with the XCP-ng rocketship logo in the console. I've tried UEFI and traditional BIOS.

@Danp

╭───────────────────────────────────────────────────────────────────╮
┊ Node               ┊ NodeType ┊ Addresses                ┊ State  ┊
╞═══════════════════════════════════════════════════════════════════╡
┊ host1  ┊ COMBINED ┊ XX.XX.XX.16:3366 (PLAIN) ┊ Online ┊
┊ host2  ┊ COMBINED ┊ XX.XX.XX.17:3366 (PLAIN) ┊ Online ┊
┊ host3  ┊ COMBINED ┊ XX.XX.XX.15:3366 (PLAIN) ┊ Online ┊
╰───────────────────────────────────────────────────────────────────╯
[16:14 host1 ~]# linstor r l --faulty
╭──────────────────────────────────────────────────────────────────╮
┊ ResourceName ┊ Node ┊ Layers ┊ Usage ┊ Conns ┊ State ┊ CreatedOn ┊
╞══════════════════════════════════════════════════════════════════╡
╰──────────────────────────────────────────────────────────────────╯

@poddingue

sm-3.2.12-23.5.xcpng8.3.x86_64 across all three hosts.

Just tried running through the chain of repair and restart, and I'm getting this on the latest as well:

[12:49 host1 ~]# xe vm-start uuid=c0faf508-9f14-e091-43b1-d6c5ef7e07d4
Error code: SR_BACKEND_FAILURE_1200
Error parameters: , [Errno 30] Read-only file system: '/dev/drbd/by-res/xcp-volume-693829e3-0b60-4b0c-bed2-611995ec83f1/0',

I am having an issue with my XCP cluster, running Linstor across three nodes.

Migrations don't complete. The final handoff doesn't finish, and they sit at 100%. VM reboots result in the underlying VDI becoming unavailable. A VM that was running just fine gets a reboot and I have to go through the process of 'xl list' 'xl destroy <X>' etc. And then on attempted start:

Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=VDI 6c8fe996-2466-47ef-993b-0de3b66da92e not detached cleanly],

I can't snapshot or do full backups. The task just hangs.
Edit: I just attempted a snapshot of a VM via the official XO Appliance, and got this:

SR_BACKEND_FAILURE_82(, Failed to snapshot VDI [opterr=['MAP_DUPLICATE_KEY', 'VDI', 'sm_config', 'OpaqueRef:cbf6441d-c558-725b-8b21-39609026f507', 'paused']], )

This is becoming a regular occurrence, and I'm not sure what to do to stop this. My environment is slowly degrading. But it definitely seems like its an issue within the SR.

Any help would be appreciated.

@acebmxer

Yeah, it does not show up as an available device in XOA or XCP-ng Center. Just listed when running lspci

At one point there was a 10GbE NIC in one of my servers, but has since been removed. A GPU has been installed, but the system is showing the old nic still sitting at 07:00.0 which is also the GPU.

What would be the best way to get rid of this ghost nic from the system so that I can effectively get this GPU assigned?

Thanks!

I've got my OPNsense (FreeBSD) router running in a VM on XCP, and it does have the xe-guest-utilities installed. I'm trying to figure out an issue on one of the interfaces, and I noticed a weird discrepancy in XO with this VM. The MAC addresses and such for the interfaces being used by the VM are all off.

It seems that VIF #0 is the only one coming up correctly.

Unfortunately, I don't think the FreeBSD or OPNsense teams have a maintainer for the xe-guest-utilities package, and so what they distribute is showing as 6.2.1-76888 in XO.

I don't know if this is what is causing my network issue, but I thought it strange.