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

    Unable to mount NFS Remote for backups while storage and ISO NFS SR's work perfectly

    Scheduled Pinned Locked Moved Backup
    25 Posts 3 Posters 95 Views 2 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.
    • B Offline
      Bub @Pilow
      last edited by

      @Pilow Sorry for the delay, bud, I was on the road all day yesterday.
      I have to admit, when it comes to CLI I struggle.
      I tried to figure out the mounting command as follows:
      xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
      xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t -vvv nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
      mount: bad usage
      Try 'mount --help' for more information.

      The mount command alone seemed to kick no error, but I do not see any remote/storage created in the gui.
      When I try to add -vvv, it complains

      P 1 Reply Last reply Reply Quote 0
      • P Online
        Pilow @Bub
        last edited by

        @Bub -v, --verbose say what is being done

        just try -v ?

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          Bub @Pilow
          last edited by

          @Pilow seems the same error
          xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -t -v nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
          mount: bad usage
          Try 'mount --help' for more information.

          P 1 Reply Last reply Reply Quote 0
          • P Online
            Pilow @Bub
            last edited by

            @Bub mmm put -v before the -t !

            B 1 Reply Last reply Reply Quote 0
            • B Offline
              Bub @Pilow
              last edited by

              @Pilow That seems did the trick!
              xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ sudo mount -v -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
              mount.nfs: timeout set for Thu Nov 20 15:42:55 2025
              mount.nfs: trying text-based options 'vers=3,addr=192.168.221.20'
              mount.nfs: prog 100003, trying vers=3, prot=6
              mount.nfs: trying 192.168.221.20 prog 100003 vers 3 prot TCP port 2049
              mount.nfs: prog 100005, trying vers=3, prot=17
              mount.nfs: trying 192.168.221.20 prog 100005 vers 3 prot UDP port 54698
              mount.nfs: mount(2): Device or resource busy
              xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ ping 192.168.221.20
              PING 192.168.221.20 (192.168.221.20) 56(84) bytes of data.
              64 bytes from 192.168.221.20: icmp_seq=1 ttl=64 time=0.884 ms
              64 bytes from 192.168.221.20: icmp_seq=2 ttl=64 time=0.531 ms
              64 bytes from 192.168.221.20: icmp_seq=3 ttl=64 time=0.507 ms
              64 bytes from 192.168.221.20: icmp_seq=4 ttl=64 time=0.648 ms
              64 bytes from 192.168.221.20: icmp_seq=5 ttl=64 time=0.496 ms
              ^C
              --- 192.168.221.20 ping statistics ---
              5 packets transmitted, 5 received, 0% packet loss, time 4082ms
              rtt min/avg/max/mdev = 0.496/0.613/0.884/0.145 ms
              xo@xo-ce:/run/xo-server/mounts/LAB-NFS$

              Why would it time out if it does mount nfs sr from the same qnap and same permission settings?! My head is starting to smoke lol

              P B 2 Replies Last reply Reply Quote 0
              • P Online
                Pilow @Bub
                last edited by

                @Bub perhaps is it permission related, or NFS version /mapping related ?

                screenshot ther nfs server side configuration ? if possible.

                1 Reply Last reply Reply Quote 0
                • B Offline
                  Bub @Bub
                  last edited by

                  6752efc5-b958-4fde-8b6a-0eb03e58303e-image.png
                  .22 XCP-ng host
                  .24 XOA
                  .115 Unraid server1 - Able to mount with no issues
                  .114 Unraid server2 - Able to mount with no issues

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    Bub
                    last edited by

                    What gets me is that if it was permissions related, theoretically, it should not mount the nfs storage SR with the same settings pointing to the xcpng host from the same qnap?!
                    It feels like something is different between the xoa nfs implementation and the xcpng host itself.
                    Dont you agree?

                    P 1 Reply Last reply Reply Quote 0
                    • P Online
                      Pilow @Bub
                      last edited by Pilow

                      @Bub I agree, all checks are green ✅

                      could you do a : ip a
                      on the xoa ?

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        Bub
                        last edited by

                        xo@xo-ce:/run/xo-server/mounts/LAB-NFS$ ip a
                        1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
                        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
                        inet 127.0.0.1/8 scope host lo
                        valid_lft forever preferred_lft forever
                        inet6 ::1/128 scope host
                        valid_lft forever preferred_lft forever
                        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
                        link/ether c6:e3:43:a1:5b:e7 brd ff:ff:ff:ff:ff:ff
                        inet 192.168.221.24/24 brd 192.168.221.255 scope global eth0
                        valid_lft forever preferred_lft forever
                        inet6 fe80::c4e3:43ff:fea1:5be7/64 scope link
                        valid_lft forever preferred_lft forever

                        P 1 Reply Last reply Reply Quote 0
                        • P Online
                          Pilow @Bub
                          last edited by Pilow

                          @Bub

                          get out of /run/xo-server/mounts/LAB-NFS

                          could you do a : mount -t nfs

                          just to see if there is not ALREADY a mount point... ?

                          if there is just do : umount /run/xo-server/mounts/LAB-NFS

                          P 1 Reply Last reply Reply Quote 0
                          • P Online
                            Pilow @Pilow
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • B Offline
                              Bub
                              last edited by

                              xo@xo-ce:~$ mount -t nfs
                              xo@xo-ce:~$ sudo mount -v -t nfs -o vers=3 192.168.221.20:/LAB-NFS /run/xo-server/mounts/LAB-NFS/
                              mount.nfs: timeout set for Thu Nov 20 16:50:18 2025
                              mount.nfs: trying text-based options 'vers=3,addr=192.168.221.20'
                              mount.nfs: prog 100003, trying vers=3, prot=6
                              mount.nfs: trying 192.168.221.20 prog 100003 vers 3 prot TCP port 2049
                              mount.nfs: prog 100005, trying vers=3, prot=17
                              mount.nfs: trying 192.168.221.20 prog 100005 vers 3 prot UDP port 54698
                              xo@xo-ce:~$ mount -t nfs
                              192.168.221.20:/LAB-NFS on /run/xo-server/mounts/LAB-NFS type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.221.20,mountvers=3,mountport=54698,mountproto=udp,local_lock=none,addr=192.168.221.20)
                              xo@xo-ce:~$ sudo umount /run/xo-server/mounts/LAB-NFS
                              xo@xo-ce:~$ mount -t nfs

                              So mounting in CLI seems to show it created a mount but i do not see it in the gui. so I unmounted it again and tried to remount in the gui remotes, its did add the remote but after a while, it gave a timeout error
                              a0003377-f39a-4bf8-877b-9b11e70f1c7f-image.png
                              {
                              "shortMessage": "Command failed with exit code 32: mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a",
                              "command": "mount -o hard -t nfs 192.168.45.20:/LAB-NFS /run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a",
                              "escapedCommand": "mount -o hard -t nfs "192.168.45.20:/LAB-NFS" "/run/xo-server/mounts/eecbb7da-e271-4c39-9681-5b50f8d65e9a"",
                              "exitCode": 32,
                              "stdout": "",
                              "stderr": "mount.nfs: Connection timed out",
                              "failed": true,
                              "timedOut": false,
                              "isCanceled": false,
                              "killed": false
                              }

                              P 1 Reply Last reply Reply Quote 0
                              • P Online
                                Pilow @Bub
                                last edited by

                                @Bub why 192.168.45.20 in the REMOTE configuration ?!

                                in CLI you point to 192.168.221.20

                                1 Reply Last reply Reply Quote 0
                                • B Offline
                                  Bub
                                  last edited by

                                  OMG I guess that's what happens when you try to to work on two labs same time, I mixed the lab1 subnet I'm working on with the lab2 on my last mount attempt.
                                  I changed it to the correct subnet and it mounted properly this time
                                  c0a2bcbd-3f04-4524-8e34-bcaff215abec-image.png

                                  Can it be that unmounting it in cli fixed the issue?
                                  I am going to try the same unmount command on lab1 setup, and see if that will get it going also.

                                  Thank you so much @Pilow . I appreciate the time and energy you spend helping me with this one!

                                  P 1 Reply Last reply Reply Quote 0
                                  • P Online
                                    Pilow @Bub
                                    last edited by Pilow

                                    @Bub haha great 😃

                                    yup in the process, you probably had a successful test in CLI to mount and it would block in XOA remote config as the mount already exists.

                                    in your first post it was : "stderr": "mount.nfs: failed to prepare mount: Operation not permitted
                                    and you had a mount.nfs: mount(2): Device or resource busy later on

                                    so keep this unmount command in case 😃

                                    1 Reply Last reply Reply Quote 0
                                    • B Offline
                                      Bub
                                      last edited by

                                      I will tell you a little secret, you taught me more than that one command for CLI lol
                                      One more important note for my Bitwarden 🙂
                                      Thanks again bud!

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