Issue still persisted after rebooting and running fsck. Host went into read-only mode not long after it came up.

I will restart and use a systemrescuecd to run fsck

It's a recently installed host.Root is only at 10% utilization. Does XCP-ng have any compatibility issues with Supermicro servers?

Hello all,
Recently experienced an issue of host upgraded from XenServer 6.5 to XCP-ng going into read-only mode. Once in this state, VMs can't be migrated to other hosts nor can VMs be started on the host. When restarted the issue is resolved for a short time but then re-occurs.

Did a fsck check and repair but this did not resolve the issue. Posts on similar issue pointed to a boot disk failure and so we replaced the disk and re-installed XCP-ng Ver 8.0 but once added back to the pool the issue re-occurred. Trying to start a VM on the host shows the error below:

Does anyone have any experience with this and how to resolve.