<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[XCP-NG Host stuck in read-only mode]]></title><description><![CDATA[<p dir="auto">Hello all,<br />
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.<br />
<img src="/forum/assets/uploads/files/1600941427717-xcp-readonly.png" alt="XCP-Readonly.png" class=" img-fluid img-markdown" /><br />
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:<br />
<img src="/forum/assets/uploads/files/1600941213469-xcp-tapdiskerror.png" alt="XCP-tapdiskerror.png" class=" img-fluid img-markdown" /><br />
Does anyone have any experience with this and how to resolve.</p>
]]></description><link>https://xcp-ng.org/forum/topic/3602/xcp-ng-host-stuck-in-read-only-mode</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 17:56:33 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/3602.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 24 Sep 2020 09:57:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Tue, 11 Apr 2023 10:06:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/olivierlambert" aria-label="Profile: olivierlambert">@<bdi>olivierlambert</bdi></a> Those were the only messages on the log, nothing else captured on any other log file like the crit.log file or dmesg</p>
]]></description><link>https://xcp-ng.org/forum/post/60982</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/60982</guid><dc:creator><![CDATA[Denson]]></dc:creator><pubDate>Tue, 11 Apr 2023 10:06:16 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Tue, 11 Apr 2023 10:00:20 GMT]]></title><description><![CDATA[<p dir="auto">The screenshot error posted is just a harmless warning</p>
]]></description><link>https://xcp-ng.org/forum/post/60981</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/60981</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Tue, 11 Apr 2023 10:00:20 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Tue, 11 Apr 2023 09:52:26 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/dmjorge" aria-label="Profile: dmjorge">@<bdi>dmjorge</bdi></a> 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.<br />
<img src="/forum/assets/uploads/files/1681206581426-xcp-xapi-errors.png" alt="xcp-xapi-errors.png" class=" img-fluid img-markdown" /><br />
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</p>
]]></description><link>https://xcp-ng.org/forum/post/60979</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/60979</guid><dc:creator><![CDATA[Denson]]></dc:creator><pubDate>Tue, 11 Apr 2023 09:52:26 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Tue, 05 Jul 2022 19:59:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/denson" aria-label="Profile: Denson">@<bdi>Denson</bdi></a> Was this ever resolved?<br />
In Xen Orchestra go to Settings/Servers and you will see a "Read Only" switch that might address the problem.<br />
-Jorge</p>
]]></description><link>https://xcp-ng.org/forum/post/50873</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/50873</guid><dc:creator><![CDATA[dmjorge]]></dc:creator><pubDate>Tue, 05 Jul 2022 19:59:32 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Thu, 08 Oct 2020 02:48:21 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/denson" aria-label="Profile: Denson">@<bdi>Denson</bdi></a> 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</p>
<pre><code>df -h
</code></pre>
]]></description><link>https://xcp-ng.org/forum/post/32150</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/32150</guid><dc:creator><![CDATA[tony]]></dc:creator><pubDate>Thu, 08 Oct 2020 02:48:21 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Wed, 07 Oct 2020 08:29:26 GMT]]></title><description><![CDATA[<p dir="auto">Issue still persisted after rebooting and running fsck. Host went into read-only mode not long after it came up.</p>
]]></description><link>https://xcp-ng.org/forum/post/32125</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/32125</guid><dc:creator><![CDATA[Denson]]></dc:creator><pubDate>Wed, 07 Oct 2020 08:29:26 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Fri, 25 Sep 2020 09:08:07 GMT]]></title><description><![CDATA[<p dir="auto"><img src="/forum/assets/uploads/files/1601024837134-xcp-dmesg.png" alt="XCP-dmesg.png" class=" img-fluid img-markdown" /><br />
I will restart and use a systemrescuecd to run fsck</p>
]]></description><link>https://xcp-ng.org/forum/post/31663</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/31663</guid><dc:creator><![CDATA[Denson]]></dc:creator><pubDate>Fri, 25 Sep 2020 09:08:07 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Fri, 25 Sep 2020 08:39:47 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/denson" aria-label="Profile: Denson">@<bdi>Denson</bdi></a> may be corrupt file system? you can probably try fsck on your next reboot</p>
<pre><code>touch /forcefsck
</code></pre>
]]></description><link>https://xcp-ng.org/forum/post/31661</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/31661</guid><dc:creator><![CDATA[tony]]></dc:creator><pubDate>Fri, 25 Sep 2020 08:39:47 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Thu, 24 Sep 2020 17:46:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/forum/user/denson" aria-label="Profile: Denson">@<bdi>Denson</bdi></a> check <code># dmesg</code></p>
]]></description><link>https://xcp-ng.org/forum/post/31626</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/31626</guid><dc:creator><![CDATA[r1]]></dc:creator><pubDate>Thu, 24 Sep 2020 17:46:44 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Thu, 24 Sep 2020 17:19:38 GMT]]></title><description><![CDATA[<p dir="auto">It's a recently installed host.Root is only at 10% utilization. Does XCP-ng have any compatibility issues with Supermicro servers?</p>
]]></description><link>https://xcp-ng.org/forum/post/31621</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/31621</guid><dc:creator><![CDATA[Denson]]></dc:creator><pubDate>Thu, 24 Sep 2020 17:19:38 GMT</pubDate></item><item><title><![CDATA[Reply to XCP-NG Host stuck in read-only mode on Thu, 24 Sep 2020 11:47:08 GMT]]></title><description><![CDATA[<p dir="auto">Disk full?</p>
]]></description><link>https://xcp-ng.org/forum/post/31592</link><guid isPermaLink="true">https://xcp-ng.org/forum/post/31592</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Thu, 24 Sep 2020 11:47:08 GMT</pubDate></item></channel></rss>