XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XCP-NG Host stuck in read-only mode

    Scheduled Pinned Locked Moved Compute
    12 Posts 5 Posters 3.8k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      Denson
      last edited by

      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.
      XCP-Readonly.png
      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:
      XCP-tapdiskerror.png
      Does anyone have any experience with this and how to resolve.

      D 1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Disk full?

        1 Reply Last reply Reply Quote 0
        • D Offline
          Denson
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • R Offline
            r1 XCP-ng Team
            last edited by

            @Denson check # dmesg

            1 Reply Last reply Reply Quote 0
            • T Offline
              tony
              last edited by

              @Denson may be corrupt file system? you can probably try fsck on your next reboot

              touch /forcefsck
              
              1 Reply Last reply Reply Quote 0
              • D Offline
                Denson
                last edited by

                XCP-dmesg.png
                I will restart and use a systemrescuecd to run fsck

                1 Reply Last reply Reply Quote 0
                • D Offline
                  Denson
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • T Offline
                    tony
                    last edited by

                    @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
                    
                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      dmjorge @Denson
                      last edited by

                      @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

                      D 1 Reply Last reply Reply Quote 0
                      • D Offline
                        Denson @dmjorge
                        last edited by Denson

                        @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.
                        xcp-xapi-errors.png
                        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

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO Offline
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          The screenshot error posted is just a harmless warning

                          D 1 Reply Last reply Reply Quote 0
                          • D Offline
                            Denson @olivierlambert
                            last edited by

                            @olivierlambert Those were the only messages on the log, nothing else captured on any other log file like the crit.log file or dmesg

                            1 Reply Last reply Reply Quote 0

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            • First post
                              Last post