Search results

Quick question - have you tried using mount command directly in CLI? In my case it works. The whole Proxmox 6 attachment routine fails because rpcinfo fails. Is it identical in your case?

The container is unpriviledged. As for the rpcbind version (the main package that allows for rpcinfo), this is for container: rpcbind: Installed: 0.2.3-0.6 Candidate: 0.2.3-0.6 Version table: *** 0.2.3-0.6 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages...

Let me know if you need help ;)

Hey! Don't worry - you can attach the card even to Proxmox 6, although the guide is for Proxmox 5. I will update the guide after some more testing, but the gist is that the only thing that needs to change are the drivers used. In this guide i recompile the drivers provided by the vendor. In...

Now i am really confused, which is a good and a bad sign at once :D Since you've mentioned that it may be a kernel issue, i was wondering what will the container behaviour be. I've created an Ubuntu 18.04 container and first deployed it on Proxmox 5. sudo rpcinfo -p xx.xx.xx.xx worked fine...

Hey! Any ideas? Would somebody help me with temporary access to Proxmox 6 to cross out the networking issues?

@Alwin After some long interactions with the ISP and debugging on my end, here are the findings: NFS fails when check_connection function runs for some reason it generates the following error command '/sbin/showmount --no-headers --exports XX.XX.XX.XX' failed: got timeout it works perfectly...

No output, no matter how i try. I get the output only when mounting is successful. Seems that function is not executed at all.

Ok, so the server restart helped for some reason. Here's a new riddle for you: when mounting the local NAS, there is output to the text file when mounting the offsite NAS, there is no output at all (seems that the function is not reached during execution). Where can it get blocked on the way?

Yes, it is. The weird aspect is that neither the CLI output nor file output work for both - successful NFS mount and unsuccessful one. I even started doubting that this is the function responsible for the mount :)

Yes. Can you try and confirm? Maybe another service needs to be restarted as well?

This is the function i've updated for debugging: sub nfs_mount { my ($server, $export, $mountpoint, $options) = @_; $server = "[$server]" if Net::IP::ip_is_ipv6($server); my $source = "$server:$export"; my $filename = '/home/temp/output.txt'; open(FH, '>', $filename) or...

@Alwin The output does not work unfortunately. It seems that the script output is directed elsewhere.

Exactly. This is what's so weird about this whole thing. For some reason the thing that's supposed to work does not. And i'd be interested to debug the script by understanding what are the vars computed - the address, the export. To be honest, i expect it to be stuck at the address tracing...

The firewall is disabled on both ends. The offsite NAS is exposed to the web via port forwarding on the router. This is why my assumption is that it's tracing related issue and it's very strange that it works on Proxmox 5, even though the algorithm hasn't changed. The only possibility is that...

@Alwin So, just to spice things up, i went a bit further :D I have 2 identical NAS-s - one offsite and one onsite. Both mount perfectly well via pvesm add nfs on Proxmox 5 Both mount perfectly well via mount -t on Proxmox 6 The offsite one doesn't mount via pvesm add nfs on Proxmox 6 The onsite...

@Alwin Thing is - mount works on Ubuntu 19.10. If you need other kernels tested - let me know and i'll gladly help. How does pvesm add nfs differ? It seems that the base functionality works well, but Proxmox implementation stumbles for some reason.

It's ipv4 - both of them. IMO the best vector to tackle the issue is to actually see how Proxmox 6 differs from Proxmox 5 in this regard. It works perfectly on Proxmox 5.

rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=[IP_MASKED],mountvers=3,mountport=46186,mountproto=udp,local_lock=none,addr=[IP_MASKED]

@Alwin This is the commend for trying to add the NAS via Proxmox: pvesm add nfs storage --path /mnt/pve/storage --server [ADDRESS] --export [PATH] --content snippets,backup,rootdir,vztmpl,iso,images --maxfiles 4 This is the commend for trying to add the NAS via mount: mount -t nfs...