Not sure if its XOStor but ... VDIs disappearing

[jcdick1]

@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',

[Danp]

Have you check the status of the nodes and for faulty resources?

linstor n l
linstor r l --faulty

[jcdick1]

@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 ┊
╞══════════════════════════════════════════════════════════════════╡
╰──────────────────────────────────────────────────────────────────╯

[jcdick1]

@Danp

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

[Danp]

@jcdick1 We can take a look using the support tunnel of your XOA instance.

[jcdick1]

@Danp

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

[Pilow]

@jcdick1 you should follow this procedure

https://help.vates.tech/kb/en-us/34-support-tunnel-and-access/30-create-a-support-tunnel

[jcdick1]

@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]

@jcdick1 Ideally you should open a ticket via the Support Portal and provide the tunnel ID there along with a link to this discussion.

[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.