XCP-NG Host stuck in read-only mode
-
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. -
Disk full?
-
It's a recently installed host.Root is only at 10% utilization. Does XCP-ng have any compatibility issues with Supermicro servers?
-
@Denson check
# dmesg -
@Denson may be corrupt file system? you can probably try fsck on your next reboot
touch /forcefsck -
I will restart and use a systemrescuecd to run fsck -
Issue still persisted after rebooting and running fsck. Host went into read-only mode not long after it came up.
-
@Denson so if you don't add this host back to the pool it doesn't go read-only? May be it has something to do with shared storage, anything in /var/log/SMlog? Also check
df -h -
@Denson Was this ever resolved?
In Xen Orchestra go to Settings/Servers and you will see a "Read Only" switch that might address the problem.
-Jorge -
@dmjorge This was never resolved. Replaced RAM and SSD, disabled SAS controller and same issue. Tried installing XCP on a different server but the same model and the issue re-occured.
Installed Proxmox and it has been running without any issue. I believe there is a compatibility issue of XCP-ng and Supermicro SYS-6028TP-HC0R -
The screenshot error posted is just a harmless warning
-
@olivierlambert Those were the only messages on the log, nothing else captured on any other log file like the crit.log file or dmesg
