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

    File recovery error

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 355 Views 1 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.
    • J Offline
      Jsawyer77
      last edited by

      I am trying to recover file in the community version and receive the error below when selecting the partition. any idea why?

      Command failed: mount --options=loop,ro,sizelimit=1073605509120,offset=135266304 --source=/tmp/1u0k4334uow/vhdi10 --target=/tmp/nealr0tayxa
      mount: /tmp/nealr0tayxa: failed to setup loop device for /tmp/1u0k4334uow/vhdi10.

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        You have left out many details that would likely assist us in helping you. Things like --

        • Is your XO installation up-to-date?
        • What hypervisor? Version? Up-to-date with patches?
        • File system (NFS, SMB, etc) on backup target
        • etc

        It would be good if you posted the complete error message from Settings > Logs.

        1 Reply Last reply Reply Quote 1
        • J Offline
          Jsawyer77
          last edited by

          1. The Xo version is 5.84.2 community version on ubuntu 20.04 and I also tried on 18.04
          2. this runs on xcp-ng 8.2 and is fully patched
          3. I tried with both windows and linux backups
          4. I can restore full backups and have verified they work I just get this issue when trying to recover files
          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Community version doesn't have a release number, but a commit version on master. Please check you are on the latest commit and rebuild 🙂

            1 Reply Last reply Reply Quote 0
            • First post
              Last post